From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 214021] New: The USB devices fail to be detected during boot
Date: Tue, 10 Aug 2021 15:26:42 +0000 [thread overview]
Message-ID: <bug-214021-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=214021
Bug ID: 214021
Summary: The USB devices fail to be detected during boot
Product: Drivers
Version: 2.5
Kernel Version: 5.12 and later version
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: chris.chiu@canonical.com
Regression: No
Created attachment 298255
--> https://bugzilla.kernel.org/attachment.cgi?id=298255&action=edit
output of lsusb -v
We found some USB devices (keyboard, storage) will fail to be detected on
kernel 5.13 during boot, but it's working OK after re-plug the device. After
looking into the dmesg during boot, there's an error message as down below
[ 39.350435] hub 1-0:1.0: USB hub found
[ 39.398835] hub 1-0:1.0: 12 ports detected
[ 39.622744] usb usb1-port3: couldn't allocate usb_device
Then we try to reproduce it on older kernel (5.4 and 5.8), there's no such
problem. After bisecting, we found the commit
https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2
makes the difference. It seems that hub_power_on_good_delay is not long enough
for this hub. The bPwrOn2PwrGood in the Hub Descriptor (please refer to the
attached lsusb-v.txt) is 20ms, which seems pretty normal when I check the same
thing on other hubs. Can we totally trust this? Please suggest what we should
do for this kind of hub. Thanks
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2021-08-10 15:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 15:26 bugzilla-daemon [this message]
2021-08-10 15:27 ` [Bug 214021] The USB devices fail to be detected during boot bugzilla-daemon
2021-08-10 15:39 ` bugzilla-daemon
2021-08-11 15:38 ` bugzilla-daemon
2021-08-12 2:31 ` bugzilla-daemon
2021-08-16 7:09 ` bugzilla-daemon
2021-08-16 7:29 ` bugzilla-daemon
2021-08-16 14:16 ` bugzilla-daemon
2021-08-18 5:48 ` bugzilla-daemon
2021-08-20 11:33 ` bugzilla-daemon
2021-08-20 14:31 ` bugzilla-daemon
2021-08-23 12:49 ` bugzilla-daemon
2021-08-23 14:06 ` bugzilla-daemon
2021-08-24 7:37 ` bugzilla-daemon
2021-08-25 12:08 ` bugzilla-daemon
2022-03-25 8:30 ` bugzilla-daemon
2022-04-07 21:25 ` bugzilla-daemon
2022-04-07 21:27 ` bugzilla-daemon
2022-04-08 11:55 ` bugzilla-daemon
2022-04-08 11:56 ` bugzilla-daemon
2022-04-08 11:57 ` bugzilla-daemon
2022-04-24 7:50 ` bugzilla-daemon
2022-04-24 7:52 ` bugzilla-daemon
2022-04-25 10:08 ` bugzilla-daemon
2022-04-25 11:00 ` bugzilla-daemon
2022-05-13 7:29 ` bugzilla-daemon
2022-05-13 8:29 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-214021-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox