[solved] How to disable a broken USB port ?

glsarch · 2025-07-26 17:53:37

edit: I had to power off my computer, unplugged it from power, waited a couple of minutes and plugged it in again. This solved the long boot time on Arch.

----------------------------

Hello,

since a couple of weeks now, my BIOS starts a little bit slower than usual (~10s extra) and my Arch takes around 2.5 minutes to boot.

When I check dmesg, I get the following error

 $ sudo dmesg --level=err,warn
...
[    7.375769] usb 1-9: device descriptor read/64, error -110
[   23.247757] usb 1-9: device descriptor read/64, error -110
[   29.391762] usb 1-9: device descriptor read/64, error -110
[   45.263768] usb 1-9: device descriptor read/64, error -110
[   50.613427] usb 1-9: Device not responding to setup address.
[   55.618464] usb 1-9: Device not responding to setup address.
[   55.826639] usb 1-9: device not accepting address 5, error -71
[   61.006298] usb 1-9: Device not responding to setup address.
[   66.011374] usb 1-9: Device not responding to setup address.
[   66.218765] usb 1-9: device not accepting address 6, error -71
[   66.221039] usb usb1-port9: unable to enumerate USB device
...

Is usb 1-9 the Device 001 and Bus 009 when I run lsusb ?

Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I don't have any other combinations of 1 and 9 for the Bus and Device.

Is there a way to tell Arch or the Linux kernel that this port doesn't exist anymore to speed up my boot process ?

$ systemd-analyze time
Startup finished in 32.226s (firmware) + 2.350s (loader) + 2min 2.996s (kernel) + 11.579s (userspace) = 2min 49.153s
graphical.target reached after 11.579s in userspace.

I found this https://bbs.archlinux.org/viewtopic.php?id=297994 what would be the idVendor and idProduct in my case ?

Thanks.

Last edited by glsarch (2025-07-27 09:16:50)

seth · 2025-07-26 19:53:44

what would be the idVendor and idProduct in my case ?

usb usb1-port9: unable to enumerate USB device

