What is Ubuntu doing different than opensuse regarding s2idle?

My laptop can not goto sleep.
I used the S0ixSelftestTool to check, if the hardware is working. When using a Lubuntu live stick, the self-test tool states “Congratulations! Your system achieved the deepest S0ix substate!”. When closing the laptop lid with running Lubuntu, the system goes to hibernation and the power consumption is very low.

full log ubuntu
---Check S2idle path S0ix Residency---:

The system OS Kernel version is:
Linux lubuntu 6.11.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 16 13:41:20 UTC 2024 x86_64 x86_64 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

S0ix substate residency before S2idle:
  9757682

Turbostat output: 
15.220486 sec
CPU%c1	CPU%c6	CPU%c7	Pkg%pc2	Pkg%pc3	Pkg%pc6	Pkg%pc8	Pk%pc10	SYS%LPI
1.86	66.03	32.27	1.62	0.00	0.00	0.78	89.75	86.51
1.92	0.08	97.07	1.62	0.00	0.00	0.78	89.75	86.51
1.92
1.83	0.10	97.88
1.83
5.96	0.19	93.44
5.96
1.17	0.04	98.80
1.17
0.94	99.20	0.00
1.26	98.75	0.00
0.85	99.16	0.00
1.22	98.95	0.00
1.08	99.15	0.00
0.87	99.30	0.00
0.64	99.56	0.00
1.15	97.93	0.00

CPU Core C7 residency after S2idle is: 32.27
CPU Package C-state 2 residency after S2idle is: 1.62
CPU Package C-state 3 residency after S2idle is: 0.00
CPU Package C-state 8 residency after S2idle is: 0.78
CPU Package C-state 10 residency after S2idle is: 89.75
S0ix residency after S2idle is: 86.51

S0ix substate after S2idle:
  S0i2.0

S0ix substate residency after S2idle:
  22925294

S0ix substates residency delta value: S0i2.0 13167612

Congratulations! Your system achieved the deepest S0ix substate!           
Here is the S0ix substates status: 
Substate   Residency      
S0i2.0     22925294       

When running the self-test tool on tumbleweed I get: “Your system CPU Core C7, GFX RC6, PCIe Device D state and Link PM state are OK, but still did not achieve PC8 after powertop --auto-tune”.

full log opensuse

---Check S2idle path S0ix Residency---:

The system OS Kernel version is:
Linux localhost.localdomain 6.18.2-1-default #1 SMP PREEMPT_DYNAMIC Fri Dec 19 10:15:01 UTC 2025 (9447271) x86_64 x86_64 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

S0ix substate residency before S2idle:
  0

Turbostat output: 
15.360648 sec
CPU%c1	CPU%c6	CPU%c7	Pkg%pc2	Pkg%pc3	Pkg%pc6	Pkg%pc8	Pk%pc10	SYS%LPI
1.11	66.03	32.55	43.25	51.84	0.00	0.00	0.00	0.00
1.45	0.45	96.79	43.25	51.85	0.00	0.00	0.00	0.00
1.45
1.04	0.26	98.14
1.04
1.48	0.23	97.50
1.48
0.99	0.21	98.17
0.99
1.19	98.51	0.00
0.95	99.06	0.00
0.75	99.29	0.00
0.94	99.04	0.00
1.00	99.11	0.00
0.68	99.52	0.00
0.74	99.37	0.00
1.50	97.30	0.00

CPU Core C7 residency after S2idle is: 32.55
CPU Package C-state 2 residency after S2idle is: 43.25
CPU Package C-state 3 residency after S2idle is: 51.84
CPU Package C-state 8 residency after S2idle is: 0.00
CPU Package C-state 10 residency after S2idle is: 0.00
S0ix residency after S2idle is: 0.00

Your system achieved PC3 residency: 51.84, but no PC8 residency during S2idle: 0.00

---Debug no PC8 residency scenario---:

Turbostat output: 

14.876421 sec
CPU%c1	CPU%c6	CPU%c7	Pkg%pc2	Pkg%pc3	Pkg%pc6	Pkg%pc8	Pk%pc10	SYS%LPI
0.53	66.53	32.78	6.80	88.81	0.00	0.00	0.00	0.00
0.75	0.65	97.47	6.80	88.82	0.00	0.00	0.00	0.00
0.75
0.56	0.30	98.89
0.56
1.15	0.28	98.27
1.15
0.58	0.53	98.68
0.58
0.27	99.75	0.00
0.22	99.74	0.00
0.19	99.88	0.00
0.37	99.73	0.00
0.19	99.94	0.00
0.38	99.72	0.00
0.19	99.86	0.00
0.63	97.94	0.00

Your CPU Core C7 residency is available: 32.78

Checking PCIe Device D state and Bridge Link state:


0000:00:07.0 Link is in Detect

The link power management state of PCIe bridge: 0000:00:07.0 is OK.

The PCIe bridge link power management state is:
e[31m10000:e0:06.0 Link is in L0e[0m

The link power management state of PCIe bridge: e[31m10000:e0:06.0e[0m is not expected. 
which is expected to be L1.1 or L1.2, or user would run this script again.


The L1SubCap of the failed 10000:e0:06.0 is:
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+

The L1SubCtl1 of the failed 10000:e0:06.0 is:
		L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-


Checking PCI Devices tree diagram:
-[0000:00]-+-00.0  Intel Corporation Raptor Lake-P/U 4p+8e cores Host Bridge/DRAM Controller
           +-02.0  Intel Corporation Raptor Lake-P [Iris Xe Graphics]
           +-04.0  Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant
           +-06.0  Intel Corporation RST VMD Managed Controller
           +-07.0-[01-38]--
           +-08.0  Intel Corporation GNA Scoring Accelerator module
           +-0d.0  Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller
           +-0d.2  Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #0
           +-0e.0  Intel Corporation Volume Management Device NVMe RAID Controller Intel Corporation
           +-12.0  Intel Corporation Alder Lake-P Integrated Sensor Hub
           +-14.0  Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller
           +-14.2  Intel Corporation Alder Lake PCH Shared SRAM
           +-14.3  Intel Corporation Raptor Lake PCH CNVi WiFi
           +-15.0  Intel Corporation Alder Lake PCH Serial IO I2C Controller #0
           +-15.1  Intel Corporation Alder Lake PCH Serial IO I2C Controller #1
           +-16.0  Intel Corporation Alder Lake PCH HECI Controller
           +-1f.0  Intel Corporation Raptor Lake LPC/eSPI Controller
           +-1f.3  Intel Corporation Raptor Lake-P/U/H cAVS
           +-1f.4  Intel Corporation Alder Lake PCH-P SMBus Host Controller
           \-1f.5  Intel Corporation Alder Lake-P PCH SPI Controller
-[10000:e0]---06.0-[e1]----00.0  Samsung Electronics Co Ltd NVMe SSD Controller PM9B1 (DRAM-less)


Your system CPU Core C7, GFX RC6, PCIe Device D state and Link PM state are OK, 
but still did not achieve PC8 after powertop --auto-tune

My question is: What is the difference between ubuntu and opensuse in configuration (?) regarding the possibility to use s2idle? What can I do to enable hibernation on tumbleweed?

@dojo Hi and welcome to the Forum :smile:
I assume you have secure boot enabled? The Tumbleweed kernel is locked down for security, which disables hibernation, suspend only… else disable secure boot and all should function.

Check the output of fwupdmgr security to see what the settings are in your test distribution.

1 Like

Thanks for your quick response.
I had indeed secure boot enabled. After disabling, output of the self-test tool changed but still states no success.

full log
---Check S2idle path S0ix Residency---:

The system OS Kernel version is:
Linux p200300ecdf3d36bc472bb6492f5cb333.dip0.t-ipconnect.de 6.18.2-1-default #1 SMP PREEMPT_DYNAMIC Fri Dec 19 10:15:01 UTC 2025 (9447271) x86_64 x86_64 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

S0ix substate residency before S2idle:
  0

Turbostat output: 
15.909087 sec
CPU%c1  CPU%c6  CPU%c7  Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc8 Pk%pc10 SYS%LPI
1.08    65.73   32.43   6.29    88.19   0.00    0.00    0.00    0.00
1.38    0.37    96.36   6.29    88.19   0.00    0.00    0.00    0.00
1.38
0.80    0.35    98.01
0.80
1.31    0.17    97.61
1.31
1.67    0.25    97.16
1.67
0.75    98.47   0.00
0.87    98.60   0.00
0.68    98.72   0.00
0.75    98.65   0.00
0.75    98.76   0.00
0.62    98.86   0.00
0.85    98.70   0.00
1.66    96.82   0.00

CPU Core C7 residency after S2idle is: 32.43
CPU Package C-state 2 residency after S2idle is: 6.29
CPU Package C-state 3 residency after S2idle is: 88.19
CPU Package C-state 8 residency after S2idle is: 0.00
CPU Package C-state 10 residency after S2idle is: 0.00
S0ix residency after S2idle is: 0.00

Your system achieved PC3 residency: 88.19, but no PC8 residency during S2idle: 0.00

---Debug no PC8 residency scenario---:
modprobe cpufreq_stats failed
Loaded 0 prior measurements
RAPL device for cpu 0
RAPL Using PowerCap Sysfs : Domain Mask d
RAPL device for cpu 0
RAPL Using PowerCap Sysfs : Domain Mask d
Devfreq not enabled
glob returned GLOB_ABORTED
Leaving PowerTOP

Turbostat output: 

14.942829 sec
CPU%c1  CPU%c6  CPU%c7  Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc8 Pk%pc10 SYS%LPI
1.13    65.82   32.38   6.48    88.02   0.00    0.00    0.00    0.00
1.81    0.34    96.04   6.48    88.02   0.00    0.00    0.00    0.00
1.81
1.00    0.15    98.15
1.00
1.38    0.44    97.30
1.38
1.79    0.15    97.04
1.79
0.72    98.76   0.00
0.50    98.98   0.00
0.40    99.11   0.00
0.99    98.41   0.00
0.93    98.53   0.00
0.56    98.92   0.00
0.36    99.23   0.00
1.64    96.84   0.00

Your CPU Core C7 residency is available: 32.38

Checking PCIe Device D state and Bridge Link state:

Available bridge device: 0000:00:07.0 10000:e0:06.0

0000:00:07.0 Link is in Detect

The link power management state of PCIe bridge: 0000:00:07.0 is OK.

The PCIe bridge link power management state is:
10000:e0:06.0 Link is in L0

The link power management state of PCIe bridge: 10000:e0:06.0 is not expected. 
which is expected to be L1.1 or L1.2, or user would run this script again.


The L1SubCap of the failed 10000:e0:06.0 is:
                L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+

The L1SubCtl1 of the failed 10000:e0:06.0 is:
                L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-


Checking PCI Devices tree diagram:
-[0000:00]-+-00.0  Intel Corporation Raptor Lake-P/U 4p+8e cores Host Bridge/DRAM Controller
           +-02.0  Intel Corporation Raptor Lake-P [Iris Xe Graphics]
           +-04.0  Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant
           +-06.0  Intel Corporation RST VMD Managed Controller
           +-07.0-[01-38]--
           +-08.0  Intel Corporation GNA Scoring Accelerator module
           +-0d.0  Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller
           +-0d.2  Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #0
           +-0e.0  Intel Corporation Volume Management Device NVMe RAID Controller Intel Corporation
           +-12.0  Intel Corporation Alder Lake-P Integrated Sensor Hub
           +-14.0  Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller
           +-14.2  Intel Corporation Alder Lake PCH Shared SRAM
           +-14.3  Intel Corporation Raptor Lake PCH CNVi WiFi
           +-15.0  Intel Corporation Alder Lake PCH Serial IO I2C Controller #0
           +-15.1  Intel Corporation Alder Lake PCH Serial IO I2C Controller #1
           +-16.0  Intel Corporation Alder Lake PCH HECI Controller
           +-1f.0  Intel Corporation Raptor Lake LPC/eSPI Controller
           +-1f.3  Intel Corporation Raptor Lake-P/U/H cAVS
           +-1f.4  Intel Corporation Alder Lake PCH-P SMBus Host Controller
           \-1f.5  Intel Corporation Alder Lake-P PCH SPI Controller
-[10000:e0]---06.0-[e1]----00.0  Samsung Electronics Co Ltd NVMe SSD Controller PM9B1 (DRAM-less)


Checking PCI Devices D3 States:
[  129.042317] [    T121] intel_ish_ipc 0000:00:12.0: PCI PM: Suspend power state: D0
[  129.042321] [    T121] intel_ish_ipc 0000:00:12.0: PCI PM: Skipped
[  129.044852] [   T4180] i801_smbus 0000:00:1f.4: PCI PM: Suspend power state: D0
[  129.044859] [   T4180] i801_smbus 0000:00:1f.4: PCI PM: Skipped
[  129.052822] [   T4182] proc_thermal_pci 0000:00:04.0: PCI PM: Suspend power state: D3hot
[  129.053006] [   T4177] sof-audio-pci-intel-tgl 0000:00:1f.3: PCI PM: Suspend power state: D3hot
[  129.053027] [   T4176] i915 0000:00:02.0: PCI PM: Suspend power state: D3hot
[  129.054548] [   T4179] nvme 10000:e1:00.0: PCI PM: Suspend power state: D3hot
[  129.057714] [   T4168] xhci_hcd 0000:00:0d.0: PCI PM: Suspend power state: D3cold
[  129.058126] [   T4178] mei_me 0000:00:16.0: PCI PM: Suspend power state: D3hot
[  129.059413] [   T4170] intel-lpss 0000:00:15.1: PCI PM: Suspend power state: D3hot
[  129.059993] [   T4167] xhci_hcd 0000:00:14.0: PCI PM: Suspend power state: D3hot
[  129.060241] [    T120] iwlwifi 0000:00:14.3: PCI PM: Suspend power state: D3hot
[  129.061600] [   T4174] pcieport 0000:00:07.0: PCI PM: Suspend power state: D3cold
[  129.066748] [   T4171] pcieport 10000:e0:06.0: PCI PM: Suspend power state: D3hot
[  129.076936] [    T121] thunderbolt 0000:00:0d.2: PCI PM: Suspend power state: D3cold
[  129.079218] [   T4166] vmd 0000:00:0e.0: PCI PM: Suspend power state: D3hot


Checking PCI Devices tree diagram:
-[0000:00]-+-00.0  Intel Corporation Raptor Lake-P/U 4p+8e cores Host Bridge/DRAM Controller
           +-02.0  Intel Corporation Raptor Lake-P [Iris Xe Graphics]
           +-04.0  Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant
           +-06.0  Intel Corporation RST VMD Managed Controller
           +-07.0-[01-38]--
           +-08.0  Intel Corporation GNA Scoring Accelerator module
           +-0d.0  Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller
           +-0d.2  Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #0
           +-0e.0  Intel Corporation Volume Management Device NVMe RAID Controller Intel Corporation
           +-12.0  Intel Corporation Alder Lake-P Integrated Sensor Hub
           +-14.0  Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller
           +-14.2  Intel Corporation Alder Lake PCH Shared SRAM
           +-14.3  Intel Corporation Raptor Lake PCH CNVi WiFi
           +-15.0  Intel Corporation Alder Lake PCH Serial IO I2C Controller #0
           +-15.1  Intel Corporation Alder Lake PCH Serial IO I2C Controller #1
           +-16.0  Intel Corporation Alder Lake PCH HECI Controller
           +-1f.0  Intel Corporation Raptor Lake LPC/eSPI Controller
           +-1f.3  Intel Corporation Raptor Lake-P/U/H cAVS
           +-1f.4  Intel Corporation Alder Lake PCH-P SMBus Host Controller
           \-1f.5  Intel Corporation Alder Lake-P PCH SPI Controller
-[10000:e0]---06.0-[e1]----00.0  Samsung Electronics Co Ltd NVMe SSD Controller PM9B1 (DRAM-less)

Pcieport is not in D3cold:     
10000:e0:06.0

fwupdmgr security shows some differences.
On Tumbleweed:

Host Security ID: HSI:1! (v2.0.19)

HSI-1
✔ BIOS Firmware-Aktualisierungen:Enabled
✔ MEI-Schlüsselmanifest:         Valid
✔ csme Herstellungsmodus:        Locked
✔ csme überschreiben:            Locked
✔ csme v0:16.1.27.2176:          Valid
✔ Plattform-Defektlokalisierung: Disabled
✔ SPI schreiben:                 Disabled
✔ SPI sperren:                   Enabled
✔ SPI-BIOS-Deskriptor:           Locked
✔ SPI BIOS-Region:               Locked
✔ Unterstützte CPU:              Valid
✔ TPM leere PCRs:                Valid
✔ TPM v2.0:                      Found
✔ UEFI-Bootdienst-Variablen:     Locked
✔ UEFI-Plattformschlüssel:       Valid

HSI-2
✔ Intel BootGuard ACM-geschützt: Valid
✔ Intel BootGuard:               Enabled
✔ Einmalig programmierbare Intel BootGuard-Sicherung:Valid
✔ Verifizierter Start mit Intel BootGuard:Valid
✔ IOMMU:                         Enabled
✔ Plattform-Defektlokalisierung: Locked
✔ TPM-PCR0-Rekonstruktion:       Valid
✘ BIOS-Rückrollschutz:           Disabled
✘ UEFI-Speicherschutz:           Disabled

HSI-3
✔ CET-Plattform:                 Supported
✔ Intel BootGuard-Fehlerrichtlinie:Valid
✔ DMA-Schutz vor dem Booten:     Enabled
✔ Im Leerlauf anhalten:          Enabled
✔ Im RAM anhalten:               Disabled

HSI-4
✔ SMAP:                          Enabled
✘ Verschlüsselter RAM:           Not supported

Runtime Suffix -!
✔ CET-BS-Unterstützung:          Supported
✔ fwupd-Plugins:                 Untainted
✔ Linux-Kernel:                  Untainted
✘ Linux-Kernel-Sperrung:         Disabled
✘ Linux-Auslagerung:             Unencrypted
✘ UEFI-DB:                       Invalid
✘ Sicherer UEFI-Boot:            Disabled

(Sorry for German, AC_ALL=en_US.UTF-8 helped only on the right hand site)

On Ubuntu:

Host Security ID: HSI:1! (v1.9.24)                                                                                                                                            
                                                                                                                                                                              
HSI-1                                                                                                                                                                         
✔ BIOS firmware updates:         Enabled                                                                                                                                      
✔ MEI key manifest:              Valid                                                                                                                                        
✔ csme manufacturing mode:       Locked                                                                                                                                       
✔ csme override:                 Locked                                                                                                                                       
✔ csme v0:16.1.27.2176:          Valid                                                                                                                                        
✔ Platform debugging:            Disabled                                                                                                                                     
✔ SPI write:                     Disabled                                                                                                                                     
✔ SPI lock:                      Enabled                                                                                                                                      
✔ SPI BIOS region:               Locked                                                                                                                                       
✔ Supported CPU:                 Valid                                                                                                                                        
✔ TPM empty PCRs:                Valid                                                                                                                                        
✔ TPM v2.0:                      Found                                                                                                                                        
✔ UEFI bootservice variables:    Locked                                                                                                                                       
✔ UEFI platform key:             Valid                                                                                                                                        
                                                                                                                                                                              
HSI-2                                                                                                                                                                         
✔ Intel BootGuard ACM protected: Valid                                                                                                                                        
✔ Intel BootGuard:               Enabled                                                                                                                                      
✔ Intel BootGuard OTP fuse:      Valid                                                                                                                                        
✔ Intel BootGuard verified boot: Valid                                                                                                                                        
✔ IOMMU:                         Enabled                                                                                                                                      
✔ Platform debugging:            Locked
✔ TPM PCR0 reconstruction:       Valid
✘ BIOS rollback protection:      Disabled

HSI-3
✔ Intel BootGuard error policy:  Valid
✔ CET Platform:                  Supported
✔ Pre-boot DMA protection:       Enabled
✔ Suspend-to-idle:               Enabled
✔ Suspend-to-ram:                Disabled

HSI-4
✔ SMAP:                          Enabled
✘ Encrypted RAM:                 Not supported

Runtime Suffix -!
✔ fwupd plugins:                 Untainted
✔ CET OS Support:                Supported
✔ Linux swap:                    Encrypted
✔ Linux kernel:                  Untainted
✘ Linux kernel lockdown:         Disabled
✘ UEFI secure boot:              Disabled

Do you see something that gives a hint?

On both my Tumbleweed setups I have;

✘ Suspend-to-idle:               Disabled
✘ Suspend-to-ram:                Enabled

I also use zram, I don’t normally suspend, but they do when the sleep key is pressed…

Let me check the Beelink system I have.

@dojo Alas none of my systems have S0ix… What is the output from cat /sys/power/mem_sleep on both systems?

Ref: https://www.kernel.org/doc/Documentation/power/states.txt

https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate