Deep sleep issues on linux

Which Linux distro are you using? Gentoo

Which release version? (If rolling release, last date updated?) Rolling, 2024/10/10

Which kernel are you using? 6.11.0

Which BIOS version are you using? 3.04

Which Framework Laptop 13 model are you using? (AMD Ryzen™ 7040 Series, Intel® Core™ Ultra Series 1, 13th Gen Intel® Core™ , 12th Gen Intel® Core™, 11th Gen Intel® Core™) 12th gen intel


Hi, I’ve been having troubles with the deep suspend mode. s2idle works fine but the battery will fully drain in about 5 hours which is not acceptable. As for deep, sometimes it works, sometimes it fails to sleep, instead just blanking the screen while the power button led remains continuously on and the battery drains, forcing me to hard reboot the system. There is no output in dmesg or Xorg.0.log during that time either.

It’s probably about 50/50 which outcome I get. I also feel like it has gotten worse recently but I can’t think of anything that’s changed so maybe that’s just superstition or my frustration speaking. I guess I updated the kernel (from 5.19.10) 3 months ago but this has been a problem since before then.

I read on this reddit thread that linux had these problems with 11th gen intels, but I have a 12th. I have never updated the BIOS since I got it 2 years ago, but I read in this forum thread that recent BIOS versions had sleep issues so I am wary of upgrading to a more broken state that I can’t back out of. I do not frequent the forums so my apologies if there was another important thread that I missed.

What should I do? Do I have to just live with s2idle forever? Are there any more logs or config settings I could share that would help? Is this known to be fixed in newer BIOS versions? Is there a hardware upgrade that would help? Thanks.

Hello @bubblingbeebles, I offer an interim answer to your question that might keep you going until someone more knowledgeable comes along.

I have a 12th Gen Intel FW13 (running LMC 21.1 and kernel 6.8.0-49-generic). Before I purchased this machine I planned to configure it to hibernate with encrypted backing store. I encountered bumps in that road. I chose the s2idle side track while I worked out how to swerve around the bumps. Here I am 22 months later and s2idle has only let me down twice.

Now we move further into the domain of anecdote. I’ve never been sufficiently disciplined (or flushed with time) to measure and document the idle time I get from my battery. However I can assure you that if it was as low as 5 hours I would long ago have gotten hibernation sorted.

My gut tells me I get at least 12 - 16 hours. If I did not, I’d have had more than 2 battery-depletion shut-downs.

The take-away from this long ramble–for you–is that it will be worth investigating why you only get 5 hours in s2idle before your battery is depleted. Seems to me it is probably not actually entering s2idle or that something is “waking” it prematurely once it gets there.

Dino

After my earlier reply I conducted an experiment. I measured the battery charge level immediately before closing the lid and again immediately after. On my 12th gen FW13 lid closure triggers s2idle. All 4 expansion bays are populated: USB C, USB A, microSDXC and a 1 TB storage module.

The average battery depletion over the last couple of days is 1% every 40 minutes.

Assuming my machine is fully charged when I finish work on a Friday, that depletion rate ensures it is still alive when I start work on Monday morning.

I’m not suggesting there is anything remarkable about how I have configured my machine. TBH I seldom think about battery life and take no overt steps to enhance it.

Dino
[edit: corrected storage module capacity]