Unknown, the device (if there is any) doesn't respond - you'd have to disable the entire hub which is unlikely to be possible (you'd lose every device attached to it)

Are any external usb devices attached? Have you tried to unplug them all?
Is the LTS kernel affected?

glsarch · 2025-07-26 20:05:48

seth wrote:

what would be the idVendor and idProduct in my case ?
usb usb1-port9: unable to enumerate USB device
Unknown, the device (if there is any) doesn't respond - you'd have to disable the entire hub which is unlikely to be possible (you'd lose every device attached to it)
Are any external usb devices attached? Have you tried to unplug them all?
Is the LTS kernel affected?

I only have mouse, keyboard, a USB DAC with my headset. They all work without any problem.

I have the same problem on Windows, I get an error saying that there is an error for a USB port, I can see a problematic device in device manager. I guess the problem is more hardware than a kernel issue (should I still try the LTS kernel?).

I can try to unplug all USB devices I have. I will do that when I boot my computer tomorrow morning.

Thanks for the information.

seth · 2025-07-26 20:12:14

I have the same problem on Windows

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

I only have mouse, keyboard, a USB DAC with my headset. They all work without any problem.

Some, notably the "USB DAC with my headset" might show up as multiple devices. Could also be an internal device - bluetooth? webcam? fingerprint reader?

mmy8x · 2025-07-27 05:00:31

That's the 9th port of the root hub of bus 1, wherever that is. It's not something behind an external hub.

Sometimes motherboards may have USB devices hard-wired on them. You would need dmesg and/or lsusb from a working machine to know what device it is. Search your journal logs for "usb 1-9" or look at linux-hardware.org (seems to be down at the moment).

Not sure if there is any way to blacklist an individual USB port, particularly at boot time. Also not sure why is your boot taking 2.5 minutes. What sort of thing ends up waiting for this bus to complete (or give up) enumerating all devices? Maybe the kernel tries to complete all HW initialization before starting userspace, but not sure.

If it's an onboard device, you could try power cycling the standby supply by completely unplugging the computer from power.

Last edited by mmy8x (2025-07-27 05:30:47)

glsarch · 2025-07-27 08:39:46

seth wrote:

I have the same problem on Windows
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
I only have mouse, keyboard, a USB DAC with my headset. They all work without any problem.
Some, notably the "USB DAC with my headset" might show up as multiple devices. Could also be an internal device - bluetooth? webcam? fingerprint reader?

I disabled fast startup with powercfg /H off as mentioned in your link. It would be weird if it was that because I never had the issue before but thanks.

I booted my computer without any USB plugged in, it was still slow with the BIOS loading, then it automatically started Windows since it is my first entry in the boot loader and I plugged my keyboard to check the device manager and I could still see a problem with one of the USB device.

It is a desktop computer, I don't have a fingerprint reader, nor a webcam. My motherboard is a Gigabyte X870 Aorus elite wifi 7 so I may have bluetooth but I've never used it.

Last edited by glsarch (2025-07-27 08:41:52)

glsarch · 2025-07-27 08:44:58

mmy8x wrote:

That's the 9th port of the root hub of bus 1, wherever that is. It's not something behind an external hub.
Sometimes motherboards may have USB devices hard-wired on them. You would need dmesg and/or lsusb from a working machine to know what device it is. Search your journal logs for "usb 1-9" or look at linux-hardware.org (seems to be down at the moment).
Not sure if there is any way to blacklist an individual USB port, particularly at boot time. Also not sure why is your boot taking 2.5 minutes. What sort of thing ends up waiting for this bus to complete (or give up) enumerating all devices? Maybe the kernel tries to complete all HW initialization before starting userspace, but not sure.

If it's an onboard device, you could try power cycling the standby supply by completely unplugging the computer from power.

Hello,

this long boot for my Arch came after I got the error on Windows saying that there was some problem with one of my USB device/port.
What kind of command should I run to get information about the kernel work here ?

I'll try to completely unplug it from power, thanks.

glsarch · 2025-07-27 09:14:55

mmy8x wrote:

If it's an onboard device, you could try power cycling the standby supply by completely unplugging the computer from power.

Dude. What is this sorcery? Thanks.

My Arch booted normally.

[    0.500932] hub 10-0:1.0: config failed, hub doesn't have any ports! (err -19)
[    0.891290] ata1.00: supports DRM functions and may not be fully accessible
[    0.892185] ata1.00: supports DRM functions and may not be fully accessible
[    1.354666] ata2.00: Model 'Samsung SSD 860 EVO 250GB', rev 'RVT01B6Q', applying quirks: noncqtrim zeroaftertrim noncqonati nolpmonati
[    1.354776] ata2.00: supports DRM functions and may not be fully accessible
[    1.362056] ata2.00: supports DRM functions and may not be fully accessible
[    2.369445] hid-generic 0003:1038:1282.0008: No inputs registered, leaving
[   13.477303] vboxdrv: loading out-of-tree module taints kernel.
[   13.501319] VBoxNetAdp: Successfully started.
[   13.504520] VBoxNetFlt: Successfully started.
[   13.632987] ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\GSA1.SMBI) (20240827/utaddress-204)
[   13.700369] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   21.968095] nvme nvme0: using unchecked data buffer
[   24.136710] warning: `kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[   32.363317] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.

$ systemd-analyze time
Startup finished in 25.814s (firmware) + 1.970s (loader) + 13.001s (kernel) + 11.356s (userspace) = 52.142s 
graphical.target reached after 11.356s in userspace.

It always takes a little bit of time until I need to enter my password to decrypt the disk then it is quick to reach the desktop.

Thanks!

seth · 2025-07-27 09:35:29

common-ish if it's not bad hardware or windows (though might have originally been triggered by the dual boot situation)
See eg https://bbs.archlinux.org/viewtopic.php … 6#p2231006

Ftr: whatt exactly /is/ usb 1-9 now?

glsarch · 2025-07-27 09:57:56

seth wrote:

Ftr: whatt exactly /is/ usb 1-9 now?

I don't know.

I executed lsusb and this is the output

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 048d:5711 Integrated Technology Express, Inc. GIGABYTE Device
Bus 001 Device 003: ID 0489:e124 Foxconn / Hon Hai Wireless_Device
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
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 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 007 Device 003: ID 0451:2036 Texas Instruments, Inc. TUSB2036 Hub
Bus 007 Device 004: ID 1038:1280 SteelSeries ApS SteelSeries GameDAC
Bus 007 Device 005: ID 1038:1282 SteelSeries ApS SteelSeries GameDAC
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 009 Device 003: ID 046d:c24a Logitech, Inc. G600 Gaming Mouse
Bus 009 Device 004: ID 1b1c:1b20 Corsair STRAFE RGB Gaming Keyboard
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

seth · 2025-07-27 10:13:46

sudo journalctl -b | grep -C3 '1-9'

mmy8x · 2025-07-27 11:37:17

glsarch wrote:

seth wrote:
Ftr: whatt exactly /is/ usb 1-9 now?
I don't know.
I executed lsusb and this is the output

There are two devices (besides the root hub itself) on bus 001. If you run "lsusb -t" it will tell which of them is port 009.

Bus 001 Device 002: ID 048d:5711 Integrated Technology Express, Inc. GIGABYTE Device
Bus 001 Device 003: ID 0489:e124 Foxconn / Hon Hai Wireless_Device

glsarch · 2025-07-27 13:35:22

seth wrote:

sudo journalctl -b | grep -C3 '1-9'

Right, sorry.

Jul 27 13:11:45 arch kernel: input: Logitech Gaming Mouse G600 as /devices/pci0000:00/0000:00:08.3/0000:76:00.0/usb9/9-1/9-1.1/9-1.1:1.0/0003:046D:C24A.0003/input/input2
Jul 27 13:11:45 arch kernel: hid-generic 0003:046D:C24A.0003: input,hidraw2: USB HID v1.11 Mouse [Logitech Gaming Mouse G600] on usb-0000:76:00.0-1.1/input0
Jul 27 13:11:45 arch kernel: input: Logitech Gaming Mouse G600 Keyboard as /devices/pci0000:00/0000:00:08.3/0000:76:00.0/usb9/9-1/9-1.1/9-1.1:1.1/0003:046D:C24A.0004/input/input3
Jul 27 13:11:45 arch kernel: usb 1-9: new high-speed USB device number 3 using xhci_hcd
Jul 27 13:11:45 arch kernel: input: Logitech Gaming Mouse G600 as /devices/pci0000:00/0000:00:08.3/0000:76:00.0/usb9/9-1/9-1.1/9-1.1:1.1/0003:046D:C24A.0004/input/input4
Jul 27 13:11:45 arch kernel: hid-generic 0003:046D:C24A.0004: input,hiddev98,hidraw3: USB HID v1.11 Keyboard [Logitech Gaming Mouse G600] on usb-0000:76:00.0-1.1/input1
Jul 27 13:11:45 arch kernel: usb 9-1.4: new full-speed USB device number 4 using xhci_hcd
Jul 27 13:11:45 arch kernel: usb 1-9: New USB device found, idVendor=0489, idProduct=e124, bcdDevice= 1.00
Jul 27 13:11:45 arch kernel: usb 1-9: New USB device strings: Mfr=5, Product=6, SerialNumber=7
Jul 27 13:11:45 arch kernel: usb 1-9: Product: Wireless_Device
Jul 27 13:11:45 arch kernel: usb 1-9: Manufacturer: MediaTek Inc.
Jul 27 13:11:45 arch kernel: usb 1-9: SerialNumber: 000000000
Jul 27 13:11:45 arch kernel: usb 7-2.2.3: new full-speed USB device number 4 using xhci_hcd
Jul 27 13:11:45 arch kernel: usb 7-2.2.3: New USB device found, idVendor=1038, idProduct=1280, bcdDevice= 1.40
Jul 27 13:11:45 arch kernel: usb 7-2.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
--
Jul 27 13:11:45 arch systemd-modules-load[443]: Inserted module 'vboxnetflt'
Jul 27 13:11:45 arch mtp-probe[624]: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:0f:00.0/usb1/1-6"
Jul 27 13:11:45 arch systemd[1]: Finished Load Kernel Modules.
Jul 27 13:11:45 arch mtp-probe[623]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:0f:00.0/usb1/1-9"
Jul 27 13:11:45 arch systemd[1]: Starting Apply Kernel Variables...
Jul 27 13:11:45 arch mtp-probe[629]: checking bus 9, device 3: "/sys/devices/pci0000:00/0000:00:08.3/0000:76:00.0/usb9/9-1/9-1.1"
Jul 27 13:11:45 arch systemd[1]: Finished Create Static Device Nodes in /dev gracefully.

glsarch · 2025-07-27 13:38:18

mmy8x wrote:

glsarch wrote:
seth wrote:
Ftr: whatt exactly /is/ usb 1-9 now?
I don't know.
I executed lsusb and this is the output
There are two devices (besides the root hub itself) on bus 001. If you run "lsusb -t" it will tell which of them is port 009.
Bus 001 Device 002: ID 048d:5711 Integrated Technology Express, Inc. GIGABYTE Device
Bus 001 Device 003: ID 0489:e124 Foxconn / Hon Hai Wireless_Device

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 006: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 006: Dev 002, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 009: Dev 003, If 0, Class=Wireless, Driver=btusb, 480M
    |__ Port 009: Dev 003, If 1, Class=Wireless, Driver=btusb, 480M
    |__ Port 009: Dev 003, If 2, Class=Wireless, Driver=[none], 480M

This part?

I can paste the complete output if that's not the correct one.
with the journalctrl output, it seems related to the WIFI that I don't use, maybe I can disable it in the BIOS. I'll look for the option.

Thanks.

Last edited by glsarch (2025-07-27 13:39:34)

seth · 2025-07-27 13:39:54

Ah. it's a mediatek wifi.
They have this *a lot* (but usually people complain that their wifi device doesn't show up )

mmy8x · 2025-07-27 15:02:01

Looks more like Bluetooth than WiFi.
WiFi should be a PCIe device on this board, as per linux-hardware.

Arch Linux

#1 2025-07-26 17:53:37

[solved] How to disable a broken USB port ?

#2 2025-07-26 19:53:44

Re: [solved] How to disable a broken USB port ?

#3 2025-07-26 20:05:48

Re: [solved] How to disable a broken USB port ?

#4 2025-07-26 20:12:14

Re: [solved] How to disable a broken USB port ?

#5 2025-07-27 05:00:31

Re: [solved] How to disable a broken USB port ?

#6 2025-07-27 08:39:46

Re: [solved] How to disable a broken USB port ?

#7 2025-07-27 08:44:58

Re: [solved] How to disable a broken USB port ?

#8 2025-07-27 09:14:55

Re: [solved] How to disable a broken USB port ?

#9 2025-07-27 09:35:29

Re: [solved] How to disable a broken USB port ?

#10 2025-07-27 09:57:56

Re: [solved] How to disable a broken USB port ?

#11 2025-07-27 10:13:46

Re: [solved] How to disable a broken USB port ?

#12 2025-07-27 11:37:17

Re: [solved] How to disable a broken USB port ?

#13 2025-07-27 13:35:22

Re: [solved] How to disable a broken USB port ?

#14 2025-07-27 13:38:18

Re: [solved] How to disable a broken USB port ?

#15 2025-07-27 13:39:54

Re: [solved] How to disable a broken USB port ?

#16 2025-07-27 15:02:01

Re: [solved] How to disable a broken USB port ?

Board footer