OS Name: Fedora Linux 41 (Workstation Edition Prerelease)
OS Build: (null)
OS Type: 64-bit
GNOME Version: 47
Windowing System: Wayland
Kernel Version: Linux 6.11.0-63.fc41.x86_64
Running ./s0ix-selftest-tool.sh -s gives me:
---Check S2idle path S0ix Residency---:
The system OS Kernel version is:
Linux DevStation 6.11.0-63.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Sep 15 17:48:54 UTC 2024 x86_64 GNU/Linux
---Check whether your system supports S0ix or not---:
Low Power S0 Idle is:1
Your system supports low power S0 idle capability.
---Check whether intel_pmc_core sysfs files exit---:
The pmc_core debug sysfs files are OK on your system.
---Judge PC10, S0ix residency available status---:
Test system supports S0ix.y substate
S0ix substate before S2idle:
S0i2.0 S0i2.1 S0i2.2
S0ix substate residency before S2idle:
0 0 0
The system failed to place S2idle entry command by turbostat,
please check if the suspend is failed or turbostat tool version is old
e.g. did you make turbostat tool executable or separately run S2idle command:
rtcwake -m freeze -s 15
I guess I forgot to describe the actual issue In short, nothing happens when i close the lid and when I select ‘Suspend’, the screen goes blank for a moment and then returns with lock screen. Same behavior also on Fedora 40.
This makes me wonder tho. What is the expected behavior, when your system doesn’t support S3, but you close the lid or request suspend? Is the system not meant go quiet anymore, because that’s what my boomer ass was expecting
Can you make sure you have turbostat on the system (and you can use the one that is in the S0ixSelftestTool repository that you got the test executable from).
Hopefully that will give you a fuller report - the one provided isn’t useful I’m afraid.
For your Q about suspend - it uses S0ix sleep (aka modern standby) instead (which replaces S3). Intel (and AMD) don’t support S3 on their CPUs any more - we only certify our systems with S0ix.