From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 222049] xhci_hcd: USB device on onboard port fails to enumerate (error -110/-71), delays boot around 70s on ASUS ROG Strix X870-F
Date: Wed, 23 Sep 2026 19:23:56 +0000 [thread overview]
Message-ID: <bug-222049-208809-EJKDwRMWQf@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222049-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=222049
Michał Pecio (michal.pecio@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michal.pecio@gmail.com
--- Comment #1 from Michał Pecio (michal.pecio@gmail.com) ---
Did this device ever work in the past?
It's probably Mediatek Bluetooth, they get stuck in such state and need a
standby power cycle to recover (disconnect the PC from power for a minute). I
recall some discussion about this on linux-bluetooth, but not sure how far it
went. IIRC some users had luck blacklisting btusb (which implies that the
driver puts the device in the bad state), or maybe it was with Realtek chips,
not sure. Others found that some BIOS settings like "ErP ready" cut power to BT
during standby and thus "fix" this device automatically.
IIRC the delay itself is not the kernel's fault - userspace started quickly,
but then it chooses to wait long time for enumeration to complete (or fail).
--
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 prev parent reply other threads:[~2026-09-23 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 22:41 [Bug 222049] New: xhci_hcd: USB device on onboard port fails to enumerate (error -110/-71), delays boot around 70s on ASUS ROG Strix X870-F bugzilla-daemon
2026-09-23 19:23 ` bugzilla-daemon [this message]
2026-09-24 11:13 ` [Bug 222049] " bugzilla-daemon
2026-09-24 11:14 ` 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-222049-208809-EJKDwRMWQf@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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