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: Mon, 02 Jun 2025 13:24:00 +0000 [thread overview]
Message-ID: <bug-220181-208809-SLzcYLnFAp@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 #6 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
This means the xHC controller only has one entry for "supported protocol
capability", which lists just one USB2 port.
There is no entry at all for USB3 ports
The xhci driver needs some minor changes in xhci-pci.c code to make this work
properly.
--
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:[~2025-06-02 13:24 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 [this message]
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
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-SLzcYLnFAp@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