From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220181] Users across distributions see “config failed, hub doesn’t have any ports! (err -19)” from xhci_hcd at boot.
Date: Wed, 24 Sep 2025 13:37:44 +0000 [thread overview]
Message-ID: <bug-220181-208809-bLOFXix5CV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220181-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220181
--- Comment #20 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
The patch supporting PCI xHCI controllers with no USB3 ports is now in usb-next
branch, and should be part of 6.18-rc1 kernel.
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/commit/?h=usb-next&id=719de070f764e079cdcb4ddeeb5b19b3ddddf9c1
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2025-09-24 13:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 12:52 [Bug 220181] New: Users across distributions see “config failed, hub doesn’t have any ports! (err -19)” from xhci_hcd at boot bugzilla-daemon
2025-06-02 7:30 ` [Bug 220181] " bugzilla-daemon
2025-06-02 10:59 ` bugzilla-daemon
2025-06-02 11:10 ` bugzilla-daemon
2025-06-02 11:54 ` bugzilla-daemon
2025-06-02 12:25 ` bugzilla-daemon
2025-06-02 13:24 ` bugzilla-daemon
2025-06-04 13:14 ` bugzilla-daemon
2025-06-14 19:57 ` bugzilla-daemon
2025-07-02 12:25 ` bugzilla-daemon
2025-07-02 13:32 ` bugzilla-daemon
2025-07-08 9:13 ` bugzilla-daemon
2025-07-08 9:34 ` bugzilla-daemon
2025-07-14 8:31 ` bugzilla-daemon
2025-08-22 16:19 ` bugzilla-daemon
2025-08-24 23:19 ` bugzilla-daemon
2025-08-25 9:39 ` bugzilla-daemon
2025-08-27 7:32 ` bugzilla-daemon
2025-09-24 12:06 ` bugzilla-daemon
2025-09-24 12:19 ` bugzilla-daemon
2025-09-24 13:07 ` bugzilla-daemon
2025-09-24 13:37 ` bugzilla-daemon [this message]
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-220181-208809-bLOFXix5CV@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 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.