-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Linux 5.15.32 sometimes failing to initialize USB #5064
Comments
The problem reported by the kernel is that there is an interrupt that "nobody care[s]" about:
I think this means that either there was no handler for the interrupt or that any handlers returned IRQ_NONE (not mine). Earlier in the log we can see that IRQ 20 is the dwc2 USB interrupt:
and the list of handlers includes "dwc2_handle_common_intr". Without reading the driver I would guess that is in an unexpected kind of interrupt, either because it is a feature that isn't being used or because the driver just isn't ready to receive one at that time (both of which sound likes bugs or major limitations). |
Are you specifying the |
i.e. |
Thank you for the quick help, everybody! Here's the config.txt:
Bootloader version:
Here's the dmesg from a happy boot just 10 minutes after the problem showed, no changes were done to the system. I overwrote some details with
|
I was able to reproduce a very similiar issue with Mainline on a Raspberry Pi 3A+ and a USB hub after suspend 2 idle. The following branch contains the relevant fix ( usb: dwc2: Fix HCD resume ): Maybe this also fixes the issue here. |
Please see at #6247 (comment) for a test build, which should fix the dwc2 IRQ issue. |
Describe the bug
Hi!
I have built a yocto-image for my CM4, and I'm using linux 5.15.32 from this repository. The CM4's USB2 lines are connected to a FE1.1S 4port hub.
I am normally seeing happy operation, and can see 2 devices connected to the hub's downstream ports. But very rarely, the system boots up and there's a crash/warning/calltrace in dmesg, and then USB initialization seem to fail (
[ 13.984092] usb 3-1: device descriptor read/64, error -110
), and neither of the 2 devices show up. I am puzzled how this can happen only sometimes, since the system boots from readonly-mounted storage, so every bootup should be the same.The dmesg when it happens is attached. My questions are:
Thank you for your help!
Steps to reproduce the behaviour
Boot the system many times until it happens.
Device (s)
Raspberry Pi CM4 Lite
System
Linux version 5.15.32-v8
Logs
Additional context
No response
The text was updated successfully, but these errors were encountered: