Realsense warm reboot issue

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

Hi ,

I am connectting the Intel realsense D415 to Nano production module . When I run sudo reboot test. I saw below err happening very often. once it happned the only way to recover is doing a hotplug or code reboot . I also applied the power control patch to power cycle realtek_hub before sudo reboot. it improved but still the issue can be reproduced .

Oct 24 09:52:13 cameras kernel: usbcore: registered new interface driver usbfs
Oct 24 09:52:13 cameras kernel: usbcore: registered new interface driver hub
Oct 24 09:52:13 cameras kernel: usbcore: registered new device driver usb
Oct 24 09:52:13 cameras kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 24 09:52:13 cameras kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 24 09:52:13 cameras kernel: usb usb1: Product: xHCI Host Controller
Oct 24 09:52:13 cameras kernel: usb usb1: Manufacturer: Linux 4.8.0-58-generic xhci-hcd
Oct 24 09:52:13 cameras kernel: usb usb1: SerialNumber: 0000:00:14.0
Oct 24 09:52:13 cameras kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
Oct 24 09:52:13 cameras kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 24 09:52:13 cameras kernel: usb usb2: Product: xHCI Host Controller
Oct 24 09:52:13 cameras kernel: usb usb2: Manufacturer: Linux 4.8.0-58-generic xhci-hcd
Oct 24 09:52:13 cameras kernel: usb usb2: SerialNumber: 0000:00:14.0
Oct 24 09:52:13 cameras kernel: usb: port power management may be unreliable
Oct 24 09:52:13 cameras kernel: usb 1-8: new full-speed USB device number 2 using xhci_hcd
Oct 24 09:52:13 cameras kernel: usb 1-8: New USB device found, idVendor=8087, idProduct=0a2b
Oct 24 09:52:13 cameras kernel: usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 24 09:52:13 cameras kernel: usb 2-2: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-2: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-2: device not accepting address 2, error -71
Oct 24 09:52:13 cameras kernel: usb 2-2: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-2: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-2: device not accepting address 3, error -71
Oct 24 09:52:13 cameras kernel: usb 2-2: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-2: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-2: device not accepting address 4, error -71
Oct 24 09:52:13 cameras kernel: usb 2-2: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-2: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-2: device not accepting address 5, error -71
Oct 24 09:52:13 cameras kernel: usb usb2-port2: unable to enumerate USB device
Oct 24 09:52:13 cameras kernel: usb 2-3: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-3: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-3: device not accepting address 6, error -71
Oct 24 09:52:13 cameras kernel: usb 2-3: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-3: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-3: device not accepting address 7, error -71
Oct 24 09:52:13 cameras kernel: usb 2-3: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-3: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-3: device not accepting address 8, error -71
Oct 24 09:52:13 cameras kernel: usb 2-3: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-3: Device not responding to setup address.
Oct 24 09:52:13 cameras kernel: usb 2-3: device not accepting address 9, error -71
Oct 24 09:52:13 cameras kernel: usb usb2-port3: unable to enumerate USB device
Oct 24 09:52:13 cameras kernel: usbcore: registered new interface driver btusb
3

Hi,
We don’t have D415. Will try D435 and check if we can reproduce the same error.

4

great. thanks. you can start realsense rgb and depth streaming then do a sudo reboot

5

Hi,
We have released r32.4.3. Could you try this release?

6

yes. we just tried today. after installing realsense driver … open realsense-view to enable rgb and depth video. then run sudo reboot. I hit the problem on second reboot.

7

Hi,
Please share the steps for reference. Not sure but it looks like you don’t close realsense-viewer before executing sudo reboot. If the issue is specific to the case, could you try to close the app and then do sudo reboot?

8

we tried to close the app after open then do reboot … still can reprdouce it … could you try it on your side too ?

9

Hi,
We don’t observe the issue in executing

  1. Open realsense-view
  2. Turn on depth stream and color stream
  3. Close realsense-view
  4. Reboot device

No issue is seen in 10 trials on Nano + D435. Could you upgrade the firmware and try again? We have seen certain issue and it disappears after firmware upgrade: