At boot, I see the undermentioned in red in dmesg
:
config failed, hub doesn't have any ports! (err -19)
I’ve one entry for each boot in journalctl
. What does this mean?
At boot, I see the undermentioned in red in dmesg
:
config failed, hub doesn't have any ports! (err -19)
I’ve one entry for each boot in journalctl
. What does this mean?
Using the first section of the error:
hub 12-0:1.0
…I’ve ascertained what the cause is:
Using lsusb -t
, I find:
/: 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:
../../../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
:
5a:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 2.0 xHCI
It’s the virtual USB controller, not exposing any ports despite the kernel purportedly requiring it. However, there obviously aren’t ports on a virtual device.
Consequently, do I take this to Linux, ASRock, or AMD?
My situation is similar to yours, but mine is hub 8-0:1.0. My system is Debian 12, and the motherboard is ROG STRIX B850-F GAMING WIFI. The result of following your steps.
/: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/0p, 5000M
../../../devices/pci0000:00/0000:00:08.3/0000:0e:00.0/usb8/8-0:1.0
3.lspci -s 0e:00.0:
0e:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15b8
Thank you, @tasmira! That should cut out ASRock from the equation. Considering it’s consistently an AMD controller that is causing problems, I’ll try talking to AMD. [1] If they state that it’s how Linux interacts with the controller, I’ll take it to spooky scary kernel Bugzilla.
I’ve had a single like at adaptivesupport.amd.com/s/question/0D5KZ00000rBD190AG
, and no responses. I originally believed that its nicheness would be of use, but I now disagree: it’s not visited enough to be. Consequently, I’ve reported this to bugzilla.kernel.org/show_bug.cgi?id=220181
: