Lost Peripherals after Recent Update

tenroc

Axios Just tried it, it didn't work. But thanks a lot for the tip!
The issues really started with the last two kernel updates, so I'm guessing something changed in the xhci driver which caused the bug. I'm typing this while using the last working kernel version and everything is fine.

Axios

tenroc Well hardware is prob good run sudo dmesg see if you can tell anything By running dmesg that way can
see hardware stuffs. There will be section with usb stuff might have do it with working kernal then the new to tell what going on something should show up

tenroc

Axios Yeah, journald does show dmesg among other logs. The errors I pasted above come from dmesg. It doesn't tell me much more than xhci dying for some reason and unloading every usb devices. I'm used to xhci errors, and I am affected by the bug you linked, i.e unresponsive usb at boot until device 2-3 times out. I have workarounds for those, the difference is that with newer kernels, failing to initiate a faulty or unresponsive device seems to bring the whole controller down. Something changed in the xhci driver, and I'm guessing this is why so many people with varying hardware have the issue.

Axios

Well after some looking reading anything on the usb buss (apple) that has a driver problem can throw things into a tizzy and the usb just shuts down. Guess what i am trying to say its not actually the ports. If I understand everything right. but everybodies hardware is so different cant think thats it. Did find this but its old issue but its seems like its what going with apple Dunno just info https://bugzilla.kernel.org/show_bug.cgi?id=115741 I think maybe the key was usb hot plug not working properly.

Axios

tenroc failing to initiate a faulty or unresponsive device seems to bring the whole controller down. Something changed in the xhci driver, yup thats what I was trying to get across It appears its suppose to work that way but only with faulty hardware.
Does your internal usb work keyboard,camera ect or does everything die

tenroc

Axios Old behavior: The faulty device (no idea what it is, something internal wired as usb) times out, xhci doesn't die and therefore doesn't bring down all of my other usb devices. So my keyboard and all are perfectly functional.

New behavior: xhci dies, and unload every usb devices, including the faulty device, my internal keyboard / trackpad, my webcam etc. So I can't get past the decryption prompt, and I have to force reboot and use the last working kernel.

noise617

Below is the response from sudo journalctl | grep -E "(xhci|\: usb)". I did the following:

First rebooted into the latest current kernel, 5.14.15-203. The OS boots up but USB keyboard and mouse do not work at all.
Then hard-rebooted into the latest LTS kernel, 4.14.246-178. The OS boots up, USB keyboard and mouse initially do not work but start working after a time out of around 30 seconds.

