Skip to contentSkip to conversation

xhci_hcd: USB-2 devices are not usable after replug

DISCUSSION Thomas Glanzmann 2 participants 2 messages Feb 27, 2023 – Mar 1, 2023 USB

lore
Share & tools
lore
#0 lore raw

Hello,
my USB-2 mouse and keyboard works when connected while I'm booting. If I replug them, I get in the dmesg the following lines and they no longer work:

[   48.739931] xhci_hcd 0000:0c:00.0: Error while assigning device slot ID: Command Aborted
[   48.739938] xhci_hcd 0000:0c:00.0: Max number of devices this xHCI host supports is 64.
[   48.739941] usb usb1-port1: couldn't allocate usb_device
[   48.776022] xhci_hcd 0000:0c:00.0: WARN: xHC save state timeout
[   48.776032] xhci_hcd 0000:0c:00.0: PM: suspend_common(): xhci_pci_suspend+0x0/0x150 [xhci_pci] returns -110
[   48.776041] xhci_hcd 0000:0c:00.0: can't suspend (hcd_pci_runtime_suspend [usbcore] returned -110)

If I plug them in USB-3 port they work. Is this a known issue? Is there a workaround? Has someone a patch that I can test?

Find the output of dmesg, lsusb, lspci, dmidecode and lscpu here:

https://tg.st/u/6c2aa1c7120cc64e2d90863dc3afea4d4c9e3d6f56666fc681c02ee5f0728130.txt

I'm running v6.2.1 with a Debian bookwork userland and have the latest linux-firmware from git installed.

Cheers,
Thomas

#1 lore raw
Quoted 17 lines · Thomas Glanzmann

Hello,
my USB-2 mouse and keyboard works when connected while I'm booting. If I replug them, I get in the dmesg the following lines and they no longer work:

[   48.739931] xhci_hcd 0000:0c:00.0: Error while assigning device slot ID: Command Aborted
[   48.739938] xhci_hcd 0000:0c:00.0: Max number of devices this xHCI host supports is 64.
[   48.739941] usb usb1-port1: couldn't allocate usb_device
[   48.776022] xhci_hcd 0000:0c:00.0: WARN: xHC save state timeout
[   48.776032] xhci_hcd 0000:0c:00.0: PM: suspend_common(): xhci_pci_suspend+0x0/0x150 [xhci_pci] returns -110
[   48.776041] xhci_hcd 0000:0c:00.0: can't suspend (hcd_pci_runtime_suspend [usbcore] returned -110)

If I plug them in USB-3 port they work. Is this a known issue? Is there a workaround? Has someone a patch that I can test?

Find the output of dmesg, lsusb, lspci, dmidecode and lscpu here:

Quoted 8 lines

https://tg.st/u/6c2aa1c7120cc64e2d90863dc3afea4d4c9e3d6f56666fc681c02ee5f0728130.txt

I'm running v6.2.1 with a Debian bookwork userland and have the latest linux-firmware from git installed.

Cheers,
Thomas

Hi,

This looks like a BIOS problem, similar to the one that was raised on an unlaunched Mendocino based design a few weeks ago. You should raise it with your motherboard vendor.

But as this is already launched and it escaped, I think we can come up with a workaround as well.

Give me a little bit to discuss internally and I'll CC you on the solution.

Thanks!