Bug 1219056

Summary: ASUS Expertbook B5302F - system doesn't sleep properly, no s0 residency in s2idle
Product: [openSUSE] openSUSE Tumbleweed Reporter: Davor Virag <davor.virag>
Component: KernelAssignee: openSUSE Kernel Bugs <kernel-bugs>
Status: NEW --- QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None CC: davor.virag, tiwai
Version: Current   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE Tumbleweed   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Full s0 self-test log
dmesg after running the s0 self-test

Description Davor Virag 2024-01-22 10:19:28 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:121.0) Gecko/20100101 Firefox/121.0
Build Identifier: 

I'm using Intel's S0ixSelftestTool (https://github.com/intel/S0ixSelftestTool/) as I was getting seemingly high battery drain in sleep. According to the logs, it can get the CPU into PC10 state, but the logs state:

"Your system supports S0ix substates, but did not achieve the shallowest s0i2.0"

I have tried "powertop --calibrate" and "powertop --auto-tune", but the s0 self-etst logs still look the same

Reproducible: Always

Steps to Reproduce:
1. Run "s0ix-selftest-tool.sh -s"
2. Check for s0 residency
Actual Results:  
CPU Core C7 residency after S2idle is: 98.34
GFX RC6 residency after S2idle is: 
CPU Package C-state 2 residency after S2idle is: 2.79
CPU Package C-state 3 residency after S2idle is: 2.26
CPU Package C-state 8 residency after S2idle is: 0.21
CPU Package C-state 9 residency after S2idle is: 1.33
CPU Package C-state 10 residency after S2idle is: 88.21
S0ix residency after S2idle is: 0.00

Your system supports S0ix substates, but did not achieve the shallowest s0i2.0
    
Here is the S0ix substates status: 
Substate   Residency      
S0i2.0     0              
S0i3.0     0      

(...)

Did not detect the potential blockers from substate_requirements,     
need to check substate_status_registers file for the advanced debug.

(...)

Your system south port controller power gating state is OK after 30 seconds runtime check.



Expected Results:  
Residency in one of the s0 states
Comment 1 Davor Virag 2024-01-22 10:20:13 UTC 
Created attachment 872056 [details]
Full s0 self-test log
Comment 2 Davor Virag 2024-01-22 10:21:10 UTC 
Created attachment 872057 [details]
dmesg after running the s0 self-test
Comment 3 Davor Virag 2024-02-04 13:49:41 UTC 
Forgot to set the appropriate severity: Now set to major, as this bug impacts a major feature that is, to me, necessary for day-to-day use.
Comment 4 Takashi Iwai 2024-02-04 14:01:11 UTC 
Is it a regression?  If yes, we can try to narrow down the regression range and identify the cause.

Otherwise, it's an upstream problem, and better to report there.
We can help backporting the fix in distro side, of course, so feel fee to put me to Cc.
Comment 5 Davor Virag 2024-02-04 14:46:47 UTC 
(In reply to Takashi Iwai from comment #4)
> Is it a regression?  If yes, we can try to narrow down the regression range
> and identify the cause.
> 
> Otherwise, it's an upstream problem, and better to report there.
> We can help backporting the fix in distro side, of course, so feel fee to
> put me to Cc.

Yeah I'll try to report upstream then as it's not a regression in my case, it's never worked properly for the past ~two years since I've had this laptop. Thank you!
Comment 6 Davor Virag 2024-02-05 16:28:43 UTC 
(In reply to Takashi Iwai from comment #4)
> Is it a regression?  If yes, we can try to narrow down the regression range
> and identify the cause.
> 
> Otherwise, it's an upstream problem, and better to report there.
> We can help backporting the fix in distro side, of course, so feel fee to
> put me to Cc.

I have created a bug report here as the kernel bugzilla was listed in the MAINTAINERS file, but unfortunately I cannot seem to add you to CC:

https://bugzilla.kernel.org/show_bug.cgi?id=218461