My notebook cannot resume from sleep, reboots instead

Ask Fedora
, ,
1

Hello Everyone,

I noticed a strange behaviour, after I put my ThinkPad to sleep (closing lid or clicking “sleep” icon), it goes to sleep for time but after that it won’t wake up when I open the lid or press some buttons, it just reboots instead. I can replicate it everytime.
It was not happening before, I remember my notebook can sleep and wake up some time ago (maybe months ago, maybe years ago). I do not know when this issue started happening because I haven’t put it into sleep for a while.

I am using Kinoite 42 on a ThinkPad E595 - hardware probe here: HW probe of Lenovo ThinkPad E595 20NF00... #66ac47b979

rpm-ostree status:

● fedora:fedora/42/x86_64/kinoite
                  Version: 42.20250627.0 (2025-06-27T00:47:12Z)
                   Commit: bb3451c63a28b8befbd3a9c5fc499435c6f8f58d75b3398eb62473eff27c23cc
             GPGSignature: Valid signature by B0F4950458F69E1150C6C5EDC8AC4916105EF944

uname -a:

Linux thinkpad 6.15.3-200.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jun 19 15:00:25 UTC 2025 x86_64 GNU/Linux

free -ht:

               total        used        free      shared  buff/cache   available
Mem:            13Gi       2,7Gi       4,6Gi        48Mi       6,6Gi        10Gi
Swap:          8,0Gi          0B       8,0Gi
Total:          21Gi       2,7Gi        12Gi
2

If you can find when it started not working that would help. It’s likely a kernel regression. See: Updates, Upgrades & Rollbacks :: Fedora Docs to test older versions.

1 Like
3

Can you also provide the output of cat /sys/power/mem_sleep? I’m wondering if you only have s2idle available or if there is still S3 sleep, which usually works much better.

4

cat /sys/power/mem_sleep:
s2idle [deep]

5

Hopefully I’ll rollback to when this issue started to happen. It may take some time, I’ll update the topic.

Thanks a lot for your answers

1 Like
6

If it is hanging with deep (S3), it could also be a firmware issue. Make sure you have the latest BIOS applied, as there have been issues that prevented suspend from working on this exact laptop model.

Otherwise, check the logs after you restart it using journalctl -b 1 to see if there is anything logged at all, such as errors during suspend or anything during resume.

7

Thanks for your suggestion!
I cannot see anything useful here (I’m not an expert though)… got the logs after a sleepy reboot.

https://paste.centos.org/view/121dcaef