FS#66348 - [linux] xhci, Not enough bandwidth for new device state.

Attached to Project: Arch Linux
Opened by Johnny (Shoppinguin) - Wednesday, 22 April 2020, 10:07 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 01 March 2022, 21:08 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Levente Polyak (anthraxx)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
When connecting multiple devices to a KVM switch(essentially a 3-port USB2.0-hub) or USB2.0 hub that is connected to a USB 3.0 port, at least one device will not work properly. Journalctl will show "Not enough bandwidth for new device state." and disable at least one of the connected devices. The problem does not occur with the exact same config while using the lts-Kernel (package version 5.4.32-1).

Additional info:
* 5.6.4.arch1-1
* Tested on HP ZBook 17 (D5D93AV) with both Belkin F1DD102L KVM switch and Belkin F4U016 USB2.0-Hub, can be reproduced on other hardware(PC using Gigabyte GA-A75-UD4H)
* devices used for test: Roccat ROC-11-723 gaming mouse, Logitech A-00061(G430 USB Audio adapter), generic USB-PS/2 adapter

Steps to reproduce:
Plug USB 2.0/3.0 hub or KVM switch to a USB 3.0 port. Run journalctl -xf. Connect each device until errormessage appears. The device connected last will not work.
Leave everything as it is and reboot with lts kernel(version 5.4.32-1). All devices work and there will be no error.

This is probably a regression as i could find an older bugreport and a board post with the same issue:
https://bugs.archlinux.org/task/18866
https://bbs.archlinux.org/viewtopic.php?id=211902

As attaching files does not work here, i have posted the output of "lsusb -tv" for three configs, which which the error was successfully reproduced here: https://www.0wx.cat/431e6f95bcc20ef598e3bb6584d2efa9/
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 01 March 2022, 21:08 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed upstream.
Comment by mattia (nTia89) - Monday, 28 February 2022, 16:33 GMT
I cannot reproduce the issue. Is it still valid for you?
Comment by Johnny (Shoppinguin) - Monday, 28 February 2022, 19:21 GMT
Haven't seen this problem in a long time. It took a few updates of the kernel but for at least half a year there were no such problems.
This can surely be closed.

Loading...