Wrong timestamp obtained in D435i

[fanofpal]

---

Required Info
Camera Model	D435i
Firmware Version	5.11.15.0
Operating System & Version	Ubuntu 18
Kernel Version (Linux Only)	5.0.0-36-generic
Platform	PC
SDK Version	2.0
Language	python
Segment	others

Issue Description

Hello, I was tring to collect some data used for a SLAM project. However, the frame timestamp obtained from frame seemed to have some problems. The following are the printed timestamps of consecutive frames. I used the code below to get them.
timestamp = frames.get_timestamp()

Then I checked the timestamp in Realsnse-viewer, it showed that the frame timestamps(global time) were also wrong (something like 3148958470379) in color and depth stream, although that in IMU streams were correct.

[Fred3D-tech]

did you try patching your kernel ?

[fanofpal]

did you try patching your kernel ?

Yes, I installed the SDK following the Linux manual installation guide, the patched kernel modules were also applied successfully.
Actually, every time I reopen the color and depth streams, they can get the normal global timestamp--but only for a few seconds, then they suddenly change to wrong number, and never return to normal--unless I reopen them again.
However, the IMU stream is always normal.

[JeremyBYU]

Same issue as #4505 . Read my comments there to understand problem. This problem is reproducable on 2 x86 computers and a raspberry pi for all parched/unpatched kernels from 5.0-5.3.

The issue goes away for me using 4.18 kernel using dkms install.

[fanofpal]

@JeremyBYU Thanks for your reply, I encountered the same problem as you, and now I switched back to the 4.15 kernel.

[RealSenseCustomerSupport]

---

Hi @fanofpal

Based on your previous comment, you're able to get things working. Is there anything more necessary on this thread?

[ev-mp]

The resolution was successfully integrated into development branch. scheduled for the upcoming release.

[RealSenseSupport]

Hi @fanofpal

Have you tried the latest librealsense? There has been quite a bit of PRs that have been put in place recently that should fix your issue.

*If we don’t hear from you in 7 days, this issue will be closed.