Skip to content

USB hub enumeration failure: error -71 #4743

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

Open
HendrikR opened this issue Nov 27, 2021 · 5 comments
Open

USB hub enumeration failure: error -71 #4743

HendrikR opened this issue Nov 27, 2021 · 5 comments

Comments

@HendrikR
Copy link

I have a Raspberry Pi 3 Model B Plus Rev 1.3, with kernel 5.10.63-v7+ Raspbian running on it.
Connected to one of the Pi's USB ports is a hub, Chipset idVendor=0424, idProduct=2514 see here.
When I try to connect a USB (input) device, it cannot enumerate and outputs errors:

Nov 27 20:16:17 retropie kernel: usb 1-1.1.3.1: new low-speed USB device number 15 using dwc_otg
Nov 27 20:16:17 retropie kernel: usb 1-1.1.3.1: device descriptor read/64, error -71
Nov 27 20:16:17 retropie kernel: usb 1-1.1.3.1: device descriptor read/64, error -71
Nov 27 20:16:17 retropie kernel: usb 1-1.1.3.1: new low-speed USB device number 16 using dwc_otg
Nov 27 20:16:17 retropie kernel: usb 1-1.1.3.1: device descriptor read/64, error -71
Nov 27 20:16:18 retropie kernel: usb 1-1.1.3.1: device descriptor read/64, error -71
Nov 27 20:16:18 retropie kernel: usb 1-1.1.3-port1: attempt power cycle
Nov 27 20:16:18 retropie kernel: usb 1-1.1.3.1: new low-speed USB device number 17 using dwc_otg
Nov 27 20:16:19 retropie kernel: usb 1-1.1.3.1: device not accepting address 17, error -71
Nov 27 20:16:19 retropie kernel: usb 1-1.1.3.1: new low-speed USB device number 18 using dwc_otg
Nov 27 20:16:19 retropie kernel: usb 1-1.1.3.1: device not accepting address 18, error -71
Nov 27 20:16:19 retropie kernel: usb 1-1.1.3-port1: unable to enumerate USB device

Strangely enough, I can connect non-input USB devices. I tested several USB sticks and another USB hub, all of which connected without problems. I could even connect the (working) USB hub to the faulty one, and then connect an input device to the second USB hub, without receiving errors.
The issue may be related to this one. As outlined there, I tried setting dwc_otg.fiq_fsm_mask=0x0, but still got the errors.

@P33M
Copy link
Contributor

P33M commented Nov 29, 2021

What device are you plugging into the Pi hub?

@HendrikR
Copy link
Author

HendrikR commented Nov 29, 2021

I tried several devices on the Hub, with the HID (human input device) ones producing an error, while others worked:

  • (error) A cheap USB gamepad: idVendor=081f, idProduct=e401, bcdDevice= 1.06
  • (error) A Lenovo ThinkPad USB keyboard: idVendor=17ef, idProduct=6047, bcdDevice= 3.30
  • (error) A USB mouse: idVendor=09da, idProduct=000a, bcdDevice= 0.14
  • (works) A USB cardreader: idVendor=214b, idProduct=7250, bcdDevice= 1.00
  • (works) Another USB Hub from a different manufacturer: idVendor=05e3, idProduct=0608, bcdDevice=77.64

I also tried the (faulty) USB hub on my desktop computer, where it produced no errors whatsoever with any device.
EDIT: It also worked when I connected the HID devices to the working hub, connected to the faulty hub, connected to the RasPi, so it's probably not a power-related error.

@P33M
Copy link
Contributor

P33M commented Nov 30, 2021

Please post a full sudo lsusb -v for the bus with the faulty hub attached.

@HendrikR
Copy link
Author

Output of sudo lsusb -v

@P33M
Copy link
Contributor

P33M commented Dec 1, 2021

Your faulty hub is actually a 058f:6254 Alcor Micro Corp. USB Hub which is a single-TT hub. These are not recommended for use on Pi 0-3 for a variety of reasons. I would suggest sourcing a multi-TT hub.

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