@lvdd Did you try to use nvme.noacpi=1 as boot parameter? It drastically reduced the battery drain in s2idle for me to a similar level as deep (~ 0.5%/h).
Which of the Windows states s0, (. . . . s3 s4 etc.) do you consider ‘deep’
I don’t know the Windows states, but it should be s3.
0.5% of what per hour?
0.5% of battery charge level on a 55Wh battery would give 54/48 or just over 1.125 W/h
So my s3 is the same roughly at 1W/h
As for the Win states; Quoted July 2024
I’m stubborn and still trying to figure out why both of my 11th gen systems suspend and resume with no issues. Poor @lvdd ran through about eleventybillion different scenarios and didn’t get anywhere with determining why his system does not come back. It feels like a driver not reloading properly, but I am way out over my skis on this. I am just a dumb end user, tinkering and plinking away on the machine. I would love it if we could get an engineer (not Support - nothing against Support, but this is out of their realm as well) that would work with us to test working and non-working systems to try to narrow things down.
Damn, so much friction just to even ‘attempt’ to get it to sleep (and wake) right. (successfully or not).
@lvdd what distribution/kernel are you using? And anything else you can comment about your setup/software configuration/kernel parameters?
Hi Kieran,
thanks for chiming in.
There are a couple of links I posted with information about my system and the systemd journal during the death-loop. Also there is a description there how to reproduce it - at least on my laptop. The distribution doesn’t matter as I can easily reproduce it with Fedora 40, Debian stable and Archlinux.
The process for me is always the same:
Install a base system with Gnome (for convenience)
Add mem_sleep_default=deep via grub to the commandline
put the laptop to sleep via powerbutton
It goes to sleep but is not waking up anymore with the effect I have outlined here: Sleep issues after 3.19 BIOS update - 11th Gen Intel Framework 13 - #28 by lvdd
The point here is that this happened after I upgraded the BIOS from 3.17 to 3.20. All of the above was working fine before. Which lets me believe that this is not an issue with Linux Kernel changes but something being introduced with the BIOS.
If I could somehow go back to 3.17 I would do that and never touch BIOS again.
@lvdd for the bios update to 3.20 we updated the core bios kernel from Insyde, and CSME, and I suspect a change in there may have broken this somehow. Your support request got to me, and I was the one who gave the statement that S3 sleep is not supported.
This is actually the official stance of Intel supported sleep states from Intel. So even though it previously did work is was not an officially supported configuration.
I am not sure exactly where this got broken, but other vendors have documented similar issues with removed/missing S3 sleep, and the requirement for CSME to support S0ix sleep. Eg https://www.reddit.com/r/System76/comments/k7xrtz/comment/gev9mkp/?utm_source=reddit&utm_medium=web2x&context=3
We can do a quick pass to see if there was something that changed which caused this to be removed, however this may be something in CSME or other components which is not fixable by us. So no guarantees if this can be fixed, and no set timeline. (I would continue to operate under the assumption that this is not going to be fixed for now).
I would have to go back and measure again for this release, but we have generally found that Linux does a much better job with S0ix sleep power drain than windows. Eg on older intel platforms I think we were ball-parking around 300mW for Windows, and around 260mW for Linux.
Regarding that may be true the s3 doesn’t actually work as a quick wake up, it’s slower than hibernate and logs me out, so I’m back to s0, which works fine but does use watts of power.
Yes, I can attest to this.
I can tell you that S0 is definitely not better on my system. When I put the laptop into suspend with s2idle in the evening with 10-15% battery left, it is dead the next morning with the battery fully drained, which was not the case with S3. I quite often have the situation that the system pretends to go into suspend - turning display off and powerbutton flashing but the fan keeps actually running and the system stays warm to the touch. I got into the habit of listening on the backside of the laptop to make sure it really has gone to sleep. That has always been the case since I got it and I was happy when S3 was working after a while.
Ok, that means I have a laptop with a crappy CPU that got actively crippled by some moronic Intel decision? I didn’t know that and I am not sure I should be required to dig that deep into CPU design to learn about these traps upfront. That means I now have to get hibernate running as this is the only way to keep this laptop useful for me.
All of that is deeply disappointing and already shaped my decision making for the future.
BTW: It would really be beneficial to have a sleep indicator on the side of the laptop and not just with the powerbutton, as it is impossible to see with the screen closed.
One last thing. It seems other manufacturers have found a solution for their systems with this crippled CPU:
That’s so easy, well actually it was already an option on Win10 and upgrading to Win 11 didn’t remove it.
Sleep is dirty and for what a few more seconds either way.
On my 11th Gen 8 secs to power down and 8 seconds to power up.
If you have problems like
or cmd powercfg /hibernate on
Why would it break on some systems but not on others? Both of my 11th gen systems are on 3.20 and using deep sleep with no issues.
Interesting, so yours work ok? What linux distro are you using/kernel? Also what expansion cards do you have installed?
Yes, one machine is on arch, the other on manjaro. Both are on the latest 6.11.x kernel (I can fire them up and check the specifics if you need that).
Arch system:
Manjaro system:
Thank you for engaging, I’m happy to try to help figure out what is different.
I have a 11gen from batch 8 with i51135G7
my lshw:
https://anonpaste.org/?3eae53d556646837#CXqnVYQP1cpJE1EJoSdfdRQgmVia8bwWqRjig4sCU8QD
Hi. About to look at this.
I dual boot Win 11 and Ubuntu. I use Win most of the time with hibernate but some 6 hours ago I closed my lid using Ubuntu to find some 28% of the battery drained after 6 hours. So I will look into the Linux sleep tweeks.
Thanks for your info
I have a Batch 8 with 1165G7
I wonder how many people are actually not aware of the sub-par out-of-the-box behavior under Linux because they use their devices differently, so they don’t run into these things - at least not right away.
For me deep sleep is not working anymore with 3.20 on Archlinux.
Batch 9
Intel i7-1165G7
AX210 WiFi
WD_BLACK™ SN850 NVMe™ - M.2 2230 - 1TB
DDR4-3200 - 16GB (2 x 8GB)
4 x USB-C
It’s a bit of a joke, that the community needs to debug this instead of their own QA, but deep sleep is no longer working for me either after the 3.20 update on Ubuntu:
Batch 9
11th Gen Intel® Core™ i7-1165G7
AX210 WiFi
WDS100T1X0E-00AFY0 (614600WD) NVMe
2x 16GB CT16G4SFRA32A
2x USB-C + 2x USB-A