Nov 03 21:18:39 solus kernel: usbcore: registered new interface driver usbfs
Nov 03 21:18:39 solus kernel: usbcore: registered new interface driver hub
Nov 03 21:18:39 solus kernel: usbcore: registered new device driver usb
Nov 03 21:18:39 solus kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Nov 03 21:18:39 solus kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
Nov 03 21:18:39 solus kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000001109810
Nov 03 21:18:39 solus kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Nov 03 21:18:39 solus kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
Nov 03 21:18:39 solus kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
Nov 03 21:18:39 solus kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.14
Nov 03 21:18:39 solus kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 03 21:18:39 solus kernel: usb usb1: Product: xHCI Host Controller
Nov 03 21:18:39 solus kernel: usb usb1: Manufacturer: Linux 5.14.15-203.current xhci-hcd
Nov 03 21:18:39 solus kernel: usb usb1: SerialNumber: 0000:00:14.0
Nov 03 21:18:39 solus kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.14
Nov 03 21:18:39 solus kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 03 21:18:39 solus kernel: usb usb2: Product: xHCI Host Controller
Nov 03 21:18:39 solus kernel: usb usb2: Manufacturer: Linux 5.14.15-203.current xhci-hcd
Nov 03 21:18:39 solus kernel: usb usb2: SerialNumber: 0000:00:14.0
Nov 03 21:18:39 solus kernel: usb 1-1: new full-speed USB device number 2 using xhci_hcd
Nov 03 21:18:40 solus kernel: usb 1-1: New USB device found, idVendor=1ea7, idProduct=0064, bcdDevice= 2.00
Nov 03 21:18:40 solus kernel: usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Nov 03 21:18:40 solus kernel: usb 1-1: Product: 2.4G Mouse
Nov 03 21:18:40 solus kernel: usbcore: registered new interface driver usbhid
Nov 03 21:18:40 solus kernel: usbhid: USB HID core driver
Nov 03 21:18:40 solus kernel: usb 1-2: new high-speed USB device number 3 using xhci_hcd
Nov 03 21:18:40 solus kernel: usb 1-2: New USB device found, idVendor=2717, idProduct=ff40, bcdDevice= 3.18
Nov 03 21:18:40 solus kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 03 21:18:40 solus kernel: usb 1-2: Product: Android
Nov 03 21:18:40 solus kernel: usb 1-2: Manufacturer: Android
Nov 03 21:18:40 solus kernel: usb 1-2: SerialNumber: edcd55e67d43
Nov 03 21:18:40 solus kernel: usb 1-3: new full-speed USB device number 4 using xhci_hcd
Nov 03 21:18:40 solus kernel: usb 1-3: New USB device found, idVendor=feed, idProduct=3060, bcdDevice= 0.01
Nov 03 21:18:40 solus kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 03 21:18:40 solus kernel: usb 1-3: Product: Corne Keyboard (crkbd)
Nov 03 21:18:40 solus kernel: usb 1-3: Manufacturer: foostan
Nov 03 21:18:40 solus kernel: usb 1-3: SerialNumber: 0
Nov 03 21:18:40 solus kernel: usb 1-6: new high-speed USB device number 5 using xhci_hcd
Nov 03 21:18:40 solus kernel: usb 1-6: New USB device found, idVendor=045e, idProduct=075d, bcdDevice= 1.05
Nov 03 21:18:40 solus kernel: usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov 03 21:18:40 solus kernel: usb 1-6: Product: Microsoft® LifeCam Cinema(TM)
Nov 03 21:18:40 solus kernel: usb 1-6: Manufacturer: Microsoft
Nov 03 21:18:41 solus kernel: usb 1-9: new full-speed USB device number 6 using xhci_hcd
Nov 03 21:18:56 m700 kernel: usb 1-9: device descriptor read/64, error -110
Nov 03 21:19:12 m700 kernel: usb 1-9: device descriptor read/64, error -110
Nov 03 21:19:12 m700 kernel: usb 1-9: new full-speed USB device number 7 using xhci_hcd
Nov 03 21:19:28 m700 kernel: usb 1-9: device descriptor read/64, error -110
Nov 03 21:19:44 m700 kernel: usb 1-9: device descriptor read/64, error -110
Nov 03 21:19:44 m700 kernel: usb usb1-port9: attempt power cycle
Nov 03 21:19:44 m700 kernel: usb 1-9: new full-speed USB device number 8 using xhci_hcd
Nov 03 21:19:51 m700 systemd-udevd[631]: usb1: Worker [662] processing SEQNUM=2466 is taking a long time
Nov 03 21:19:54 m700 kernel: xhci_hcd 0000:00:14.0: Abort failed to stop command ring: -110
Nov 03 21:19:54 m700 kernel: xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
Nov 03 21:19:54 m700 kernel: xhci_hcd 0000:00:14.0: HC died; cleaning up
Nov 03 21:19:54 m700 kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
Nov 03 21:19:55 m700 kernel: usb 1-9: device not accepting address 8, error -108
Nov 03 21:19:55 m700 kernel: usb usb1-port9: couldn't allocate usb_device
Nov 03 21:19:55 m700 kernel: usb 1-1: USB disconnect, device number 2
Nov 03 21:19:55 m700 kernel: usb 1-2: USB disconnect, device number 3
Nov 03 21:19:55 m700 kernel: usb 1-3: USB disconnect, device number 4
Nov 03 21:19:55 m700 kernel: usb 1-6: USB disconnect, device number 5
Nov 03 21:19:55 m700 kernel: usbcore: registered new interface driver snd-usb-audio
Nov 03 21:19:55 m700 kernel: usbcore: registered new interface driver uvcvideo
Nov 03 21:25:32 solus kernel: usbcore: registered new interface driver usbfs
Nov 03 21:25:32 solus kernel: usbcore: registered new interface driver hub
Nov 03 21:25:32 solus kernel: usbcore: registered new device driver usb
Nov 03 21:25:32 solus kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Nov 03 21:25:32 solus kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
Nov 03 21:25:32 solus kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000001109810
Nov 03 21:25:32 solus kernel: xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
Nov 03 21:25:32 solus kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov 03 21:25:32 solus kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 03 21:25:32 solus kernel: usb usb1: Product: xHCI Host Controller
Nov 03 21:25:32 solus kernel: usb usb1: Manufacturer: Linux 4.14.246-178.lts xhci-hcd
Nov 03 21:25:32 solus kernel: usb usb1: SerialNumber: 0000:00:14.0
Nov 03 21:25:32 solus kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Nov 03 21:25:32 solus kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
Nov 03 21:25:32 solus kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.0  SuperSpeed
Nov 03 21:25:32 solus kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
Nov 03 21:25:32 solus kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 03 21:25:32 solus kernel: usb usb2: Product: xHCI Host Controller
Nov 03 21:25:32 solus kernel: usb usb2: Manufacturer: Linux 4.14.246-178.lts xhci-hcd
Nov 03 21:25:32 solus kernel: usb usb2: SerialNumber: 0000:00:14.0
Nov 03 21:25:33 solus kernel: usb 1-1: new full-speed USB device number 2 using xhci_hcd
Nov 03 21:25:33 solus kernel: usb 1-1: New USB device found, idVendor=1ea7, idProduct=0064
Nov 03 21:25:33 solus kernel: usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Nov 03 21:25:33 solus kernel: usb 1-1: Product: 2.4G Mouse
Nov 03 21:25:33 solus kernel: usbcore: registered new interface driver usbhid
Nov 03 21:25:33 solus kernel: usbhid: USB HID core driver
Nov 03 21:25:33 solus kernel: usb 1-2: new high-speed USB device number 3 using xhci_hcd
Nov 03 21:25:33 solus kernel: usb 1-2: New USB device found, idVendor=2717, idProduct=ff40
Nov 03 21:25:33 solus kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 03 21:25:33 solus kernel: usb 1-2: Product: Android
Nov 03 21:25:33 solus kernel: usb 1-2: Manufacturer: Android
Nov 03 21:25:33 solus kernel: usb 1-2: SerialNumber: edcd55e67d43
Nov 03 21:25:33 solus kernel: usb 1-3: new full-speed USB device number 4 using xhci_hcd
Nov 03 21:25:33 solus kernel: usb 1-3: New USB device found, idVendor=feed, idProduct=3060
Nov 03 21:25:33 solus kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 03 21:25:33 solus kernel: usb 1-3: Product: Corne Keyboard (crkbd)
Nov 03 21:25:33 solus kernel: usb 1-3: Manufacturer: foostan
Nov 03 21:25:33 solus kernel: usb 1-3: SerialNumber: 0
Nov 03 21:25:33 solus kernel: usb 1-6: new high-speed USB device number 5 using xhci_hcd
Nov 03 21:25:34 solus kernel: usb 1-6: New USB device found, idVendor=045e, idProduct=075d
Nov 03 21:25:34 solus kernel: usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov 03 21:25:34 solus kernel: usb 1-6: Product: Microsoft® LifeCam Cinema(TM)
Nov 03 21:25:34 solus kernel: usb 1-6: Manufacturer: Microsoft
Nov 03 21:25:34 solus kernel: usb 1-9: new full-speed USB device number 6 using xhci_hcd
Nov 03 21:25:49 m700 kernel: usb 1-9: device descriptor read/64, error -110
Nov 03 21:26:05 m700 kernel: usb 1-9: device descriptor read/64, error -110
Nov 03 21:26:05 m700 kernel: usb 1-9: new full-speed USB device number 7 using xhci_hcd
Nov 03 21:26:21 m700 kernel: usb 1-9: device descriptor read/64, error -110
Nov 03 21:26:37 m700 kernel: usb 1-9: device descriptor read/64, error -110
Nov 03 21:26:37 m700 kernel: usb usb1-port9: attempt power cycle
Nov 03 21:26:37 m700 kernel: usb 1-9: new full-speed USB device number 8 using xhci_hcd
Nov 03 21:26:43 m700 kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
Nov 03 21:26:43 m700 kernel: usb 1-9: Device not responding to setup address.
Nov 03 21:26:43 m700 kernel: usb 1-9: device not accepting address 8, error -71
Nov 03 21:26:43 m700 kernel: usb 1-9: new full-speed USB device number 9 using xhci_hcd
Nov 03 21:26:47 m700 systemd-udevd[647]: usb1: Worker [692] processing SEQNUM=2224 is taking a long time
Nov 03 21:26:48 m700 kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
Nov 03 21:26:48 m700 kernel: usb 1-9: Device not responding to setup address.
Nov 03 21:26:49 m700 kernel: usb 1-9: device not accepting address 9, error -71
Nov 03 21:26:49 m700 kernel: usb usb1-port9: unable to enumerate USB device
Nov 03 21:26:49 m700 kernel: usbcore: registered new interface driver snd-usb-audio
Nov 03 21:26:49 m700 kernel: usbcore: registered new interface driver uvcvideo

Axios

noise617 This is prob the offender udev tells you that some worker hangs prob driver issue or weird rule installed by some package that runs some binary that is excessively slow-- (systemd-udevd[647]: usb1: Worker [692] processing SEQNUM=2224 is taking a long time) I guess it says usb1 whats in usb1?

tenroc

noise617 For me this is the culprit:

Nov 03 21:18:56 m700 kernel: usb 1-9: device descriptor read/64, error -110

The change in behavior is the same as mine: Both times, it fails to setup usb 1-9, both times, it gives you some udev error, but with the working kernel it simply gives up on setting usb 1-9 after it times out (therefore the lag before your usb ports become usable again), with the newer, faulty kernel, it brings down your whole usb controller, and xhci proceeds to unload every usb devices.

By the way, usb 1 is just your controller. you can try to find what is usb 1-9 with lsusb. The logs tell you that it gets registered as device 6 on Bus 1. No idea if it will show up though, since it times out.

noise617

Axios Is this it?

Nov 03 21:18:39 solus kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.14
Nov 03 21:18:39 solus kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 03 21:18:39 solus kernel: usb usb1: Product: xHCI Host Controller
Nov 03 21:18:39 solus kernel: usb usb1: Manufacturer: Linux 5.14.15-203.current xhci-hcd
Nov 03 21:18:39 solus kernel: usb usb1: SerialNumber: 0000:00:14.0

Axios

I think this is prob what you are looking at been going on for while with host controller.
So appears got wait for kernel fix. I can see how it could have been a hiccup early on
its with the command ring pointer corruption so I can see how everyones sympton is just little different depends on how it got corrupted See what you guys think. https://bbs.archlinux.org/viewtopic.php?id=270795
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.14.y&id=e54abefe703ab7c4e5983e889babd1447738ca42 after reading alot on its appears stubborn bug!! So to me thats where I leave it. Hope this helps

tenroc

Axios Wow thanks for the links! Yes, that seems to be the issue. So it affects every distro with the faulty kernels then. Yes, seems our best shot is just to wait for it to get fixed by the kernel devs. I'll stay on the LTS kernel until then.

noise617

Axios tenroc Do you guys think the annoying timeout (in my case) will be fixed as well, with the future updated kernel? What I mean is, why do I even have this timeout? Everything seems to be working fine. Before a certain point, for my several Solus years, I had no such problems.

Also:

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 045e:075d Microsoft Corp. LifeCam Cinema
Bus 001 Device 004: ID feed:3060 foostan Corne Keyboard (crkbd)
Bus 001 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz Wireless rechargeable vertical mouse [More&Better]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Axios

All the issues even the thumbs issues are all related to this I am sure It will prob get fixed,I have read things back to 2008 and as current as oct 1 21 The device can recover or die depending on what caused it. Usb is the mainstay today seems like so prob wont go unfixed.
Something changed in kernal to upset the apple cart.
About best simplest way I can explain it. I read the intel exhc controller doc you dont wanna read it 645 pages...lol
Just lucky got a kernal that you can fallback on the issue appears to be in the pipeline tho
(PS a timeout can be good or bad depending on what its for Just because its there does not mean its bad)

noise617

Axios Thanks for the reply! Hope this will be fixed 🙂

noise617

As of January 2022, this problem persists for my Lenovo M700 mini-PC. Still no USB devices work when I use Linux core version 5.

I have also tried out Zorin OS: when running it from a USB stick, things work flawlessly. But after installation and a reboot from the regular drive, keyboard and mouse do not respond.

Has anyone found a solution?

noise617

P. S. I reinstalled Solus. Here are the errors displayed after the installer rebooted the computer:

WetGeek

Experiment with the timing of when you remove the installer USB drive from the computer when you reboot after an installation. If you leave it in place too long, the USB drive wil be what gets rebooted*. When I've taken it out before restarting, I've seen errors I didn't understand. Pretty soon you'll get used to starting the reboot, and then after a seond or two you pull out the installer USB. That way it will be the new system that's started.

* If you do end up back in the inistaller, that's no problem. Just remove the installer and reboot.

noise617

@WetGeek, I posted the picture because it is a rare opportunity to see the errors that are likely related to the support of USB devices by Linux on my PC.

noise617

Okay, so what solved the problem was BIOS update. More problems emerged recently which made OS unusable. I updated Lenovo BIOS. now everything works. Thanks to everyone who shared their advice, anyway.

brent

noise617 Rarely (never) have I seen a Solved issue end with flashing as the solution. I have lived with outdated BIOS in all my machines in my linux life (circa '16) because I hear it is notoriously dangerous in Linux. Far out, and congrats.

Axios

noise617 Glad you got it fixed Just acquired a lenovo thinkpad 11e has to small m.2 ssd in it for any
kinda windows stuff win10 updates puke on small drive space. My point was thanks for posting your results in case I decide to put linux on it and experience issues.

« Previous Page Next Page »