Bugzilla – Bug 1223164
Unplugging charger while in s2idle sleep causes laptop to stop responding
Last modified: 2024-04-21 10:25:50 UTC
Specs: Laptop Model: Lenovo Ideapad 5 PRO 14ARH7 CPU: Ryzen 7 6800HS Creator Edition GPU: Integrated: AMD Radeon 680M RAM: 16 GB Wifi Card: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter Storage: 1TB M.2 NVME WD PC SN810 SDCPNRY-1T00-1101 This laptop supports s2idle sleep only. When the laptop is in sleep mode, everything works properly, there is almost no battery drain. However, when I plug in or unplug my charger, the laptop will no longer responds to any inputs and can no longer be woken up. The keyboard backlight briefly flashes and the laptop starts producing heat and the only way to get out of sleep mode is to hold the power button for 5 seconds to forcefully shut it down. Alt + Sysrq + b does nothing. I have tried setting TLP_ENABLE=0 and rebooting. That does not seem to help. The only thing that changes is that now the fans spin up once the laptop gets stuck and the keyboard backlight no longer flashes. There are no errors present in journalctl -b -1 after rebooting. The last message is that the laptop successfully entered s2idle sleep mode. I have tried the Live environment of a different distribution according to a few tips online. Fedora 39 live environment does not have this issue. Either this bug is specific to this distribution or I messed something up with my installation. I could not figure out what could cause this. This issue is present on kernel versions 6.5, 6.6, 6.7 and 6.8. I haven't tried any other versions.
I forgot to mention, this laptop only supports USB-C power delivery charging at 65W. There is no proprietary charger that I could use on this laptop.
Nevermind. The problem was in the TLP package. Even if I disable it by setting TLP_ENABLE=0, it was still doing something in the background causing this issue, despite tlp-stat -s saying it's disabled. By reinstalling the package, thus resetting all configurations to default, the issues are now fixed.