5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

thatvolvonut · 2020-11-22 19:58:43

tl;dr - upgrading from kernel 5.9.1 to 5.9.9 seems to break most USB devices (hid and USB serial don't work, USB storage is fine).

Hi all, this is the first issue I haven't been able to solve with Google, so here I am!

I'm running a pretty vanilla install with SwayWM on an ancient (ca. 2004 I think?) Pentium 4 system. I have udev rules for an Adafruit USBTiny ISP, a SparkFun ESP8266 Thing Dev, and Sigrok.

What's Wrong: My mouse is not being recognized by the kernel at all. It's a standard Dell USB mouse, showing up as ID 0461:4e22 Primax Electronics, Ltd Dell Mouse, 2 Buttons, Modell: MS111-P (sic) on lsusb (using kernel 5.9.1). dmesg shows it as a PixArt USB Optical Mouse. It works on Windows and kernel 5.9.1 but not on any later kernels. Booting with it attached or hotplugging (or both) show no activity in dmesg and no entry on lsusb. Most of my testing has been on kernel 5.9.9.

What I've Tried: Downgrading relevant-seeming packages isolated the kernel update as the issue: with all packages fully up to date, downgrading just the kernel to version 5.9.1 makes the mouse work again. I downgrade by using Server = https://archive.archlinux.org/repos/202 … o/os/$arch in my mirrorlist and running pacman -Syy linux, which makes the mouse work again. Manually loading the usbhid and/or hid modules in kernel 5.9.9 does not work.

More Observations: 5.9.1 boots with the usb_storage and uas modules loaded; this is probably due to the installed card reader. 5.9.9 does not boot with these modules loaded and doesn't recognize the card reader (lsusb shows 4 USB hubs and nothing else). I also have an FTDI board (SparkFun ESP8266 Thing Dev) that is recognized under 5.9.1, generating /dev/ttyUSB, that is not recognized under 5.9.9. Strangely, a USB 3.0 flash drive works perfectly fine (though in some kind of 2.0 compatibility mode, I'm sure) - that's the only USB device that I've seen work. PS/2 devices work fine, a different known good USB mouse does not work.

There doesn't seem to be any USB errors in dmesg when booting 5.9.9, it just ignores most USB devices. dmesg | grep usb is identical between both kernels except for the extra recognized devices; dump is below.

I'm completely stuck; I don't know nearly enough about kernel-level USB to dig into this, and the fact that nothing's showing up in dmesg is kind of freaking me out. I know it's not a hardware issue because I've been bouncing between 5.9.1 and 5.9.9 using the mirrorlist downgrade method above. I'm willing to do a wipe/reinstall, but only as a super last resort.

Sorry for the wall of text, I tried to include all the relevant details. Any hints are much appreciated, thanks!
~thatvolvonut

dmesg | grep usb, kernel 5.9.1

