librealsense: Re-starting the color stream crashes the camera
Required Info | |
---|---|
Camera Model | D435i |
Firmware Version | 5.12.06 |
Operating System & Version | Linux Ubuntu 20.04 |
Kernel Version (Linux Only) | 5.4 |
Platform | PC |
SDK Version | 2.36.0 |
Language | python |
Segment | others |
Issue Description
Using the RealSense viewer and my D435i camera, the RGB stream only works when enabling it the first time. Stopping and re-enabling the stream does not work, ‘no frames arrived’ error message is shown. Plugging the camera’s USB out and in again helps.
This was tested on two Linux computers (Ubuntu and Arch), latest versions, using compiled realsense with RSUSB=1 testing with RealSense Viewer. HOWEVER, this problem does not appear on every USB ports/controllers:
- using the port driven by
Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
host controller works - using the port driven by
ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
host controller does not work (tested on two different computers)
Could the issue be hardware related? How come the stream work the first time?
Here are the logs when using the ASMedia technology host controller, and re-starting the RGB stream using RealSense Viewer (Ubuntu 20.04): singlecam_dmesg.log
...
[ 1370.391612] hid-sensor-hub 0003:8086:0B3A.0008: No report with id 0xffffffff found
[ 1429.940193] xhci_hcd 0000:09:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 15
Hi @jurc192 I note that you have updated the camera to the most recent firmware and that you have built Ubuntu 20.04 with the RSUSB installation method. So that covers the first two suggestions that I would have recommended trying.
It does seem likely though that it is an issue related to a specific USB port rather than a firmware or SDK issue.
If you know how to access the BIOS settings when your computer is booting up and you feel confident in making changes to the configuration settings, could you check if your computer’s BIOS has an option called xHCI please? If it does, set it to Enabled (not Auto or Smart Auto). xHCI may be under the Devices > USB section of the BIOS options.
Given that the working Intel controller is an xHCI one and the ASMedia ports’ description does not mention xHCI, this will hopefully resolve your problem with the affected ports.