You are not logged in.
Pages: 1
Hey everyone,
Arch newbie here (8 months) and I've ran into a pretty annoying issue. A USB port seems to have gone kaput, and while seemingly no important devices (peripherals, fans) are attached to it my system tries to enable it nonetheless, resulting in long boot times as it cycles through a few attempts before finally giving up.
I have already cycled through and disabled/re-enabled each USB port in my BIOS but to no success. How can I terminate this issue port before the boot gets stuck on trying to get it's attention? Attached is the output of dmesg --ctime with extraneous information removed, aside from a few lines of border entries.
[Mon Mar 2 11:33:15 2026] [drm] Initialized amdgpu 3.64.0 for 0000:0c:00.0 on minor 0
[Mon Mar 2 11:33:15 2026] amdgpu 0000:0c:00.0: [drm] Cannot find any crtc or sizes
[Mon Mar 2 11:33:15 2026] [drm] pre_validate_dsc:1667 MST_DSC dsc precompute is not needed
[Mon Mar 2 11:33:17 2026] usb 1-8: device descriptor read/64, error -110
[Mon Mar 2 11:33:33 2026] usb 1-8: device descriptor read/64, error -110
[Mon Mar 2 11:33:33 2026] usb 1-8: new high-speed USB device number 5 using xhci_hcd
[Mon Mar 2 11:33:39 2026] usb 1-8: device descriptor read/64, error -110
[Mon Mar 2 11:33:55 2026] usb 1-8: device descriptor read/64, error -110
[Mon Mar 2 11:33:55 2026] usb usb1-port8: attempt power cycle
[Mon Mar 2 11:33:55 2026] usb 1-8: new high-speed USB device number 6 using xhci_hcd
[Mon Mar 2 11:34:00 2026] usb 1-8: Device not responding to setup address.
[Mon Mar 2 11:34:05 2026] usb 1-8: Device not responding to setup address.
[Mon Mar 2 11:34:05 2026] usb 1-8: device not accepting address 6, error -71
[Mon Mar 2 11:34:06 2026] usb 1-8: new high-speed USB device number 7 using xhci_hcd
[Mon Mar 2 11:34:10 2026] usb 1-8: Device not responding to setup address.
[Mon Mar 2 11:34:15 2026] usb 1-8: Device not responding to setup address.
[Mon Mar 2 11:34:16 2026] usb 1-8: device not accepting address 7, error -71
[Mon Mar 2 11:34:16 2026] usb usb1-port8: unable to enumerate USB device
[Mon Mar 2 11:34:16 2026] fbcon: Taking over console
[Mon Mar 2 11:34:16 2026] Console: switching to colour frame buffer device 240x67
Last edited by Rocklost (Yesterday 22:02:55)
Offline
https://bbs.archlinux.org/viewtopic.php?id=297994
The problem w/ that is that the device doesn't even enumerate…
output of dmesg --ctime with extraneous information removed, aside from a few lines of border
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.stSanity check: is this a dual boot system?
Offline
Thanks for responding, and no I am not dual booting ![]()
Offline
Not sure if there is any way to do that.
It looks like you have some broken device connected somewhere. See if disconnecting external devices helps. If not, it may be onboard. In such case, try disconnecting the PC from power for a minute. Sometimes chips get stuck and a power cycle of the standby rail brings them back.
Offline
resulting in long boot times
Doesn't seem so?
Mar 02 11:34:16 arch kernel: Linux version 6.18.13-arch1-1 (linux@archlinux) (gcc (GCC) 15.2.1 20260209, GNU ld (GNU Binutils) 2.46) #1 SMP PREEMPT_DYNAMIC Wed, 25 Feb 2026 23:12:35 +0000
…
Mar 02 11:34:16 arch kernel: usb 1-8: device not accepting address 7, error -71
Mar 02 11:34:16 arch kernel: usb usb1-port8: unable to enumerate USB device
Mar 02 11:34:16 arch kernel: fbcon: Taking over console
…
Mar 02 11:34:17 arch systemd-logind[615]: New seat seat0.
…
Mar 02 11:34:18 arch systemd[1]: Started Getty on tty1.
…
Mar 02 11:34:25 arch systemd[694]: Started Dunst notification daemon.Slowdown seems to be the DM (lidm?) and you GUI session.
As for the device, probably the bluetooth of the MT wifi chip?
Can you disable that?
Offline
In such case, try disconnecting the PC from power for a minute. Sometimes chips get stuck and a power cycle of the standby rail brings them back.
Sigh, back to my 5 second boot times... I guess nothing really is above "turning off and back on again" is it? Thanks for the help, I appreciate the concise explanation and solution ![]()
Offline
You can now run "dmesg | grep 1-8" or "lsusb -t" (and look for Bus 001 Port 008) if you are curious to see what device it was.
Probably some bluetooth or WiFi as seth said. We have seen a few cases like that before. I think they connect those chips to 5VSB so they can wake up the system from sleep if necessary, but this makes it hard to power cycle them when they go wrong.
Last edited by mmy8x (Today 06:53:11)
Offline
Pages: 1