You are not logged in.

Pages: 1

#1 2024-01-02 21:24:33

0xfMel
Member
Registered: 2022-07-19
Posts: 4

Devices Connected to a USB Hub Resetting Constantly

I recently purchased a powered USB 3.2 Gen 2 USB Hub but I've been having issues using it with Arch.

The issue seems to be that USB devices connected through a USB hub are being reset randomly, and frequently.
I initially noticed the issue as when typing, my keyboard would randomly miss keypresses, or keep a key held down once I had let go.  That accompanied the light on my microphone flashing each time something unexpected happened.
Inspecting the journal shows that USB devices keep getting reset, more recently it's been happening every couple of seconds.

Jan 02 20:57:43 mel-arch kernel: usb 1-7.3: reset full-speed USB device number 8 using xhci_hcd
Jan 02 20:57:44 mel-arch kernel: usb 1-7.3: reset full-speed USB device number 8 using xhci_hcd
Jan 02 20:57:47 mel-arch kernel: usb 1-7.3: reset full-speed USB device number 8 using xhci_hcd
Jan 02 20:57:48 mel-arch kernel: usb 1-2.3.2: reset full-speed USB device number 29 using xhci_hcd
Jan 02 20:57:51 mel-arch kernel: usb 1-7.3: reset full-speed USB device number 8 using xhci_hcd
Jan 02 20:57:55 mel-arch kernel: usb 1-7.3: reset full-speed USB device number 8 using xhci_hcd
Jan 02 20:57:56 mel-arch kernel: usb 1-7.3: reset full-speed USB device number 8 using xhci_hcd
Jan 02 20:57:59 mel-arch kernel: usb 1-7.3: reset full-speed USB device number 8 using xhci_hcd
Jan 02 20:58:01 mel-arch kernel: usb 1-2.3.2: reset full-speed USB device number 29 using xhci_hcd
Jan 02 20:58:01 mel-arch kernel: usb 1-7.3: reset full-speed USB device number 8 using xhci_hcd
Jan 02 20:58:06 mel-arch kernel: usb 1-7.3: reset full-speed USB device number 8 using xhci_hcd
Jan 02 20:58:11 mel-arch kernel: usb 1-7.3: reset full-speed USB device number 8 using xhci_hcd
Jan 02 20:58:20 mel-arch kernel: usb 1-7.3: reset full-speed USB device number 8 using xhci_hcd
Jan 02 20:58:23 mel-arch kernel: usb 1-7.3: reset full-speed USB device number 8 using xhci_hcd

USB Device 8 (usb 1-7.3) is a device inside my tower that I hadn't noticed any issues with, but seems to have always been experiencing this just less frequently.  Looking at lsusb:

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/10p, 480M
    |__ Port 002: Dev 024, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 001: Dev 025, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 001: Dev 025, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 001: Dev 025, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 003: Dev 026, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 001: Dev 028, If 0, Class=Audio, Driver=snd-usb-audio, 480M
            |__ Port 001: Dev 028, If 1, Class=Audio, Driver=snd-usb-audio, 480M
            |__ Port 001: Dev 028, If 2, Class=Application Specific Interface, Driver=[none], 480M
            |__ Port 002: Dev 029, If 0, Class=Audio, Driver=snd-usb-audio, 12M
            |__ Port 002: Dev 029, If 1, Class=Audio, Driver=snd-usb-audio, 12M
            |__ Port 002: Dev 029, If 2, Class=Audio, Driver=snd-usb-audio, 12M
            |__ Port 002: Dev 029, If 3, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 004: Dev 027, If 0, Class=Hub, Driver=hub/4p, 480M
    |__ Port 004: Dev 023, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 004: Dev 023, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 004: Dev 023, If 2, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 007: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 001: Dev 006, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 003: Dev 008, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 003: Dev 008, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 003: Dev 008, If 2, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 010: Dev 005, If 0, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    |__ Port 001: Dev 009, If 0, Class=Hub, Driver=hub/4p, 10000M
        |__ Port 003: Dev 010, If 0, Class=Hub, Driver=hub/4p, 10000M
        |__ Port 004: Dev 011, If 0, Class=Hub, Driver=hub/4p, 10000M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M

Seems to show that it's connected through a USB hub.
When connecting all my peripherals directly to my motherboard, all the peripherals behave correctly but this internal device continues to give these messages.

If I chain another (unpowered) USB hub between my PC and the hub I'm using it gives the following error when I restart, sometimes multiple times with different addresses:

usb 1-2.4.3: device not accepting address 10, error -71

Below is all dmesg lines related to usb during boot:

[    0.000000] Command line: initrd=\amd-ucode.img initrd=\initramfs-linux-zen.img root=UUID=c9056f71-f2b2-46a7-9a7f-35083a10af22 rw nvidia_drm.modeset=1 uinput usbcore.autosuspend=-1
[    0.037055] Kernel command line: initrd=\amd-ucode.img initrd=\initramfs-linux-zen.img root=UUID=c9056f71-f2b2-46a7-9a7f-35083a10af22 rw nvidia_drm.modeset=1 uinput usbcore.autosuspend=-1
[    0.330238] usbcore: registered new interface driver usbfs
[    0.330238] usbcore: registered new interface driver hub
[    0.330238] usbcore: registered new device driver usb
[    0.392372] usbcore: registered new interface driver usbserial_generic
[    0.392377] usbserial: USB Serial support registered for generic
[    5.646242] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    5.646247] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.646249] usb usb1: Product: xHCI Host Controller
[    5.646251] usb usb1: Manufacturer: Linux 6.6.8-zen1-1-zen xhci-hcd
[    5.646253] usb usb1: SerialNumber: 0000:02:00.0
[    5.646975] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    5.647004] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06
[    5.647007] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.647009] usb usb2: Product: xHCI Host Controller
[    5.647011] usb usb2: Manufacturer: Linux 6.6.8-zen1-1-zen xhci-hcd
[    5.647012] usb usb2: SerialNumber: 0000:02:00.0
[    5.647275] usb: port power management may be unreliable
[    5.647878] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    5.647880] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.647881] usb usb3: Product: xHCI Host Controller
[    5.647883] usb usb3: Manufacturer: Linux 6.6.8-zen1-1-zen xhci-hcd
[    5.647884] usb usb3: SerialNumber: 0000:0b:00.3
[    5.648116] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    5.648139] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06
[    5.648141] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.648142] usb usb4: Product: xHCI Host Controller
[    5.648144] usb usb4: Manufacturer: Linux 6.6.8-zen1-1-zen xhci-hcd
[    5.648145] usb usb4: SerialNumber: 0000:0b:00.3
[    5.946290] usb 1-2: new high-speed USB device number 2 using xhci_hcd
[    6.166434] usb 1-2: New USB device found, idVendor=2109, idProduct=2822, bcdDevice=90.14
[    6.166438] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.166440] usb 1-2: Product: USB2.0 Hub
[    6.166442] usb 1-2: Manufacturer: VIA Labs, Inc.
[    6.166444] usb 1-2: SerialNumber: 000000001
[    6.628825] usb 2-1: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci_hcd
[    6.669965] usb 2-1: New USB device found, idVendor=2109, idProduct=0822, bcdDevice=90.14
[    6.669969] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.669971] usb 2-1: Product: USB3.1 Hub
[    6.669972] usb 2-1: Manufacturer: VIA Labs, Inc.
[    6.669974] usb 2-1: SerialNumber: 000000001
[    6.844293] usb 1-4: new full-speed USB device number 3 using xhci_hcd
[    7.210137] usb 1-4: New USB device found, idVendor=3434, idProduct=0162, bcdDevice= 1.02
[    7.210145] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    7.210149] usb 1-4: Product: Keychron Q6
[    7.210152] usb 1-4: Manufacturer: Keychron
[    7.232291] usb 1-2.4: new high-speed USB device number 4 using xhci_hcd
[    7.393319] usb 1-2.4: New USB device found, idVendor=2109, idProduct=2822, bcdDevice= 8.b4
[    7.393324] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    7.393326] usb 1-2.4: Product: USB2.0 Hub
[    7.393328] usb 1-2.4: Manufacturer: VIA Labs, Inc.
[    7.554302] usb 1-7: new high-speed USB device number 5 using xhci_hcd
[    7.766318] usb 1-7: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=60.52
[    7.766324] usb 1-7: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    7.766328] usb 1-7: Product: USB2.0 Hub
[    7.826983] usb 2-1.4: new SuperSpeed Plus Gen 2x1 USB device number 3 using xhci_hcd
[    8.515644] usb 2-1.4: New USB device found, idVendor=2109, idProduct=0822, bcdDevice= 8.b4
[    8.515653] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    8.515657] usb 2-1.4: Product: USB3.1 Hub
[    8.515660] usb 2-1.4: Manufacturer: VIA Labs, Inc.
[    8.689780] usb 1-10: new full-speed USB device number 6 using xhci_hcd
[    8.997420] usb 1-10: New USB device found, idVendor=26ce, idProduct=01a2, bcdDevice= 0.00
[    8.997430] usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    8.997433] usb 1-10: Product: LED Controller
[    8.997436] usb 1-10: Manufacturer: ASRock
[    8.997439] usb 1-10: SerialNumber: A02019100900
[    9.041294] usb 1-7.1: new full-speed USB device number 7 using xhci_hcd
[    9.049862] input: Keychron Keychron Q6 as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-4/1-4:1.0/0003:3434:0162.0001/input/input14
[    9.101473] hid-generic 0003:3434:0162.0001: input,hidraw0: USB HID v1.11 Keyboard [Keychron Keychron Q6] on usb-0000:02:00.0-4/input0
[    9.104833] hid-generic 0003:3434:0162.0002: hiddev96,hidraw1: USB HID v1.11 Device [Keychron Keychron Q6] on usb-0000:02:00.0-4/input1
[    9.111978] input: Keychron Keychron Q6 Mouse as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-4/1-4:1.2/0003:3434:0162.0003/input/input15
[    9.112043] input: Keychron Keychron Q6 System Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-4/1-4:1.2/0003:3434:0162.0003/input/input16
[    9.163363] input: Keychron Keychron Q6 Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-4/1-4:1.2/0003:3434:0162.0003/input/input17
[    9.163424] input: Keychron Keychron Q6 Keyboard as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-4/1-4:1.2/0003:3434:0162.0003/input/input18
[    9.163608] hid-generic 0003:3434:0162.0003: input,hidraw2: USB HID v1.11 Mouse [Keychron Keychron Q6] on usb-0000:02:00.0-4/input2
[    9.176787] input: ASRock LED Controller as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-10/1-10:1.0/0003:26CE:01A2.0004/input/input19
[    9.228381] hid-generic 0003:26CE:01A2.0004: input,hidraw3: USB HID v1.10 Device [ASRock LED Controller] on usb-0000:02:00.0-10/input0
[    9.228408] usbcore: registered new interface driver usbhid
[    9.228410] usbhid: USB HID core driver
[    9.287292] usb 1-2.4.1: new full-speed USB device number 8 using xhci_hcd
[    9.344126] usb 1-7.1: New USB device found, idVendor=1e71, idProduct=2006, bcdDevice= 2.00
[    9.344131] usb 1-7.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    9.344134] usb 1-7.1: Product: NZXT USB Device
[    9.344137] usb 1-7.1: Manufacturer: NZXT. - Inc.
[    9.344139] usb 1-7.1: SerialNumber: 00000000001A
[    9.394142] hid-generic 0003:1E71:2006.0005: hiddev97,hidraw4: USB HID v1.11 Device [NZXT. - Inc. NZXT USB Device] on usb-0000:02:00.0-7.1/input0
[    9.574819] usb 2-1.4.3: new SuperSpeed Plus Gen 2x1 USB device number 4 using xhci_hcd
[    9.613171] usb 1-2.4.1: New USB device found, idVendor=046d, idProduct=c091, bcdDevice=23.01
[    9.613178] usb 1-2.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    9.613182] usb 1-2.4.1: Product: G903 LIGHTSPEED Wireless Gaming Mouse w/ HERO
[    9.613185] usb 1-2.4.1: Manufacturer: Logitech
[    9.613188] usb 1-2.4.1: SerialNumber: 11C9C775
[    9.619210] usb 2-1.4.3: New USB device found, idVendor=2109, idProduct=0822, bcdDevice= 8.b4
[    9.619217] usb 2-1.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    9.619221] usb 2-1.4.3: Product: USB3.1 Hub
[    9.619224] usb 2-1.4.3: Manufacturer: VIA Labs, Inc.
[    9.670448] input: Logitech G903 LIGHTSPEED Wireless Gaming Mouse w/ HERO as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.4/1-2.4.1/1-2.4.1:1.0/0003:046D:C091.0006/input/input20
[    9.670612] hid-generic 0003:046D:C091.0006: input,hidraw5: USB HID v1.11 Mouse [Logitech G903 LIGHTSPEED Wireless Gaming Mouse w/ HERO] on usb-0000:02:00.0-2.4.1/input0
[    9.688697] input: Logitech G903 LIGHTSPEED Wireless Gaming Mouse w/ HERO Keyboard as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.4/1-2.4.1/1-2.4.1:1.1/0003:046D:C091.0007/input/input21
[    9.689298] usb 1-7.3: new full-speed USB device number 9 using xhci_hcd
[    9.740588] hid-generic 0003:046D:C091.0007: input,hidraw6: USB HID v1.11 Keyboard [Logitech G903 LIGHTSPEED Wireless Gaming Mouse w/ HERO] on usb-0000:02:00.0-2.4.1/input1
[    9.756459] hid-generic 0003:046D:C091.0008: hiddev98,hidraw7: USB HID v1.11 Device [Logitech G903 LIGHTSPEED Wireless Gaming Mouse w/ HERO] on usb-0000:02:00.0-2.4.1/input2
[    9.960224] usb 2-1.4.4: new SuperSpeed Plus Gen 2x1 USB device number 5 using xhci_hcd
[    9.990216] usb 1-7.3: New USB device found, idVendor=2516, idProduct=0051, bcdDevice=11.01
[    9.990226] usb 1-7.3: New USB device strings: Mfr=3, Product=1, SerialNumber=0
[    9.990230] usb 1-7.3: Product: AMD SR4 lamplight Control
[    9.990233] usb 1-7.3: Manufacturer: Cooler Master Technology Inc.
[   10.005589] usb 2-1.4.4: New USB device found, idVendor=2109, idProduct=0822, bcdDevice= 8.b4
[   10.005598] usb 2-1.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   10.005602] usb 2-1.4.4: Product: USB3.1 Hub
[   10.005605] usb 2-1.4.4: Manufacturer: VIA Labs, Inc.
[   10.043088] input: Cooler Master Technology Inc. AMD SR4 lamplight Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-7/1-7.3/1-7.3:1.0/0003:2516:0051.0009/input/input22
[   10.072786] usb 1-2.4.3: new high-speed USB device number 10 using xhci_hcd
[   10.094990] hid-generic 0003:2516:0051.0009: input,hidraw8: USB HID v1.11 Keyboard [Cooler Master Technology Inc. AMD SR4 lamplight Control] on usb-0000:02:00.0-7.3/input0
[   10.110624] hid-generic 0003:2516:0051.000A: hiddev99,hidraw9: USB HID v1.11 Device [Cooler Master Technology Inc. AMD SR4 lamplight Control] on usb-0000:02:00.0-7.3/input1
[   10.124009] input: Cooler Master Technology Inc. AMD SR4 lamplight Control System Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-7/1-7.3/1-7.3:1.2/0003:2516:0051.000B/input/input23
[   10.176027] input: Cooler Master Technology Inc. AMD SR4 lamplight Control Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-7/1-7.3/1-7.3:1.2/0003:2516:0051.000B/input/input24
[   10.176265] hid-generic 0003:2516:0051.000B: input,hidraw10: USB HID v1.11 Device [Cooler Master Technology Inc. AMD SR4 lamplight Control] on usb-0000:02:00.0-7.3/input2
[   10.205230] nzxt-smart2 0003:1E71:2006.0005: hidraw4: USB HID v1.11 Device [NZXT. - Inc. NZXT USB Device] on usb-0000:02:00.0-7.1/input0
[   10.426563] usb 1-2.4.3: Device not responding to setup address.
[   10.740612] usb 1-2.4.3: Device not responding to setup address.
[   10.953728] usb 1-2.4.3: device not accepting address 10, error -71
[   11.031757] usb 1-2.4.3: new high-speed USB device number 11 using xhci_hcd
[   11.144098] usb 1-2.4.3: New USB device found, idVendor=2109, idProduct=2822, bcdDevice= 8.b4
[   11.144109] usb 1-2.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   11.144112] usb 1-2.4.3: Product: USB2.0 Hub
[   11.144116] usb 1-2.4.3: Manufacturer: VIA Labs, Inc.
[   12.013793] usb 1-2.4.4: new high-speed USB device number 12 using xhci_hcd
[   12.125011] usb 1-2.4.4: New USB device found, idVendor=2109, idProduct=2822, bcdDevice= 8.b4
[   12.125022] usb 1-2.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   12.125025] usb 1-2.4.4: Product: USB2.0 Hub
[   12.125028] usb 1-2.4.4: Manufacturer: VIA Labs, Inc.
[   12.344456] input: Logitech G903 LIGHTSPEED Wireless Gaming Mouse w/ HERO as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.4/1-2.4.1/1-2.4.1:1.0/0003:046D:C091.0006/input/input25
[   12.344542] logitech-hidpp-device 0003:046D:C091.0006: input,hidraw5: USB HID v1.11 Mouse [Logitech G903 LIGHTSPEED Wireless Gaming Mouse w/ HERO] on usb-0000:02:00.0-2.4.1/input0
[   12.417915] input: Logitech G903 LIGHTSPEED Wireless Gaming Mouse w/ HERO as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.4/1-2.4.1/1-2.4.1:1.1/0003:046D:C091.0007/input/input26
[   12.469565] logitech-hidpp-device 0003:046D:C091.0007: input,hidraw6: USB HID v1.11 Keyboard [Logitech G903 LIGHTSPEED Wireless Gaming Mouse w/ HERO] on usb-0000:02:00.0-2.4.1/input1
[   12.491298] usb 1-2.4.3.1: new high-speed USB device number 13 using xhci_hcd
[   12.608830] usb 1-2.4.3.1: New USB device found, idVendor=152a, idProduct=8750, bcdDevice= 1.04
[   12.608836] usb 1-2.4.3.1: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[   12.608839] usb 1-2.4.3.1: Product: D10s
[   12.608842] usb 1-2.4.3.1: Manufacturer: Topping
[   12.695294] usb 1-2.4.3.2: new full-speed USB device number 14 using xhci_hcd
[   12.706252] logitech-hidpp-device 0003:046D:C091.0008: hiddev97,hidraw7: USB HID v1.11 Device [Logitech G903 LIGHTSPEED Wireless Gaming Mouse w/ HERO] on usb-0000:02:00.0-2.4.1/input2
[   12.952806] usb 1-2.4.3.2: New USB device found, idVendor=1532, idProduct=0511, bcdDevice= 1.00
[   12.952815] usb 1-2.4.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   12.952819] usb 1-2.4.3.2: Product: Razer Seiren X
[   12.952822] usb 1-2.4.3.2: Manufacturer: Razer Inc
[   12.952825] usb 1-2.4.3.2: SerialNumber: UC2016L01204967
[   13.003141] input: Razer Inc Razer Seiren X Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.4/1-2.4.3/1-2.4.3.2/1-2.4.3.2:1.3/0003:1532:0511.000C/input/input27
[   13.054627] hid-generic 0003:1532:0511.000C: input,hiddev98,hidraw11: USB HID v1.00 Device [Razer Inc Razer Seiren X] on usb-0000:02:00.0-2.4.3.2/input3
[   13.254781] usb 1-2.4.3.1: 1:3 : unsupported format bits 0x100000000
[   13.906103] usbcore: registered new interface driver snd-usb-audio

