You are not logged in.
Hello everyone,
since yesterday, my system takes a long time to boot. It hangs during the initramfs stage. I can see this in my logs:
Mai 07 12:16:30 archlinux kernel: usb 1-11: device descriptor read/64, error -110
Mai 07 12:16:46 archlinux kernel: usb 1-11: device descriptor read/64, error -110
Mai 07 12:16:46 archlinux kernel: usb 1-11: new full-speed USB device number 3 using xhci_hcd
Mai 07 12:17:02 archlinux kernel: usb 1-11: device descriptor read/64, error -110
Mai 07 12:17:16 archlinux systemd-udevd[398]: usb1: Worker [495] processing SEQNUM=2676 is taking a long time.
Mai 07 12:17:16 archlinux systemd-udevd[398]: usb2: Worker [491] processing SEQNUM=2678 is taking a long time.
Mai 07 12:17:18 archlinux kernel: usb 1-11: device descriptor read/64, error -110
Mai 07 12:17:18 archlinux kernel: usb usb1-port11: attempt power cycle
Mai 07 12:17:18 archlinux kernel: usb 1-11: new full-speed USB device number 4 using xhci_hcd
Mai 07 12:17:23 archlinux kernel: usb 1-11: Device not responding to setup address.
Mai 07 12:17:28 archlinux kernel: usb 1-11: Device not responding to setup address.
Mai 07 12:17:28 archlinux kernel: usb 1-11: device not accepting address 4, error -71
Mai 07 12:17:28 archlinux kernel: usb 1-11: WARN: invalid context state for evaluate context command.
Mai 07 12:17:28 archlinux kernel: usb 1-11: new full-speed USB device number 5 using xhci_hcd
Mai 07 12:17:33 archlinux kernel: usb 1-11: Device not responding to setup address.
Mai 07 12:17:38 archlinux kernel: usb 1-11: Device not responding to setup address.
Mai 07 12:17:39 archlinux kernel: usb 1-11: device not accepting address 5, error -71
Mai 07 12:17:39 archlinux kernel: usb 1-11: WARN: invalid context state for evaluate context command.
Mai 07 12:17:39 archlinux kernel: usb usb1-port11: unable to enumerate USB deviceSo I'm wondering which device is causing this. Because Wifi+Bluetooth, as well as externally plugged (in fact, using every USB port) USB devices work, I suspect this is some internal device.
This is the output of lsusb:
$ lsusb -t
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 012: Dev 006, If 0, Class=Human Interface Device, Driver=usbhid, 12M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 10000M
|__ Port 004: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
/: Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M
|__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 001: Dev 003, If 0, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 001: Dev 003, If 1, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 001: Dev 003, If 2, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 001: Dev 003, If 3, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 001: Dev 003, If 4, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 001: Dev 003, If 5, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 002: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 002: Dev 004, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 003: Dev 005, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 003: Dev 005, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 003: Dev 005, If 2, Class=Human Interface Device, Driver=usbhid, 12M
/: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
|__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M
/: Bus 007.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 006: ID 0db0:0076 Micro Star International MYSTIC LIGHT
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 1058:10b8 Western Digital Technologies, Inc. Elements Portable (WDBU6Y, WDBUZG)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 2109:2815 VIA Labs, Inc. USB2.0 Hub
Bus 005 Device 003: ID 1038:2202 SteelSeries ApS Arctis Nova 7
Bus 005 Device 004: ID 046d:c33a Logitech, Inc. G413 Gaming Keyboard
Bus 005 Device 005: ID 0b05:1960 ASUSTek Computer, Inc. ROG KERIS WIRELESS
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 002: ID 2109:0815 VIA Labs, Inc. USB3.0 Hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 05e3:0608 Genesys Logic, Inc. HubObviously, something is completely broken here as 1-11 isn't even shown. Seeing "Micro Star International MYSTIC LIGHT" at 1-12 strengthens my suspicion that this is probably some internal mainboard management device.
Does anybody have the same mainboard by any chance and could help me out by posting the output of lsusb and lsusb -t in order to confirm this and to have some hint at where I could have a look when I take a look at the mainboard?
Thanks a lot!
Last edited by marcoh00 (2026-05-07 14:26:53)
Offline
as it helped in the past: disconnect EVERYthing from your system - including power - let it sit completely isolated for a few minutes - then reconnect and try again
hint: for some reason usb controllers like to hickup in a way which remains as long as power is provided via +5Vsb and only clear after complete disconnect of everything
Offline
Hi,
thanks that helped. Now that I do have the device id the search results improved a lot! Seems to be a common problem unfortunately...
In case anyone else finds this and not the other posts and reported issues, here's the lsusb output including the offender (0489:e10a)...
$ lsusb
[...]
Bus 001 Device 002: ID 0489:e10a Foxconn / Hon Hai
[...]
$ lsusb -t
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 011: Dev 002, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 011: Dev 002, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 012: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
[...]Related:
https://bbs.archlinux.org/viewtopic.php?id=311779
https://github.com/ublue-os/bazzite/issues/3812
https://discuss.cachyos.org/t/bluetooth … ling/20027
Offline