USB3 Device Connection Issues

mbanducci · June 30, 2022, 1:25am

I’m having a new, weird problem that I can’t figure out. I’m not sure if it’s something with my particular collection of hardware or if I’m actually seeing a bug.

I have 4 devices (mouse, dac, audio interface, keyboard) that I switch between two machines using a usb3.0 switcher. The switcher is a 4-port self-powered hub with 2 host connections and a button to swap between them.

In the last month or so, when the system boots, I experience the following:

UEFI and Plymouth work normally
Gnome login works normally
Once logged in, the keyboard disconnects and I have to unplug+replug to get it to reappear

I see all kinds of stuff in dmesg:

[   19.722889] usb 5-3.2: 3:1: cannot get freq at ep 0x82
[   20.363909] usb 5-3.3: 1:1: cannot get freq at ep 0x1
[   20.427020] usb 5-3.3: 1:1: cannot get freq at ep 0x1
[   20.745018] Bluetooth: RFCOMM TTY layer initialized
[   20.745022] Bluetooth: RFCOMM socket layer initialized
[   20.745039] Bluetooth: RFCOMM ver 1.11
[   58.842743] rfkill: input handler enabled
[   59.932543] rfkill: input handler disabled
[   61.664675] usb 5-3.1: USB disconnect, device number 4
[   61.828924] usb 5-3.2: USB disconnect, device number 6
[   61.829480] usb 5-3.3: USB disconnect, device number 7
[   61.830008] usb 5-3.4: USB disconnect, device number 9
[   61.830012] usb 5-3.4.4: USB disconnect, device number 10
[   62.519438] hub 5-3:1.0: USB hub found
[   62.519948] hub 5-3:1.0: 4 ports detected
[   63.065892] hub 5-3:1.0: USB hub found
[   63.066202] hub 5-3:1.0: 4 ports detected
[   63.285699] usb 5-3.1: new full-speed USB device number 11 using xhci_hcd
[   63.382850] usb 5-3.1: New USB device found, idVendor=1e7d, idProduct=2c88, bcdDevice= 1.01
[   63.382853] usb 5-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   63.382854] usb 5-3.1: Product: ROCCAT Kone Pro
[   63.382855] usb 5-3.1: Manufacturer: ROCCAT
[   63.594939] input: ROCCAT ROCCAT Kone Pro as /devices/pci0000:00/0000:00:08.1/0000:0e:00.3/usb5/5-3/5-3.1/5-3.1:1.0/0003:1E7D:2C88.0012/input/input25
[   63.595065] hid-generic 0003:1E7D:2C88.0012: input,hidraw1: USB HID v1.11 Mouse [ROCCAT ROCCAT Kone Pro] on usb-0000:0e:00.3-3.1/input0
[   63.599940] hid-generic 0003:1E7D:2C88.0013: hiddev97,hidraw2: USB HID v1.11 Device [ROCCAT ROCCAT Kone Pro] on usb-0000:0e:00.3-3.1/input1
[   63.605052] input: ROCCAT ROCCAT Kone Pro Keyboard as /devices/pci0000:00/0000:00:08.1/0000:0e:00.3/usb5/5-3/5-3.1/5-3.1:1.2/0003:1E7D:2C88.0014/input/input26
[   63.656752] input: ROCCAT ROCCAT Kone Pro Mouse as /devices/pci0000:00/0000:00:08.1/0000:0e:00.3/usb5/5-3/5-3.1/5-3.1:1.2/0003:1E7D:2C88.0014/input/input27
[   63.656814] input: ROCCAT ROCCAT Kone Pro as /devices/pci0000:00/0000:00:08.1/0000:0e:00.3/usb5/5-3/5-3.1/5-3.1:1.2/0003:1E7D:2C88.0014/input/input28
[   63.656847] input: ROCCAT ROCCAT Kone Pro Wireless Radio Control as /devices/pci0000:00/0000:00:08.1/0000:0e:00.3/usb5/5-3/5-3.1/5-3.1:1.2/0003:1E7D:2C88.0014/input/input29
[   63.656915] hid-generic 0003:1E7D:2C88.0014: input,hiddev98,hidraw3: USB HID v1.11 Keyboard [ROCCAT ROCCAT Kone Pro] on usb-0000:0e:00.3-3.1/input2
[   63.660971] hid-generic 0003:1E7D:2C88.0015: hiddev99,hidraw4: USB HID v1.11 Device [ROCCAT ROCCAT Kone Pro] on usb-0000:0e:00.3-3.1/input3
[   63.725697] usb 5-3.2: new full-speed USB device number 12 using xhci_hcd
[   63.828849] usb 5-3.2: New USB device found, idVendor=194f, idProduct=0301, bcdDevice= 1.10
[   63.828853] usb 5-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   63.828854] usb 5-3.2: Product: AudioBox USB
[   63.828855] usb 5-3.2: Manufacturer: PreSonus Audio
[   63.843906] usb 5-3.2: 2:1: cannot get freq at ep 0x1
[   63.884910] usb 5-3.2: 3:1: cannot get freq at ep 0x82
[   64.006719] usb 5-3.3: new full-speed USB device number 13 using xhci_hcd
[   64.104894] usb 5-3.3: New USB device found, idVendor=0451, idProduct=0003, bcdDevice= 1.02
[   64.104899] usb 5-3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   64.104901] usb 5-3.3: Product: SMSL AD18 AMP
[   64.104902] usb 5-3.3: Manufacturer: SMSL AUDIO       
[   64.121181] usb 5-3.3: 1:1: cannot get freq at ep 0x1
[   64.230717] usb 5-3.4: new high-speed USB device number 14 using xhci_hcd
[   64.313696] usb 5-3.4: New USB device found, idVendor=2109, idProduct=2812, bcdDevice= d.a0
[   64.313700] usb 5-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   64.313702] usb 5-3.4: Product: USB2.0 Hub             
[   64.313703] usb 5-3.4: Manufacturer: VIA Labs, Inc.         
[   64.357369] hub 5-3.4:1.0: USB hub found
[   64.358332] hub 5-3.4:1.0: 4 ports detected
[   64.427910] usb 5-3.3: 1:1: cannot get freq at ep 0x1
[   64.490036] usb 5-3.3: 1:1: cannot get freq at ep 0x1
[   64.616911] usb 5-3.2: 3:1: cannot get freq at ep 0x82
[   64.692690] usb 5-3.4.4: new full-speed USB device number 15 using xhci_hcd
[   65.060824] usb 5-3.4.4: device descriptor read/64, error -32
[   65.268707] usb 5-3.4.4: device descriptor read/64, error -32
[   65.457693] usb 5-3.4.4: new full-speed USB device number 16 using xhci_hcd
[   65.537706] usb 5-3.4.4: device descriptor read/64, error -32
[   65.722707] usb 5-3.4.4: device descriptor read/64, error -32
[   65.825992] usb 5-3.4-port4: attempt power cycle
[   66.442029] usb 5-3.4.4: new full-speed USB device number 17 using xhci_hcd
[   66.442655] usb 5-3.4.4: Device not responding to setup address.
[   66.650702] usb 5-3.4.4: Device not responding to setup address.
[   66.857803] usb 5-3.4.4: device not accepting address 17, error -71
[   66.938813] usb 5-3.4.4: new full-speed USB device number 18 using xhci_hcd
[   66.939464] usb 5-3.4.4: Device not responding to setup address.
[   67.146601] usb 5-3.4.4: Device not responding to setup address.
[   67.353994] usb 5-3.4.4: device not accepting address 18, error -71
[   67.354406] usb 5-3.4-port4: unable to enumerate USB device

Note that the disconnects during 61.x are not my unplugging anything.

Things I’ve tried:

Plugging fewer devices into the switcher
Plugging the devices into a powered usb3 hub and connecting that hub to the switcher
Enabling IOMMU in UEFI based on this post.

It’s also worth noting that when the switcher is connected to the other host (Dell laptop running Windows 10), I do not see this problem.

Device information:
The problem device is the only USB3.0 device connected to the switcher, though I’m not sure if that’s a red herring. It is a Das Keyboard 4 Professional and it includes a 2-port USB3 hub, although I have had nothing connected to those ports during this testing.

The remaining devices are:

SMSL AD18
Presonus Audiobox USB
Roccat Kone Pure

I’m not sure what to search for anymore, or if I’m running into a bug in the USB drivers or kernel. I’m happy to try to troubleshoot, I’ve just run into the limits of my knowledge and ability to effectively search based on the information I have.

Thank you!

computersavvy · June 30, 2022, 3:31am

Is the switcher a USB3 hub or a USB2 hub?

There are certain devices that have problems with a usb3 device plugged into a usb2 hub, and vice versa.

It has never been a good idea to daisy chain USB hubs.

It has also several times been noted that devices attached to external hubs may not be properly recognized when used in the method you mention. The hub remains powered on so the device does not ask for recognition when it is switched from one system to the other. Unplugging it and reconnecting it forces the system to reconfigure it.

The fact that windows accepts that type of switching is a red herring since windows is not linux and works differently.

mbanducci · July 1, 2022, 8:33pm

The switcher is a USB3 hub. I know it’s not the best idea to daisy-chain hubs, but I don’t have many other options unless I want to crawl under the desk any time I need to switch computers

The thing I can’t figure out is why it took >1yr of using the setup exactly like this for the problem to manifest - It never showed up under Fedora 34 or 35, which is why I wonder if there’s been a regression somewhere.

computersavvy · July 1, 2022, 8:54pm

I guess potentially there may have been a regression. I don’t use an external hub, powered or not, and have not seen any issues but have noted some posts here about issues with devices attached to hubs and even docking stations that had issues similar to yours.

If I had your config I might consider posting a bug just to make the developers aware of the issue so they could see if there is something that could be changed with udev that might reconfigure all usb devices, not just those directly attached, when waking from hibernation or sleep.