https://bugzilla.kernel.org/show_bug.cgi?id=219198 Adam Williamson (adamw@xxxxxxxxxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adamw@xxxxxxxxxxxxxxxxx --- Comment #5 from Adam Williamson (adamw@xxxxxxxxxxxxxxxxx) --- I'm seeing something similar, and powertop doesn't seem to be involved. I also have a Dell laptop - an XPS 13 9315. It's connected to a CalDigit TS3+ Thunderbolt docking station. Connected to the CalDigit are a 4K monitor (connected by USB-C), Ethernet, a USB webcam, USB headset, and a USB keyboard. The laptop has an internal keyboard and trackpad, of course. And I have a Bluetooth external mouse. When I boot kernel 6.9.12 or 6.10.6, all of these work fine more or less immediately after boot, every time. When I boot kernel 6.11 (tried rc3, rc4 and rc5) this is what happens: * At the point where I have to enter the passphrase to decrypt my storage, the USB keyboard always works. * When I reach the login screen - whether GDM or just a tty, I tested boot to multi-user.target and it's the same - nothing works for quite some time. After about 20 seconds, the laptop's internal keyboard and trackpad, and the Bluetooth mouse, start working. But the USB external keyboard never starts working. (I'm not sure of the status of the webcam and headset, I didn't check). I have powertop and power-profiles-daemon installed, but I tried removing both and doing a test boot of 6.11rc5, and the symptoms were exactly the same, nothing changed. I'll attach the journal from an affected 6.11rc5 boot and from a working 6.10 boot. Something I notice is that early in boot we see: Aug 26 11:47:03 xps13a.happyassassin.net kernel: hid-generic 0003:154A:0002.0002: input,hidraw1: USB HID v1.00 Keyboard [ID Innovations Inc. Input Device] on usb-0000:56:00.0-2/input0 but then later, we see: Aug 26 11:47:44 xps13a.happyassassin.net kernel: xhci_hcd 0000:57:00.0: Abort failed to stop command ring: -110 Aug 26 11:47:44 xps13a.happyassassin.net kernel: xhci_hcd 0000:57:00.0: xHCI host controller not responding, assume dead Aug 26 11:47:44 xps13a.happyassassin.net kernel: xhci_hcd 0000:57:00.0: HC died; cleaning up Aug 26 11:47:44 xps13a.happyassassin.net kernel: xhci_hcd 0000:57:00.0: Error while assigning device slot ID: Command Aborted Aug 26 11:47:44 xps13a.happyassassin.net kernel: xhci_hcd 0000:57:00.0: Max number of devices this xHCI host supports is 64. Aug 26 11:47:44 xps13a.happyassassin.net kernel: usb usb9-port1: couldn't allocate usb_device Aug 26 11:47:44 xps13a.happyassassin.net systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 26 11:47:44 xps13a.happyassassin.net audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Aug 26 11:47:50 xps13a.happyassassin.net kernel: Bluetooth: hci0: Opcode 0x200e failed: -110 Aug 26 11:48:00 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: Abort failed to stop command ring: -110 Aug 26 11:48:00 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: xHCI host controller not responding, assume dead Aug 26 11:48:00 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: HC died; cleaning up Aug 26 11:48:00 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: Error while assigning device slot ID: Command Aborted Aug 26 11:48:00 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: Max number of devices this xHCI host supports is 32. Aug 26 11:48:00 xps13a.happyassassin.net kernel: usb usb7-port2: couldn't allocate usb_device Aug 26 11:48:00 xps13a.happyassassin.net kernel: usb usb8-port4: couldn't allocate usb_device and after that, we never see "USB HID v1.00 Keyboard" appear again. In contrast, in the 6.10 logs, we see "USB HID v1.00 Keyboard" appear twice, and we never see any "couldn't allocate usb_device" or "Abort failed to stop command ring" errors. I *think* the 're-enumeration' that seems to be happening here (which seems to work fine on 6.10, but lead to problems on 6.11) is a result of thunderbolt.service starting up. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
