6.17.10 broke my standby (Lenovo Yoga 7, s2idle)

Ask Fedora
21

Still broken in 6.18.3 for me.

22

I wouldn’t hold my breath for it in 6.18. According to the kernel git logs, the fix commit appears only in 6.19:

$ git tag --contains 3925683515e9
v6.19-rc1
v6.19-rc2
v6.19-rc3
v6.19-rc4
1 Like
23

I tried 6.18.0 via Rawhide, and it still didn’t work for me.

Sad to hear it’ll likely be pushed to 6.19.

How did you get 6.18.3?

Edit: Oh, just realized 6.18.3 is available through dnf now.

I have an exclude set for all kernel updates since 6.17.1 is the most stable one for me.

24

Regular updates from the repos (I use the KDE spin of Feroda 43 in case it makes a difference).

25

Yeah, same Fedora 43 Plasma, just realized it’s been released. I have an exclude set in dnf for kernel updates since 6.17.1 is the only one that is mostly functional… so long as I don’t dock or undock my laptop while asleep.

26

Had to be academic about it and try 6.18.3 myself, and indeed it’s still broken. It completely locks up if you put the computer to sleep, after connecting and disconnecting some TB4 devices.

27

I’m also having trouble suspending on my Lenovo IdeaPad Pro 5 (14AKP10), but I actually get into the lock screen after resuming from sleep. It’s just completely broken with no images or icons loading and I can’t log in. I tried compiling the kernel with the fix applied but it didn’t help.. in fact, I get the error message that the fix is supposed to prevent on successful resume attempts. When I wake the laptop and reach the broken login screen it produces no logs in jorunalctl after it states it successfully reached sleep. I opened a thread about it here assuming it’s probably a different issue, but I find it interesting I get the error and can still resume just fine. Suspend leaves laptop in a broken state (Lenovo IdeaPad Pro 5 14AKP10)

28

Independend from the standby issue on some kernels, is there any way to make s2idle resume faster after standby?

It usually takes about 10s for my laptop to resume, while my other laptop that supports & uses S3 wakes up basically instandly.

On my s2idle only laptop I believe it has something todo with the time spend in standby. It’s fatser if my system wasn’t asleep for too long. The hardware goes to some “deeper” sleep state probably, since the battery consumption in standby is very low (I lose 1% in about 5h), but I would prefer a faster resume time instead.