I’ve run Fedora KDE spin on a Thinkpad T460 laptop (8GB, Intel® Core™ i5-6300U, Intel HD Graphics 520) with external monitor and Logitech wireless USB mouse for 7 years, the last few atop Wayland. In that time suspend has worked reasonably well; sometimes the laptop comes out of suspend “on its own” within minutes of entering suspend (web search suggests this might be a USB issue).
But for a few weeks now, I resume after choosing Sleep in KDE, and soon in the middle of typing the system hangs. No cursor motion, keyboard unresponsive, lid close does nothing; if the fan was on it stays on. I can only do a hard power-off. Upon powering on, there is no journald information about the hang, typically no journald entries from around the hang, and then lots of boot logging with no obvious smoking gun. One non-standard thing about my setup is I mount an NTFS partition read-write with documents and Firefox and Thunderbird app data (not kernel, not root, not home directories) using the ntfs-3g userspace driver; maybe that FUSE driver hangs hard, maybe when KDE’s baloo indexer reindexes some file on NTFS? But this is pure conjecture, and doesn’t explain why it never hangs until after I suspend then resume.
I always and mostly run konsole, Firefox and Thunderbird for Wayland, and KeePassXC. The hang has occurred while typing in the terminal, typing in Firefox, and once just typing my password at the lock screen. It’s usually within a few minutes of resuming. I don’t think it’s hung while just browsing and scrolling. It doesn’t seem a hardware problem since I’ve never had a hang after power-on, only after resume from suspend.
Any suggestions in how to debug this? I can’t find a Fedora guide to debugging suspend-resume. Is Ubuntu’s guide appropriate? It suggests enabling /sys/power/pm_trace. Others suggest disabling the kernel i915 Intel graphics driver. The wrinkle here is that suspend and resume both seem to work, but shortly after resume I reliably experience the hard hang. So maybe I need to consult a “debugging input hangs” guide. Thanks!
I’m working on a Thinkpad X270 and I’m experiencing the same. Similar for other Thinkpad notebooks (also X270s) in my family.
Behavior is always the same: during typing - and only during typing - the machine locks up and becomes fatally unresponsive. I didn’t notice that this only occurs after a resume from suspend, but your correct; the machine does not freeze when freshly rebooted.
I’ve also noticed the upper mouse buttons (the ones with the red stripe) becoming unresponsive after a resume from suspend, sometimes. In these cases I need to either unload/reload the drivers or just suspend/resume again.
I have not yet been able to find out, what the cause is.
I found something, but I doubt that it is related. This has to do with wifi.
Mai 25 00:33:43 abrt-notification[3374]: [🡕] System encountered a non-fatal error in iwl_mvm_rx_umac_scan_complete_notif()
░░ Subject: ABRT has detected a non-fatal system error
░░ Defined-By: ABRT
░░ Support: https://bugzilla.redhat.com/
░░ Documentation: man:abrt(1)
░░
░░ WARNING: CPU: 0 PID: 9847 at drivers/net/wireless/intel/iwlwifi/mvm/scan.c:3158 iwl_mvm_rx_umac_scan_complete_notif+0x1f8/0x210 [iwlmvm] [iwlmvm]
░░
░░ Use the abrt command-line tool for further analysis or to report
░░ the problem to the appropriate support site.
I’ll try to see if I can get anything out of abrt.
Thanks for chiming in! I had given up and just stopped using standby/suspend . I looked in the logs I saved back in October 2023 and there were no usb .* (WARN|Device not responding or soft lockup messages. I did have a Logitech F310 USB gamepad plugged in back then but I’m pretty sure I tried unplugging it. Did you do anything to get more log output?
I never use the Thinkpad’s mouse buttons above the trackpad, or its “mouse nipple.”
One time in May 2024, processes on my Thinkpad started hanging and there were messages like
May 04 18:41:20 fedlaptop kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 708s! [kworker/2:0:173352]
in journalctl. But I was able to continue in some windows, it wasn’t an immediate hard total lockup while typing. I don’t think this happened since.
I’ll start using standby/suspend again. If anyone has guidance to get more potentially useful kernel logging, thanks in advance!
… and my Thinkpad running KDE hasn’t hung in 10 or so suspend/resume cycles!
Maybe software improvements since September 2023 fixed the hard hangs. Also, in the interim I switched from GRUB 2 to systemd-boot (losing secure boot).
. I looked in the logs I saved back in October 2023 and there were no 