From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219387] Bluetooth: hci0: Reading supported features failed (-16)
Date: Tue, 08 Jul 2025 04:46:14 +0000 [thread overview]
Message-ID: <bug-219387-62941-ajVT3sIayl@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219387-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219387
potefa (tynsareatger@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tynsareatger@gmail.com
--- Comment #12 from potefa (tynsareatger@gmail.com) ---
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
https://speedstars-unblocked.github.io 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 the assignee for the bug.
next prev parent reply other threads:[~2025-07-08 4:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 16:40 [Bug 219387] New: Bluetooth: hci0: Reading supported features failed (-16) bugzilla-daemon
2024-10-14 16:42 ` [Bug 219387] " bugzilla-daemon
2024-10-16 5:51 ` bugzilla-daemon
2024-10-16 20:44 ` bugzilla-daemon
2024-10-16 21:02 ` bugzilla-daemon
2024-10-17 0:35 ` bugzilla-daemon
2024-11-03 14:04 ` bugzilla-daemon
2024-11-04 13:02 ` bugzilla-daemon
2024-11-04 13:04 ` bugzilla-daemon
2024-11-04 13:07 ` bugzilla-daemon
2025-01-27 19:02 ` bugzilla-daemon
2025-01-27 19:09 ` bugzilla-daemon
2025-01-28 4:02 ` bugzilla-daemon
2025-07-08 4:46 ` bugzilla-daemon [this message]
2025-12-24 15:04 ` bugzilla-daemon
2025-12-24 15:45 ` 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-219387-62941-ajVT3sIayl@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.