Arch Linux

avalon

Member

Registered: 2013-12-12

Posts: 7

Re: xHCI host controller not responding, assume dead

Happens to me with Lenovo T590 and Kernel 5.17.11

This helps though, thanks a lot!

Restarting xHCI sometimes works for me like so (but sometimes it does not work for no apparent reason):

echo -n "0000:00:14.0" | tee /sys/bus/pci/drivers/xhci_hcd/unbind
sleep 5
echo -n "0000:00:14.0" | tee /sys/bus/pci/drivers/xhci_hcd/bind

harvie

Member

From: Prague

Registered: 2015-01-20

Posts: 17

Website

Re: xHCI host controller not responding, assume dead

Happens to me with Lenovo X270 and Kernel 6.13.4-zen1-1-zen
xhci_hcd rebind works. (tried only once tho).

Dunno if this is related, but bluetooth was acting up couple seconds before that happened:

[57709.041555] Bluetooth: hci0: corrupted SCO packet
[57709.041556] Bluetooth: hci0: corrupted SCO packet
[57718.031585] Bluetooth: hci0: corrupted SCO packet
[57718.031599] Bluetooth: hci0: corrupted SCO packet
[57718.031605] Bluetooth: hci0: corrupted SCO packet
[57718.031609] Bluetooth: hci0: corrupted SCO packet
[57718.031614] Bluetooth: hci0: corrupted SCO packet
[64135.350299] Bluetooth: hci0: command 0x0405 tx timeout
[64137.013259] xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command
[64137.013287] xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
[64137.013328] xhci_hcd 0000:00:14.0: Timeout while waiting for stop endpoint command
[64137.013338] xhci_hcd 0000:00:14.0: HC died; cleaning up

tapia

Member

Registered: 2013-03-13

Posts: 59

Re: xHCI host controller not responding, assume dead

I have the same issue.

I get the following relevant information in journalctl:

Feb 24 22:57:51 tapia-laptop kernel: xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command
Feb 24 22:57:51 tapia-laptop kernel: xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
Feb 24 22:57:51 tapia-laptop kernel: xhci_hcd 0000:00:14.0: HC died; cleaning up
Feb 24 22:57:51 tapia-laptop kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for stop endpoint command
Feb 24 22:57:51 tapia-laptop kernel: usb 2-1: USB disconnect, device number 2
Feb 24 22:57:51 tapia-laptop kernel: usb 2-1.1: USB disconnect, device number 5
Feb 24 22:57:51 tapia-laptop kernel: usb 3-1: USB disconnect, device number 2
Feb 24 22:57:51 tapia-laptop kernel: usb 2-1.2: USB disconnect, device number 7
Feb 24 22:57:51 tapia-laptop kernel: usb 2-1.4: USB disconnect, device number 13
Feb 24 22:57:51 tapia-laptop kernel: usb 2-2: USB disconnect, device number 14
Feb 24 22:57:51 tapia-laptop kernel: usb 2-3: USB disconnect, device number 4
Feb 24 22:57:51 tapia-laptop kernel: usb 2-4: USB disconnect, device number 6
Feb 24 22:57:51 tapia-laptop kernel: usb 2-5: USB disconnect, device number 9

dabbeg

Member

Registered: 2025-02-26

Posts: 1

Re: xHCI host controller not responding, assume dead

Same issue here:

Feb 26 12:49:05 skeletor kernel: xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command
Feb 26 12:49:05 skeletor kernel: xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
Feb 26 12:49:05 skeletor kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for stop endpoint command
Feb 26 12:49:05 skeletor kernel: xhci_hcd 0000:00:14.0: HC died; cleaning up
Feb 26 12:49:05 skeletor kernel: usb 3-1: USB disconnect, device number 2
Feb 26 12:49:05 skeletor kernel: usb 3-3: USB disconnect, device number 33
Feb 26 12:49:05 skeletor kernel: usb 3-4: USB disconnect, device number 4
Feb 26 12:49:05 skeletor kernel: usb 3-5: USB disconnect, device number 53
Feb 26 12:49:05 skeletor kernel: usb 3-5.1: USB disconnect, device number 54
Feb 26 12:49:05 skeletor kernel: usb 3-5.1.1: USB disconnect, device number 55
Feb 26 12:49:05 skeletor kernel: usb 3-5.1.2: USB disconnect, device number 56
Feb 26 12:49:05 skeletor kernel: usb 3-10: USB disconnect, device number 6

Last edited by dabbeg (2025-02-26 13:41:46)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,465

Re: xHCI host controller not responding, assume dead

This thread started in 2016 .

Try the unbind/bind method mentioned in several replies, if that doesn't help start a new thread.

Closing this old thread

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky