[Bug 220181] New: Users across distributions see “config failed, hub doesn’t have any ports! (err -19)” from xhci_hcd at boot.

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=220181

            Bug ID: 220181
           Summary: Users across distributions see “config failed, hub
                    doesn’t have any ports! (err -19)” from xhci_hcd at
                    boot.
           Product: Drivers
           Version: 2.5
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: low
          Priority: P3
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: 6svcyk03@rokejulianlockhart.addy.io
        Regression: No

At boot, I see the undermentioned in red in `dmesg`:

> ~~~log
> config failed, hub doesn't have any ports! (err -19)
> ~~~

I've one entry for each boot in `journalctl`.

Using the first section of the error:

> ~~~YAML
> hub 12-0:1.0
> ~~~

...I believe that I've ascertained what the cause is. Using `lsusb -t`, I find:

> ~~~YAML
> /:  Bus 012.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/0p, 5000M
> ~~~

`Driver=xhci_hcd/0p` means it has 0 ports, which is invalid, hence the error.

I tried to `readlink /sys/class/usb_host/usb12` it to ascertain what the cause
is, but that fails, because the device unsuccessfully enumerated. Consequently,
I used `readlink /sys/bus/usb/devices/usb12` to verify the device ID:

> ~~~log
> ../../../devices/pci0000:00/0000:00:08.3/0000:5a:00.0/usb12
> ~~~

When known, I used `5a:00.0` to locate the cause with `lspci -s 5a:00.0`:

> ~~~YAML
> 5a:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 2.0 xHCI
> ~~~

It's the virtual "Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB
2.0 xHCI" USB controller, not exposing any ports despite the driver purportedly
requiring it. However, there obviously aren't ports on a virtual device.

At
https://discussion.fedoraproject.org/t/what-does-config-failed-hub-doesnt-have-any-ports-err-19-mean/153954,
I cite corroborations from Kali Linux, Ubuntu, Debian and Fedora. However, I've
also received a personal e-mail from an interested party who claims to
reproduce this on openSUSE.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.