Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USB Error while running a Docker Container #1124

Open
SimeonOA opened this issue Jun 23, 2020 · 1 comment
Open

USB Error while running a Docker Container #1124

SimeonOA opened this issue Jun 23, 2020 · 1 comment

Comments

@SimeonOA
Copy link

I am running a Docker container application that uses libfreenect2 in a system/setup with eight computers running Ubuntu 18.04 and a Kinect connected to each of the computers. All computers are running the same version of the application and were set up alike. The USB is USB 3.0.

I keep seeing this error on two of the computers:

[Error] [protocol::CommandTransaction] bulk transfer failed: LIBUSB_ERROR_TIMEOUT Operation timed out
[Error] [protocol::CommandTransaction] bulk transfer failed: LIBUSB_ERROR_TIMEOUT Operation timed out
[Error] [protocol::CommandTransaction] bulk transfer failed: LIBUSB_ERROR_TIMEOUT Operation timed out
[Info] [Freenect2DeviceImpl] stopping...
[Info] [Freenect2DeviceImpl] canceling rgb transfers...
[Info] [Freenect2DeviceImpl] canceling depth transfers...
[Error] [protocol::CommandTransaction] bulk transfer failed: LIBUSB_ERROR_TIMEOUT Operation timed out

Disconnecting and reconnecting the USB usually fixes this for a short while before the issue develops again.

I have looked at similar issues: 546, 547, 915, 831, 458 and the troubleshooting tips here.

I tried increasing the USBFS buffer size to 64 and 128 but this had no effect.

Disabling USB autosuspend worked for a longer period but the error still developed.

Do you have any suggestions on what might be wrong or what I could try?

All the other computers are working without this error and have the same buffer size and settings as the two which have this error.

Thank you.

@floe
Copy link
Contributor

floe commented Jun 24, 2020

Just guessing, but I'd say there's two possible causes:

  • if the computers are different (i.e. different USB3 host controllers in particular): bug in the HC silicon and/or driver
  • if the computers are identical: problems with the USB3 cables

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants