USB hub enumeration failure: error -71
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c, linux
- Domain
- embedded-iot, operating-systems
Research direction
No source file, test, or kernel entry point is identified. Start by reproducing the reported Raspberry Pi USB topology and error -71 logs, then compare the behavior with linked issue #2692 and the attempted dwc_otg.fiq_fsm_mask=0x0 setting. Done means the affected input device enumerates successfully through the described hub setup.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- C
- Stars
- 13.2k
- Forks
- 5.5k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 21
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/linux
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7415 · 2 comments · 1 reaction ·
-
rp1-cfe doesn't forward V4L2_EVENT_SOURCE_CHANGE event from csi-2 sensor driver to userspace app Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raspberrypi/linux#7399 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
raspberrypi/linux#7357 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7054 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
raspberrypi/linux#7634 · 8 comments · 1 reaction ·