Booting my desktop into Windows without changing the USB device configuration works flawlessly, works fine as well with an Ubuntu live USB, so not a hardware issue.
Issue exists as well for the Arch live USB, so not just an issue with my current installation.

I've tried a few things like adding usbcore.autosuspend=-1 to my kernal params but that hasn't helped.  Everything I can find online appears to be unrelated or some hardware issue.
Pretty stumped don't know what else to try at this point, any help would be appreciated.  Thanks

Offline

#2 2024-01-02 22:26:03

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: Devices Connected to a USB Hub Resetting Constantly

Booting my desktop into Windows

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

tried a few things like adding usbcore.autosuspend=-1 to my kernal

"kernEl", wtf does this "kernAl" thing come from?
On topic: nb. that userspace tools like TLP can and will change the autosuspend at runtime so you have to change the config there (as well)
You might as well just install TLP and have it configure this for you (there've actually been success reports about such approach, though it seems like voodoo)

Have you tried a non-zen kernel (regular or LTS one)?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2024-04-08 14:06:06

brilthor
Member
Registered: 2016-04-24
Posts: 4

Re: Devices Connected to a USB Hub Resetting Constantly

I'm facing a similar/same issue, some current notes in case they are helpful

  • Specifically HID devices seem to be causing the issue (there might be others that I'm just not seeing, or some other connection), I switched my mouse and keyboard to a couple older units, same issue.

  • This machine does not dual-boot, so windows fast start would not be related tongue

  • This feels like it's become and issue / more of an issue on recent kernels

here is the current USB device tree for reference, devices 023 and 022 are the ones resetting

I am seeing similar behavior, s
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/10p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 002: Dev 099, If 0, Class=Hub, Driver=hub/1p, 480M
        ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
        |__ Port 001: Dev 100, If 0, Class=Hub, Driver=hub/1p, 480M
            ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
            |__ Port 001: Dev 012, If 0, Class=Hub, Driver=hub/4p, 480M
                ID 2109:2812 VIA Labs, Inc. VL812 Hub
                |__ Port 003: Dev 013, If 0, Class=Hub, Driver=hub/4p, 480M
                    ID 2109:2812 VIA Labs, Inc. VL812 Hub
                    |__ Port 001: Dev 023, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
                        ID 045e:00dd Microsoft Corp. Comfort Curve Keyboard 2000 V1.0
                    |__ Port 001: Dev 023, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
                        ID 045e:00dd Microsoft Corp. Comfort Curve Keyboard 2000 V1.0
                    |__ Port 002: Dev 014, If 0, Class=Hub, Driver=hub/4p, 480M
                        ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 "TetraHub"
                        |__ Port 004: Dev 020, If 0, Class=Wireless, Driver=btusb, 12M
                            ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
                        |__ Port 004: Dev 020, If 1, Class=Wireless, Driver=btusb, 12M
                            ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
                    |__ Port 003: Dev 015, If 0, Class=Hub, Driver=hub/4p, 480M
                        ID 050d:0233 Belkin Components 
                        |__ Port 001: Dev 018, If 0, Class=Audio, Driver=snd-usb-audio, 12M
                            ID 0c76:1648 JMTek, LLC. 
                        |__ Port 001: Dev 018, If 1, Class=Audio, Driver=snd-usb-audio, 12M
                            ID 0c76:1648 JMTek, LLC. 
                        |__ Port 001: Dev 018, If 2, Class=Human Interface Device, Driver=usbhid, 12M
                            ID 0c76:1648 JMTek, LLC. 
                        |__ Port 004: Dev 022, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
                            ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
                    |__ Port 004: Dev 017, If 0, Class=Human Interface Device, Driver=usbhid, 12M
                        ID 1852:50d0 GYROCOM C&C Co., LTD 
                    |__ Port 004: Dev 017, If 1, Class=Audio, Driver=snd-usb-audio, 12M
                        ID 1852:50d0 GYROCOM C&C Co., LTD 
                    |__ Port 004: Dev 017, If 3, Class=Audio, Driver=snd-usb-audio, 12M
                        ID 1852:50d0 GYROCOM C&C Co., LTD 
    |__ Port 006: Dev 002, If 0, Class=Vendor Specific Class, Driver=[none], 12M
        ID 0b05:1939 ASUSTek Computer, Inc. 
    |__ Port 006: Dev 002, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        ID 0b05:1939 ASUSTek Computer, Inc. 
    |__ Port 007: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 05e3:0608 Genesys Logic, Inc. Hub
    |__ Port 009: Dev 098, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        ID 0624:0307 Avocent Corp. 
    |__ Port 009: Dev 098, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
        ID 0624:0307 Avocent Corp. 
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/1p, 5000M
        ID 0bda:0411 Realtek Semiconductor Corp. Hub
        |__ Port 001: Dev 003, If 0, Class=Hub, Driver=hub/1p, 5000M
            ID 0bda:0411 Realtek Semiconductor Corp. Hub
            |__ Port 001: Dev 010, If 0, Class=Hub, Driver=hub/4p, 5000M
                ID 2109:0812 VIA Labs, Inc. VL812 Hub
                |__ Port 001: Dev 011, If 0, Class=Vendor Specific Class, Driver=[none], 5000M
                    ID 17e9:4307 DisplayLink 
                |__ Port 001: Dev 011, If 1, Class=Application Specific Interface, Driver=[none], 5000M
                    ID 17e9:4307 DisplayLink 
                |__ Port 001: Dev 011, If 2, Class=Audio, Driver=snd-usb-audio, 5000M
                    ID 17e9:4307 DisplayLink 
                |__ Port 001: Dev 011, If 3, Class=Audio, Driver=snd-usb-audio, 5000M
                    ID 17e9:4307 DisplayLink 
                |__ Port 001: Dev 011, If 4, Class=Audio, Driver=snd-usb-audio, 5000M
                    ID 17e9:4307 DisplayLink 
                |__ Port 001: Dev 011, If 5, Class=Communications, Driver=cdc_ncm, 5000M
                    ID 17e9:4307 DisplayLink 
                |__ Port 001: Dev 011, If 6, Class=CDC Data, Driver=cdc_ncm, 5000M
                    ID 17e9:4307 DisplayLink 
                |__ Port 003: Dev 012, If 0, Class=Hub, Driver=hub/4p, 5000M
                    ID 2109:0812 VIA Labs, Inc. VL812 Hub
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 001: Dev 002, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M
        ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port / Mobile Phone Data Cable
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub

Offline

#4 2024-04-08 15:24:29

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: Devices Connected to a USB Hub Resetting Constantly

There were BT related issues in some 6.8 kernels, do you experience this if you remove the BT dongle (which is on the relevant bus…) and have you tried the behavior on the 6.8.4 kernel?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2024-04-08 15:45:20

brilthor
Member
Registered: 2016-04-24
Posts: 4

Re: Devices Connected to a USB Hub Resetting Constantly

seth wrote:

There were BT related issues in some 6.8 kernels, do you experience this if you remove the BT dongle (which is on the relevant bus…)

Yes, since the bt was on the same hub as the mouse it was one of the first things I tried, unfortunately it doesn't appear to be related

seth wrote:

and have you tried the behavior on the 6.8.4 kernel?

I haven't jumped around kernel versions yet, it's on my list to try when I have a maintenance window, @0xfMel did you get to the point of trying different kernel versions?

Offline

#6 2024-04-08 16:07:00

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: Devices Connected to a USB Hub Resetting Constantly

6.8.4 is the current default kernel, https://archlinux.org/packages/core/x86_64/linux/ and the OPs issue predated the bluetooth problems.
Please post your complete system journal for a boot w/ reconnects: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2024-04-08 17:43:13

brilthor
Member
Registered: 2016-04-24
Posts: 4

Re: Devices Connected to a USB Hub Resetting Constantly

seth wrote:

6.8.4 is the current default kernel, https://archlinux.org/packages/core/x86_64/linux/

yup, up to date

# uname -a
Linux maindesktop 6.8.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 05 Apr 2024 00:14:23 +0000 x86_64 GNU/Linux
seth wrote:

Please post your complete system journal for a boot w/ reconnects: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

this file is ~40MB, which is quite a lot to redact, it can be done if needed, however is there something I can look specifically in it for you?

Also:
Switched the controller I was plugged into; the issue appears to have gone away

new:

30:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

old:

03:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset USB 3.1 XHCI Controller

Offline

#8 2024-04-09 21:53:45

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: Devices Connected to a USB Hub Resetting Constantly

From your previous post:

    ID 1d6b:0002 Linux Foundation 2.0 root hub
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    ID 1d6b:0003 Linux Foundation 3.0 root hub

Are you sure you've ever witnessed the behavior w/ the 6.8.4 kernel (can you trigger it by switching the usb controller again)?

If a journal for a single boot is 40MB, here's probably something severely wrong (of you've a bunch of kernel debug options enabled?)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2024-05-21 21:55:23

jocris
Member
Registered: 2024-02-19
Posts: 9

Re: Devices Connected to a USB Hub Resetting Constantly

I have noticed a similar issue with Kingston DataTraveler G2 USB flash drive

  • Issue occurs on Linux 6.9.1-arch1-1

  • Issue does not occur on Linux 6.6.31-1-lts

Journal kernel logs (working & non-working kernel)

Last edited by jocris (2024-05-21 21:56:07)

Offline

#10 2024-05-23 16:02:08

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: Devices Connected to a USB Hub Resetting Constantly

May 21 21:42:47 oldell kernel: usb-storage 1-1.3:1.0: USB Mass Storage device detected
May 21 21:42:47 oldell kernel: scsi host6: usb-storage 1-1.3:1.0
May 21 21:42:47 oldell kernel: usbcore: registered new interface driver usb-storage
May 21 21:42:47 oldell kernel: usbcore: registered new interface driver uas
May 21 21:42:48 oldell kernel: scsi 6:0:0:0: Direct-Access     Kingston DataTraveler G2  1.00 PQ: 0 ANSI: 2
May 21 21:42:48 oldell kernel: sd 6:0:0:0: [sdb] 15654848 512-byte logical blocks: (8.02 GB/7.46 GiB)
May 21 21:42:48 oldell kernel: sd 6:0:0:0: [sdb] Write Protect is off
May 21 21:42:48 oldell kernel: sd 6:0:0:0: [sdb] Mode Sense: 16 24 09 51
May 21 21:42:48 oldell kernel: sd 6:0:0:0: [sdb] Incomplete mode parameter data
May 21 21:42:48 oldell kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
May 21 21:42:48 oldell kernel: usb 1-1.3: reset high-speed USB device number 4 using ehci-pci
May 21 21:42:48 oldell kernel: usb 1-1.3: reset high-speed USB device number 4 using ehci-pci
May 21 21:42:48 oldell kernel: usb 1-1.3: reset high-speed USB device number 4 using ehci-pci
May 21 21:42:48 oldell kernel: usb 1-1.3: reset high-speed USB device number 4 using ehci-pci
May 21 21:42:48 oldell kernel: usb 1-1.3: reset high-speed USB device number 4 using ehci-pci
May 21 21:42:49 oldell kernel: usb 1-1.3: reset high-speed USB device number 4 using ehci-pci
May 21 21:42:49 oldell kernel: usb 1-1.3: reset high-speed USB device number 4 using ehci-pci
May 21 21:42:49 oldell kernel: usb 1-1.3: reset high-speed USB device number 4 using ehci-pci
May 21 21:42:49 oldell kernel: usb 1-1.3: reset high-speed USB device number 4 using ehci-pci
May 21 21:42:49 oldell kernel: usb 1-1.3: reset high-speed USB device number 4 using ehci-pci
May 21 21:42:49 oldell kernel: usb 1-1.3: reset high-speed USB device number 4 using ehci-pci
May 21 21:42:50 oldell kernel: usb 1-1.3: reset high-speed USB device number 4 using ehci-pci
May 21 21:42:50 oldell kernel: sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
May 21 21:42:50 oldell kernel: sd 6:0:0:0: [sdb] tag#0 Sense Key : Unit Attention [current] 
May 21 21:42:50 oldell kernel: sd 6:0:0:0: [sdb] tag#0 Add. Sense: Not ready to ready change, medium may have changed
May 21 21:42:50 oldell kernel: sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00

The device has issues from the get-go, so it's probably not autosuspend.
Does it behave more stable on a different USB port? The one where bluetooth isn't attached (nb. that the bus order changes between the boots usb1 and usb2 swap their posittions)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2024-05-23 19:19:17

jocris
Member
Registered: 2024-02-19
Posts: 9

Re: Devices Connected to a USB Hub Resetting Constantly

Tried all USB ports, same problem on the new kernel. It never stabilize.
Not all USB drives are affected, for example this one works fine on the new kernel:

May 23 20:15:37 oldell kernel: usb 2-1.2: new high-speed USB device number 9 using ehci-pci
May 23 20:15:37 oldell kernel: usb 2-1.2: New USB device found, idVendor=6557, idProduct=2031, bcdDevice= 1.10
May 23 20:15:37 oldell kernel: usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 23 20:15:37 oldell kernel: usb 2-1.2: Product: USB DISK 3.0
May 23 20:15:37 oldell kernel: usb 2-1.2: Manufacturer:         
May 23 20:15:37 oldell kernel: usb 2-1.2: SerialNumber: 070D393C83CB5024
May 23 20:15:37 oldell kernel: usb-storage 2-1.2:1.0: USB Mass Storage device detected
May 23 20:15:37 oldell kernel: scsi host6: usb-storage 2-1.2:1.0
May 23 20:15:37 oldell mtp-probe[2300]: checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2"
May 23 20:15:37 oldell mtp-probe[2300]: bus: 2, device: 9 was not an MTP device
May 23 20:15:37 oldell mtp-probe[2301]: checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2"
May 23 20:15:37 oldell mtp-probe[2301]: bus: 2, device: 9 was not an MTP device
May 23 20:15:38 oldell kernel: scsi 6:0:0:0: Direct-Access              USB DISK 3.0     PMAP PQ: 0 ANSI: 6
May 23 20:15:39 oldell kernel: sd 6:0:0:0: [sdb] 121145344 512-byte logical blocks: (62.0 GB/57.8 GiB)
May 23 20:15:39 oldell kernel: sd 6:0:0:0: [sdb] Write Protect is off
May 23 20:15:39 oldell kernel: sd 6:0:0:0: [sdb] Mode Sense: 45 00 00 00
May 23 20:15:39 oldell kernel: sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
May 23 20:15:39 oldell kernel:  sdb: sdb1 sdb2
May 23 20:15:39 oldell kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk

Offline

#12 2024-05-23 20:38:53

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: Devices Connected to a USB Hub Resetting Constantly

Devices get reset to bail out of communication errors and the later errors support that as well.
It could be a driver bug, but you're having that on ehci while the OP faces xhci resets, so I suspected it's more a side-effect from powersaving/interference/noise on the bus but apparently not.

But the OP got this on 6.6.8-zen, then brilthor on some undisclosed but likely 6.8.x kernel  and  you're facing the only recorded regression between the 6.6.31 and 6.9.1 kernels
=> Test the behavior on the latest 6.8 kernel(s), https://wiki.archlinux.org/title/Arch_Linux_Archive - downgrading the kernel in isolation is fine, but don't forget to also downgrade OOT modules (nvidia, virtualbox, …) or use their DKMS variants.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#13 2024-05-23 22:21:26

jocris
Member
Registered: 2024-02-19
Posts: 9

Re: Devices Connected to a USB Hub Resetting Constantly

linux 6.8.9-arch1-2 is good:

ay 23 23:18:47 oldell kernel: usb 1-1.2: new high-speed USB device number 4 using ehci-pci
May 23 23:18:48 oldell kernel: usb 1-1.2: New USB device found, idVendor=0951, idProduct=1624, bcdDevice= 1.00
May 23 23:18:48 oldell kernel: usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 23 23:18:48 oldell kernel: usb 1-1.2: Product: DataTraveler G2
May 23 23:18:48 oldell kernel: usb 1-1.2: Manufacturer: Kingston
May 23 23:18:48 oldell kernel: usb 1-1.2: SerialNumber: 0014780F9955F971A5EC08D7
May 23 23:18:48 oldell mtp-probe[1063]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.2"
May 23 23:18:48 oldell mtp-probe[1063]: bus: 1, device: 4 was not an MTP device
May 23 23:18:48 oldell kernel: usb-storage 1-1.2:1.0: USB Mass Storage device detected
May 23 23:18:48 oldell kernel: scsi host6: usb-storage 1-1.2:1.0
May 23 23:18:48 oldell kernel: usbcore: registered new interface driver usb-storage
May 23 23:18:48 oldell kernel: usbcore: registered new interface driver uas
May 23 23:18:48 oldell mtp-probe[1071]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.2"
May 23 23:18:48 oldell mtp-probe[1071]: bus: 1, device: 4 was not an MTP device
May 23 23:18:49 oldell kernel: scsi 6:0:0:0: Direct-Access     Kingston DataTraveler G2  1.00 PQ: 0 ANSI: 2
May 23 23:18:49 oldell kernel: sd 6:0:0:0: [sdb] 15654848 512-byte logical blocks: (8.02 GB/7.46 GiB)
May 23 23:18:49 oldell kernel: sd 6:0:0:0: [sdb] Write Protect is off
May 23 23:18:49 oldell kernel: sd 6:0:0:0: [sdb] Mode Sense: 16 24 09 51
May 23 23:18:49 oldell kernel: sd 6:0:0:0: [sdb] Incomplete mode parameter data
May 23 23:18:49 oldell kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
May 23 23:18:49 oldell kernel:  sdb: sdb1
May 23 23:18:49 oldell kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk

Offline

#14 2024-05-24 06:38:26

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: Devices Connected to a USB Hub Resetting Constantly

So it's a 6.9 regression, pot. limited to the ehci module.
If it doesn't go away w/ one of the next updates, you'll have to bisect the kernel.
loqs migth still have some commits pre-built that you could use as starting point.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#15 2024-05-25 22:22:27

jocris
Member
Registered: 2024-02-19
Posts: 9

Re: Devices Connected to a USB Hub Resetting Constantly

Thanks seth for the tips.
Using git-bisect narrowed it down to this 1st bad commit:

commit 4f53138fffc2b18396859aa4ff3e7ef2b0839c2b
Author: Bart Van Assche <bvanassche@acm.org>
Date:   Tue Jan 30 13:48:37 2024 -0800

    scsi: sd: Translate data lifetime information
    
    Recently T10 standardized SBC constrained streams. This mechanism allows to
    pass data lifetime information to SCSI devices in the group number field.
    Add support for translating write hint information into a permanent stream
    number in the sd driver. Use WRITE(10) instead of WRITE(6) if data lifetime
    information is present because the WRITE(6) command does not have a GROUP
    NUMBER field.
    
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Damien Le Moal <dlemoal@kernel.org>
    Signed-off-by: Bart Van Assche <bvanassche@acm.org>
    Link: https://lore.kernel.org/r/20240130214911.1863909-12-bvanassche@acm.org
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

But didn't figure out what could be the relationship to the reset loop

Offline

#16 2024-05-26 08:00:08

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: Devices Connected to a USB Hub Resetting Constantly

But didn't figure out what could be the relationship to the reset loop

https://en.wikipedia.org/wiki/USB_Attached_SCSI
See eg. https://bugzilla.kernel.org/show_bug.cgi?id=215333

Did you check a kernel w/ only that patch reverted as cross check?
If so, mail Bart and CC Martin and linux-scsi@vger.kernel.org with your findings. Indicate that you need to be CC'd in replies.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#17 2024-05-26 08:48:07

jocris
Member
Registered: 2024-02-19
Posts: 9

Re: Devices Connected to a USB Hub Resetting Constantly

seth wrote:

Did you check a kernel w/ only that patch reverted as cross check?

I tested with the parent commit (4977c0f4523e1d6c87df4eedceb33d38f055c5fb) -  the issue does not occur. is that what you were asking?

Offline

#18 2024-05-26 09:03:26

seth
Member
Registered: 2012-09-03
Posts: 59,882

Re: Devices Connected to a USB Hub Resetting Constantly

Yup, it's just a cross test to really pin the culprit.
Edit: apparently my brain rebooted - no: the idea is to only revert that commit to really pin the culprit.

You'll then have to mail the relevant kernel developers - it's likely that some HW responds badly to the group field or the changed write command but the assessment and pot. mitigation strategies will require very specialized knowledge of the protocol and implementation.

Last edited by seth (2024-05-26 09:04:40)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#19 2024-06-23 10:33:40

the_sakinai
Member
Registered: 2024-06-23
Posts: 2

Re: Devices Connected to a USB Hub Resetting Constantly

jocris wrote:
seth wrote:

Did you check a kernel w/ only that patch reverted as cross check?

I tested with the parent commit (4977c0f4523e1d6c87df4eedceb33d38f055c5fb) -  the issue does not occur. is that what you were asking?

Hi, did you follow-up with this?

I'm sorry to bump this thread, but I'm facing the same problem, and symptoms, with two devices resetting:
1. Bus 001 Device 011: ID 3434:0251 Keychron Keychron K5 Pro
2. Bus 001 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver

I've tested with kernels versions 6.8.* to 6.10.*, and with:
1. Arch (install)
2. Fedora (install and livecd)
3. Mint (livecd, kernel 5.15.0-91)

I also tried unplugging the devices individually.

I'm not sure where else to go for debugging this issue or it's a matter of waiting until the culprit commit that you found is looked at (where would I go to track it?)

[  309.817139] usb 1-1.3: reset full-speed USB device number 11 using xhci_hcd
[  310.284973] usb 1-1.2: reset full-speed USB device number 7 using xhci_hcd
[  311.185137] usb 1-1.3: reset full-speed USB device number 11 using xhci_hcd
[  311.704281] usb 1-1.2: reset full-speed USB device number 7 using xhci_hcd
[  312.761142] usb 1-1.3: reset full-speed USB device number 11 using xhci_hcd
[  313.144308] usb 1-1.2: reset full-speed USB device number 7 using xhci_hcd
[  314.169103] usb 1-1.3: reset full-speed USB device number 11 using xhci_hcd
[  314.796931] usb 1-1.2: reset full-speed USB device number 7 using xhci_hcd
[  315.856761] usb 1-1.3: reset full-speed USB device number 11 using xhci_hcd
[  317.180914] usb 1-1.2: reset full-speed USB device number 7 using xhci_hcd
[  323.352963] usb 1-1.3: reset full-speed USB device number 11 using xhci_hcd
[  334.312635] usb 1-1.3: reset full-speed USB device number 11 using xhci_hcd
[  347.796849] usb 1-1.3: reset full-speed USB device number 11 using xhci_hcd
[  348.260013] usb 1-1.2: reset full-speed USB device number 7 using xhci_hcd
[  354.148132] usb 1-1.3: reset full-speed USB device number 11 using xhci_hcd
[  355.912791] usb 1-1.3: reset full-speed USB device number 11 using xhci_hcd
[  360.168636] usb 1-1.3: reset full-speed USB device number 11 using xhci_hcd
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 3: Dev 11, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 3: Dev 11, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 3: Dev 11, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 1: Dev 4, If 2, Class=Audio, Driver=snd-usb-audio, 480M
        |__ Port 1: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M
        |__ Port 1: Dev 4, If 3, Class=Audio, Driver=snd-usb-audio, 480M
        |__ Port 1: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M
        |__ Port 4: Dev 15, If 2, Class=Audio, Driver=snd-usb-audio, 480M
        |__ Port 4: Dev 15, If 0, Class=Audio, Driver=snd-usb-audio, 480M
        |__ Port 4: Dev 15, If 3, Class=Vendor Specific Class, Driver=, 480M
        |__ Port 4: Dev 15, If 1, Class=Audio, Driver=snd-usb-audio, 480M
        |__ Port 2: Dev 7, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 2: Dev 7, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 2: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/3p, 480M
        |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/7p, 480M
            |__ Port 1: Dev 10, If 1, Class=Human Interface Device, Driver=usbhid, 12M
            |__ Port 1: Dev 10, If 0, Class=Human Interface Device, Driver=usbhid, 12M
            |__ Port 6: Dev 18, If 0, Class=Human Interface Device, Driver=usbhid, 12M
            |__ Port 2: Dev 14, If 5, Class=Audio, Driver=snd-usb-audio, 480M
            |__ Port 2: Dev 14, If 3, Class=Audio, Driver=snd-usb-audio, 480M
            |__ Port 2: Dev 14, If 1, Class=Video, Driver=uvcvideo, 480M
            |__ Port 2: Dev 14, If 4, Class=Audio, Driver=snd-usb-audio, 480M
            |__ Port 2: Dev 14, If 2, Class=Audio, Driver=snd-usb-audio, 480M
            |__ Port 2: Dev 14, If 0, Class=Video, Driver=uvcvideo, 480M
            |__ Port 7: Dev 19, If 0, Class=Human Interface Device, Driver=usbhid, 12M
            |__ Port 5: Dev 17, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 2: Dev 9, If 3, Class=Application Specific Interface, Driver=, 12M
        |__ Port 2: Dev 9, If 1, Class=Vendor Specific Class, Driver=btusb, 12M
        |__ Port 2: Dev 9, If 2, Class=Vendor Specific Class, Driver=btusb, 12M
        |__ Port 2: Dev 9, If 0, Class=Vendor Specific Class, Driver=btusb, 12M
        |__ Port 3: Dev 13, If 0, Class=Communications, Driver=cdc_acm, 480M
        |__ Port 3: Dev 13, If 1, Class=CDC Data, Driver=cdc_acm, 480M
    |__ Port 3: Dev 5, If 2, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 3: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 3: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 4: Dev 8, If 0, Class=Mass Storage, Driver=usb-storage, 480M
    |__ Port 5: Dev 20, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 5: Dev 20, If 1, Class=Wireless, Driver=btusb, 12M
    |__ Port 6: Dev 16, If 2, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 6: Dev 16, If 0, Class=Vendor Specific Class, Driver=, 12M

Offline

#20 2024-06-23 20:25:49

jocris
Member
Registered: 2024-02-19
Posts: 9

Re: Devices Connected to a USB Hub Resetting Constantly

My issue was resolved on kernel 6.9.5. This commit fixed it:

24b70ff usb: Do not query the IO advice hints grouping mode page for USB devices

Do you know a kernel version where your devices run fine? Do them run fine on windows?

Offline

#21 2024-06-23 21:59:09

the_sakinai
Member
Registered: 2024-06-23
Posts: 2

Re: Devices Connected to a USB Hub Resetting Constantly

Thanks for the info! And I'm glad you got it fixed!

My devices do run fine on Win10 and MacOS, exact same setup.

This issue doesn't happen in 6.1.21-v8+ (on my RPI).

I'm out of options on what to do next. If you have any suggestions, feel free to send them my way.

Thanks again.

Last edited by the_sakinai (2024-06-23 22:01:22)

Offline

#22 2024-06-24 20:53:15

jocris
Member
Registered: 2024-02-19
Posts: 9

Re: Devices Connected to a USB Hub Resetting Constantly

Its weird its working on 6.1.21-v8+ but not in 5.15.0-91 or 6.8.x.
I suggest to first bisect kernel using pre compiled kernel versions to find which release introduce the issue.
Once you find the release that introduces the issue, next step is to bisect the kernel commits between the closest bad and good release using git-bisect tool. This is very time consuming because you need to recompile the kernel on each step. I used linux-mainline-git AUR package for the kernel source.

Hint to make the process faster:
- use qemu with USB redirection to test each release/commit.
- before compiling, set kernel config to use just the required modules for qemu vm. this is done with make localmodconfig + the lsmod output from the qemu vm + LSMOD parameter. you can find more info here https://www.kernel.org/doc/readme/Docum … README.rst

Offline

Pages: 1

Board footer

Powered by FluxBB