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 11:54:02 +0000 [thread overview]
Message-ID: <bug-220181-208809-UWiKXEsFRy@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 #4 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
(In reply to Mr. Beedell, Roke Julian Lockhart (RJLB) from comment #3)
> (In reply to Mathias Nyman from comment #2)
>
> > Or does this xHC host have 0 ports on usb2 roothub as well?
>
> I dare say that I'm operating at the boundaries of my lay man's knowledge as
> it is. How do you suggest that I ascertain this?
Probably best to take a closer at the xHC port information of this host
The reg-ext-protocol:00 and reg-ext-protocol:01 files in debugfs should show
all info about the ports the host provides:
Example, this machine has only one xHC at PCI address 0000:00:14.0:
cat /sys/kernel/debug/usb/xhci/0000:00:14.0/reg-ext-protocol*
EXTCAP_REVISION = 0x02000802
EXTCAP_NAME = 0x20425355
EXTCAP_PORTINFO = 0x30010e01
EXTCAP_PORTTYPE = 0x00000000
EXTCAP_MANTISSA1 = 0x000c0021
EXTCAP_MANTISSA2 = 0x05dc0012
EXTCAP_MANTISSA3 = 0x01e00023
EXTCAP_REVISION = 0x03000802
EXTCAP_NAME = 0x20425355
EXTCAP_PORTINFO = 0x10000610
EXTCAP_PORTTYPE = 0x00000000
EXTCAP_MANTISSA1 = 0x00050134
Above shows:
EXTCAP_REVISION tells if ports are USB3 or USB2,
EXTCAP_PORTNINFO = 0x****AA**, where AA tells us how many ports
--
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 11:54 UTC|newest]
Thread overview: 18+ 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 [this message]
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
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-UWiKXEsFRy@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;
as well as URLs for NNTP newsgroup(s).