[    0.389471] usbcore: registered new interface driver usbfs
[    0.389487] usbcore: registered new interface driver hub
[    0.389521] usbcore: registered new device driver usb
[    0.489821] pci 0000:00:1c.0: quirk_usb_early_handoff+0x0/0x6d5 took 26239 usecs
[    0.516458] pci 0000:00:1c.1: quirk_usb_early_handoff+0x0/0x6d5 took 26000 usecs
[    0.543123] pci 0000:00:1c.2: quirk_usb_early_handoff+0x0/0x6d5 took 26028 usecs
[    0.928042] usbcore: registered new interface driver usbserial_generic
[    0.928051] usbserial: USB Serial support registered for generic
[    3.211861] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.09
[    3.211868] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.211872] usb usb1: Product: EHCI Host Controller
[    3.211875] usb usb1: Manufacturer: Linux 5.9.1-arch1-1 ehci_hcd
[    3.211878] usb usb1: SerialNumber: 0000:00:1c.3
[    3.276855] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.09
[    3.276859] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.276861] usb usb2: Product: OHCI PCI host controller
[    3.276864] usb usb2: Manufacturer: Linux 5.9.1-arch1-1 ohci_hcd
[    3.276865] usb usb2: SerialNumber: 0000:00:1c.0
[    3.336790] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.09
[    3.336793] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.336796] usb usb3: Product: OHCI PCI host controller
[    3.336798] usb usb3: Manufacturer: Linux 5.9.1-arch1-1 ohci_hcd
[    3.336800] usb usb3: SerialNumber: 0000:00:1c.1
[    3.396776] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.09
[    3.396779] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.396782] usb usb4: Product: OHCI PCI host controller
[    3.396784] usb usb4: Manufacturer: Linux 5.9.1-arch1-1 ohci_hcd
[    3.396786] usb usb4: SerialNumber: 0000:00:1c.2
[    3.777983] usb 2-3: new low-speed USB device number 2 using ohci-pci
[    4.008340] usb 2-3: New USB device found, idVendor=0461, idProduct=4e22, bcdDevice= 1.00
[    4.008343] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    4.008346] usb 2-3: Product: USB Optical Mouse
[    4.008348] usb 2-3: Manufacturer: PixArt
[    4.029608] usbcore: registered new interface driver usbhid
[    4.029611] usbhid: USB HID core driver
[    4.598000] usb 4-2: new full-speed USB device number 2 using ohci-pci
[    4.831430] usb 4-2: New USB device found, idVendor=058f, idProduct=9360, bcdDevice= 1.00
[    4.831435] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.831437] usb 4-2: Product: USB Reader
[    4.831439] usb 4-2: Manufacturer:  
[    4.831441] usb 4-2: SerialNumber: 9205291
[    4.842148] usb-storage 4-2:1.0: USB Mass Storage device detected
[    4.842963] scsi host6: usb-storage 4-2:1.0
[    4.843316] usbcore: registered new interface driver usb-storage
[    9.941458] usbcore: registered new interface driver uas
[    9.971704] input: PixArt USB Optical Mouse as /devices/pci0000:00/0000:00:1c.0/usb2/2-3/2-3:1.0/0003:0461:4E22.0001/input/input3
[    9.984901] hid-generic 0003:0461:4E22.0001: input,hidraw0: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:1c.0-3/input0

demsg | grep usb, kernel 5.9.9

[    0.388728] usbcore: registered new interface driver usbfs
[    0.388728] usbcore: registered new interface driver hub
[    0.388728] usbcore: registered new device driver usb
[    0.487436] pci 0000:00:1c.0: quirk_usb_early_handoff+0x0/0x6e0 took 25236 usecs
[    0.514074] pci 0000:00:1c.1: quirk_usb_early_handoff+0x0/0x6e0 took 26002 usecs
[    0.540738] pci 0000:00:1c.2: quirk_usb_early_handoff+0x0/0x6e0 took 26027 usecs
[    0.926501] usbcore: registered new interface driver usbserial_generic
[    0.926511] usbserial: USB Serial support registered for generic
[    3.197147] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.09
[    3.197152] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.197156] usb usb1: Product: EHCI Host Controller
[    3.197159] usb usb1: Manufacturer: Linux 5.9.9-arch1-1 ehci_hcd
[    3.197162] usb usb1: SerialNumber: 0000:00:1c.3
[    3.262695] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.09
[    3.262698] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.262701] usb usb2: Product: OHCI PCI host controller
[    3.262703] usb usb2: Manufacturer: Linux 5.9.9-arch1-1 ohci_hcd
[    3.262705] usb usb2: SerialNumber: 0000:00:1c.0
[    3.322688] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.09
[    3.322691] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.322693] usb usb3: Product: OHCI PCI host controller
[    3.322695] usb usb3: Manufacturer: Linux 5.9.9-arch1-1 ohci_hcd
[    3.322697] usb usb3: SerialNumber: 0000:00:1c.1
[    3.379352] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.09
[    3.379356] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.379358] usb usb4: Product: OHCI PCI host controller
[    3.379360] usb usb4: Manufacturer: Linux 5.9.9-arch1-1 ohci_hcd
[    3.379362] usb usb4: SerialNumber: 0000:00:1c.2

Scimmia · 2020-11-22 23:41:29

When it doesn't work, what does `uname -a` give you?

thatvolvonut · 2020-11-23 00:32:37

When the mouse works:

$ uname -a
Linux serenity 5.9.1-arch1-1 #1 SMP PREEMPT Sat, 17 Oct 2020 13:30:37 +0000 x86_64 GNU/Linux

When the mouse is broken:

$ uname -a
Linux serenity 5.9.9-arch1-1 #1 SMP PREEMPT Wed, 18 Nov 2020 19:52:04 +0000 x86_64 GNU/Linux

paulkerry · 2020-11-23 10:14:52

Looking at the arch package release history for linux, 5.9.1 was committed on Oct 17, 2020 and there have been many USB changes in the kernel since then so it might be tricky to track down unless you want to do regression testing.
You could try installing linux-lts and if that works for you, stick to using that kernel.

Cheers
Paul.

thatvolvonut · 2020-11-25 00:38:55

Thanks for the tip! I poked around the various dmesg log levels, just to see if there was anything obvious, but nothing jumped out so I made the switch to linux-lts. Unfortunately, it has the same problems I'm seeing on kernels above 5.9.1. The weird thing is, I've been using this system for months and this has just now become an issue.

I've never really dug into the kernel before; maybe if I have some free time I'll try my hand at a bugfix... For now, I'll try custom-configuring a new kernel, and if I can't get that to work (or get frustrated with build times), I'll just build a custom named 5.9.1 to run so I can update my system normally

paulkerry · 2020-11-25 11:48:11

Is there any difference between 5.9.1 and the now available 5.9.10 with the kernel modules that are loaded? Use...

lsmod

Do the suggestions here help - https://wiki.archlinux.org/index.php/US … leshooting

thatvolvonut · 2020-11-26 03:25:11

Yes - I don't have output handy right now, but 5.9.1 loads the hid and usbhid modules, among others, on boot if the mouse is plugged in or on hotplug. Later kernels (including 5.9.10) do not load that, nor seemingly any other usb modules (other than *hci_pci and *hci_hcd, presumably for the 1.1 and 2.0 hubs). Even if I run:

#modprobe usbhid

devices attached to the hubs do not seem to exist to the kernel.

Thanks for the link, surprised I haven't stumbled across that myself! Alas, my BIOS is so old that there's maybe 20 options total, and the *HCI handoff options mentioned are not included. It does have a "USB 2.0 support" option, however, and that is enabled. Hmmmmm....maybe worth trying it disabled...

thatvolvonut · 2020-11-26 03:50:30

Grabbed a bit more info. Disabling USB 2.2 wasn't the easy fix I secretly hoped it would be

Onto lsmod dumps. This is running lsmod immediately after loading into SwayWM, on a fresh boot, with the mouse plugged in. I cleaned up the output so the diffs would be intelligible.

First off, 5.9.10 and lts have a few differences, but nothing that looks significant to my problem:

$ diff modules_5.9.10.txt modules_lts.txt
7c7
< snd_intel_dspcfg
---
> snd_intel_nhlt
31a32
> sd_mod
38a40
> libata
41a44
> scsi_mod
57,58d59
< cec
< rc_core

Next, 5.9.10 and 5.9.1 (differences look entirely related to my problem):

$ diff modules_5.9.10.txt modules_5.9.1.txt
4a5
> mousedev
15a17
> uas
17a20
> hid_generic
33a37,39
> usb_storage
> usbhid
> hid

And, for completeness, 5.9.1 and lts (just a mashup of the previous two):

$ diff modules_5.9.1.txt modules_lts.txt
5d4
< mousedev
8c7
< snd_intel_dspcfg
---
> snd_intel_nhlt
17d15
< uas
20d17
< hid_generic
34a32
> sd_mod
37,39d34
< usb_storage
< usbhid
< hid
44a40
> libata
47a44
> scsi_mod
63,64d59
< cec
< rc_core

[EDIT] tried modprobeing the missing modules from the 5.9.10/5.9.1 diff in a fresh 5.9.10 boot, to no effect.

Last edited by thatvolvonut (2020-11-26 03:58:09)

paulkerry · 2020-11-26 14:09:35

What happens if you don't run sway and go straight into a tty, then see what

lsusb

shows you?
I can't think of much else to try at this stage: it could be something to do with your specific motherboard hardware (you've not mentioned as yet what make/model you have apart from it being old).
I'm not sure if they would help, but maybe things like "iommu" kernel boot settings might be needed, for instance...
https://unix.stackexchange.com/question … -uefi-bios
You could try and see if a linux live usb stick boots up and does the mouse work OK with that?
If you have a ps/2 mouse port, do you have a ps/2->usb mouse dongle thing you could try?

thatvolvonut · 2020-11-26 16:14:56

lsusb from a plain tty just shows 4 hubs (3x 1.1, 1x 2.0). Also tried booting with "iommu" and with the latest installation media, both were a no-go.

A PS/2 adapter would get my mouse working (the only reason I can type is because I have a PS/2 keyboard), but I'd still need to solve the USB problem for other devices - thanks for the thought though!

My motherboard is pretty generic from what I'm seeing in my research, an RC410-M2 from ECS (https://www.ecs.com.tw/ECSWebSite/Product/Product_SPEC/EN/Motherboard/RC410-M2%20-LL-V1-DO-0-RR-/Socket%20775%20-LL-Intel-RR-). It has an the ATI RC410 chipset and is running AMI BIOS v02.58.

I tried custom-building the latest kernel with all seemingly relevant USB HID options enabled (not modularized), just for kicks and giggles, but it doesn't work.

I'm also at the end of my (admittedly very short) list of things to try - I'll just stay at 5.9.1 and/or play with boot flags for now until I can put some time into figuring out what the bug is. Thanks so much for all the thoughts, I really appreciate your time!

anarchuser · 2020-12-01 08:59:12

Thanks for all the research you've put into this. I am also facing the same issue on an Asrock 939Dual-SATA2 with a dual-core Opteron 175, with the latest 5.9.11 kernel as well: no USB mouse, but a Logitech webcam does get detected. I was about to do a custom build myself, but your last post spared it.

paulkerry · 2020-12-04 11:44:59

As @V1del mentions on https://bbs.archlinux.org/viewtopic.php?id=261322
you could try booting with usbcore.autosuspend=-1 to see if it helps?

V1del · 2020-12-04 12:28:17

based on this and the other topic I doubt it will help. Both of you use the ohci_driver so there's a potential regression here. I'd suggest you try to bisect the issue between these versions to find the commit that introduces the breakage and reporting it on bugzilla.kernel.org

anarchuser · 2020-12-12 22:08:52

I've built linux-git 5.10rc7.r220.g7f376f1917d7 and the USB mouse works again. Does this mean that we should just wait for the kernel 5.10 to make it to the core repository?

loqs · 2020-12-12 22:59:04

If it was only fixed in 5.10-rc7 i would suspect https://github.com/torvalds/linux/commi … 2c254346b3

anarchuser · 2020-12-18 06:45:28

Kernel 5.10.1 in testing solves it.

Arch Linux

#1 2020-11-22 19:58:43

5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

#2 2020-11-22 23:41:29

Re: 5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

#3 2020-11-23 00:32:37

Re: 5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

#4 2020-11-23 10:14:52

Re: 5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

#5 2020-11-25 00:38:55

Re: 5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

#6 2020-11-25 11:48:11

Re: 5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

#7 2020-11-26 03:25:11

Re: 5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

#8 2020-11-26 03:50:30

Re: 5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

#9 2020-11-26 14:09:35

Re: 5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

#10 2020-11-26 16:14:56

Re: 5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

#11 2020-12-01 08:59:12

Re: 5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

#12 2020-12-04 11:44:59

Re: 5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

#13 2020-12-04 12:28:17

Re: 5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

#14 2020-12-12 22:08:52

Re: 5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

#15 2020-12-12 22:59:04

Re: 5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

#16 2020-12-18 06:45:28

Re: 5.9.1 -> 5.9.X, Kernel Upgrade Breaks USB Mouse

Board footer