With one of the latest updates to fedora 38, I have been experience system failure when I disconnect my USB devices. I have a USB switcher that I use to switch my keyboard and mouse from my work computer to my framework. This is the same setup I have had since I got my framework about a year ago. Just last week every time I switch my keyboard and mouse away from my framework, it effectively crashes. the USB becomes non functional and I have to hard power off to get the system to respond again.
Which OS (Operating System)? Fedora
Which release of your OS (Operating System)? Fedora 38
It worked as expected on the fedora live ISO. And it appears to be working well on 6.3.13 kernel. The issue was very easy to reproduce before and I have not been replicate it on 6.3.13 so far. I think I should be in good shape for now.
Delighted to hear you have this sorted with 6.3.13 - this is not something I’ve experienced on the other kernels myself, but the important thing is 6.3.13 has not been an issue yet.
If it crops up again, please do share what device specifically seems to set it off. In the meantime, I’ll mark this as resolved.
Just wanted to comment that this is not just a framework issue nor just a Fedora 38 issue. I had the same thing happen (very similar call stack) with Fedora 37 on a Thinkpad T14s.
It would take approx 24 hours before the bug would occur, but once it did a hard poweroff was required to fix.
For sure this occurred on 6.4.9-100.fc47, 6.4.10-100.fc47, 6.4.11-100.fc47, 6.4.12-100.fc47
Appreciate this. I am putting together a list for the Fedora team, for you, this occurred on 37 with kernels listed. Noted and added to my running list.
@Matt_Hartley I’m not sure - I just rebooted to that version to give it a try. When it happened in the past it took about a day to occur. I’ll try and get an update tomorrow - if I don’t reply by Wednesday night feel free to give me a poke. (going on vacation early wed morning so tomorrow night might be a bit hectic)
Hi,
not a framework user but wanted to report that I have the exact same crash on usb hub switching away from this machine.
Not sure when it started but fairly rececentyl, on 6.4.12 on arch-linux now (6.4.9 previously, I think I had a crash there as well).
Cannot upgrade to latest 6.4 unfortunately since the linux package have already moved on 6.5 (which I cannot use yet since it is not compatible with zfs).
Appreciate you sharing your experiences with the kernel, even if not on a Framework 13 laptop.
In my a Fedora 37 install (I use both 37 and 38), kernel 6.4.13-100.fc37.x86_64 and no such issues here. I am seeing this happening on Arch specifically here in the community, but my bigger concern is seeing this on Fedora - if it’s not happening on Fedora, I am feeling reasonably good overall as Fedora 37/38 are officially supported by us.
Hi Matt - I am still experiencing this issue with a lot of the newer kernels including 6.4.14-200.fc38 on Fedora 38. My system is now version locked 6.3.13-200.fc38.x86_64 and is stable. Something in the later 6.4. kernels do not like my setup. I am happy to provide any info you like. Let me know and thank you @Matt_Hartley !
Onboard USB ports on Asus X570 Prime motherboard with AMD Ryzen 5900x. lspci reports as USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
Aten US224 USB switch, with a Logitech wireless keyboard & a yubikey
A lot of things running, keyboard and yubikey not in active use while switching
Problem does not always occur on switching, only sometimes. And only when switching away from this machine.
Result is semi-hung machine, existing TCP connections seems to work but cannot make new ones, some new processes cannot be started (like sudo) but others seems to work (new foot terminal). Can close all apps but cannot succeed in a graceful reboot, so have to do hard poweroff.
This is happening due to a bug in the hid_logitech_dj kernel module, which occurs when a Logitech Unifying (as well as Bolt and other dongles I believe) is disconnected (not all the time, but often enough for it to happen to me regularly).
Just to confirm, if you check the stack traces when this occurs, somewhere higher up in the trace will be a call to logi_dj_remove, which is part of the hid_logitech_dj kernel module. Every stack trace I’ve seen describing this issue, including my own, has had this in the call stack.
I solved this on my systems by blacklisting the hid_logitech_dj kernel module about 10 days ago and have not had the issue since. I was previously running into this issue multiple times a day as I use a KVM to switch between machines and was happening nearly every 2-3 switches.
To work around this on your system, create a file at /etc/modprobe.d/logitech-blacklist.conf with the following contents:
blacklist hid_logitech_dj
Then update your initramfs and reboot; for Arch it’s mkinitcpio -P, debian is update-initramfs -u -k all, and I believe fedora is dracut --regenerate-all.
Fedora 3x? 38
Kernel in use when this happened? 6.4.14-200.fc38.x86_64
Which expansion cards are in use? USB-A, C, HDMI, etc? 2 usbc, 1 usbA, ethernet
Do you use a USB dock and is it connected when this is happening? yes
Software open when this happens? clean boot then opened 2 terminal windows in gnome
Bat or AC power? ac
lsub just before crash on disconnect
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 003 Device 010: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 009: ID 1b1c:1b2d Corsair K95 RGB Platinum Keyboard [RGP0056]
Bus 003 Device 008: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 002: ID 04e8:a020 Samsung Electronics Co., Ltd 4-Port USB 2.0 Hub
Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
After seeing @ryanpetris comment I tried removing the logitech dongle from the mix, and interestingly enough the problem only happens if the Logitech Unifying receiver is connected. This is with 6.4.14-200.fc38.x86_64.