You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Raspberry Pi model 3 with three USB webcams, a USB keyboard and a USB mouse. The 3 webcams are plugged directly into the Raspberry Pi. The USB keyboard and mouse are plugged in via a four port hub.
I am using motionto stream the webcam video. Everything works fine for anywhere from about 30 seconds to a few minutes. Then the webcams, keyboard and mouse stop working. The following message appears repeatedly in the dmesg output:
uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
See below for the full dmesg and lsusb -v output .
I have tried a number of resolutions and frame rates, but the results are the same. The motion command is configured to use three threads, one per camera. The CPU utilization for motion is about 18%, mostly allocated to one of the four cores.
I see that issue #618 is similar and I have tried the following things:
Setting uvcvideo quirks to 0x100 in /etc/modprobe.d/uvcvideo.conf
Adding dwc_otg.fiq_fsm_enable=0 to /boot/cmdline.txt and rebooting
Replacing dwc_otg.fiq_fsm_enable=0 with dwc_otg.fiq_fsm_mask=0x3 and rebooting
Enabling uvcvideo trace level 0x408
However, none of these resolve the issue. Any thoughts on what else to try?
Back-of-the-envelope calculation of bandwidth usage:
3072 bytes = 24576 bits per camera per microframe (negating bit-stuff overhead and protocol overhead of a few bytes)
24576 x 3 = 73728 bits per microframe
73728 x 8000 = 589mbit/s
USB2.0 has a 480mbit/s raw data rate. I suspect it works briefly because each camera doesn't always send the maximum amount of data per microframe.
The bug in this case is with the bandwidth reservation code - it should reject transfers that could exceed the maximum periodic bandwidth reservation for USB2.0.
There is a long-standing issue over on the Digilent forums regarding the Analog Discovery 2 not working correctly on raspberry pi 3. As another high-bandwidth USB2 device, I wonder if this could be the root cause?
I have a Raspberry Pi model 3 with three USB webcams, a USB keyboard and a USB mouse. The 3 webcams are plugged directly into the Raspberry Pi. The USB keyboard and mouse are plugged in via a four port hub.
I am using
motion
to stream the webcam video. Everything works fine for anywhere from about 30 seconds to a few minutes. Then the webcams, keyboard and mouse stop working. The following message appears repeatedly in the dmesg output:See below for the full dmesg and lsusb -v output .
I have tried a number of resolutions and frame rates, but the results are the same. The
motion
command is configured to use three threads, one per camera. The CPU utilization formotion
is about 18%, mostly allocated to one of the four cores.I see that issue #618 is similar and I have tried the following things:
However, none of these resolve the issue. Any thoughts on what else to try?
Here is the lsusb -v output:
Here is the dmesg output at the point where the USB becomes unresponsive:
The text was updated successfully, but these errors were encountered: