Vivobook Pro 15 OLED: issues with sleep on Fedora 41 and 40

Ask Fedora
, ,
1

In short, the issue is that when I close the lid or hit suspend, the screen goes blank for a few seconds and then turns back on with the lock screen. My laptop fails to go into s2idle (s0ix) sleep.

System Details Report

Report details

  • Date generated: 2024-10-16 10:36:15

Hardware Information:

  • Hardware Model: ASUSTeK COMPUTER INC. ASUS Vivobook Pro 15 N6506MU_N6506MU
  • Memory: 24.0 GiB
  • Processor: Intel® Core™ Ultra 9 185H Ă— 22
  • Graphics: Intel® Arc™ Graphics (MTL)
  • Graphics 1: NVIDIA GeForce RTX™ 4050 Laptop GPU
  • Disk Capacity: 1.0 TB

Software Information:

  • Firmware Version: N6506MU.308
  • 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.3-300.fc41.x86_64

This is what ./s0ix-selftest-tool.sh -s gives me:

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

The system OS Kernel version is:
Linux fedora 6.11.3-300.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Oct 10 19:18:36 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

Turbostat output: 
5.075730 sec
CPU%c1	CPU%c6	CPU%c7	Pkg%pc2	Pkg%pc3	Pkg%pc6	Pkg%pc8	Pk%pc10	SYS%LPI
10.82	57.58	26.43	21.81	0.00	0.00	0.00	0.00	0.00
6.20	91.63	0.00
5.41	92.45	0.00
5.47	92.47	0.00
4.67	93.26	0.00
5.19	92.68	0.00
3.68	93.68	0.00
4.74	92.82	0.00
5.78	91.48	0.00
11.45	0.51	47.09
11.45
7.62	0.39	77.69
7.62
46.86	1.29	40.54	21.81	0.00	0.00	0.00	0.00	0.00
46.85
7.25	0.00	88.96
7.25
10.65	0.05	80.41
10.65
6.87	0.01	88.21
6.87
8.28	89.64	0.00
7.29	88.87	0.00

CPU Core C7 residency after S2idle is: 26.43
CPU Package C-state 2 residency after S2idle is: 21.81
CPU Package C-state 3 residency after S2idle is: 0.00
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 PC2 residency: 21.81, 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: 

3.041700 sec
CPU%c1	CPU%c6	CPU%c7	Pkg%pc2	Pkg%pc3	Pkg%pc6	Pkg%pc8	Pk%pc10	SYS%LPI
11.26	56.76	27.69	35.53	0.00	0.00	0.00	0.00	0.00
6.17	91.50	0.00
8.05	89.62	0.00
5.88	91.93	0.00
5.10	92.66	0.00
4.79	93.05	0.00
5.79	92.07	0.00
5.13	92.38	0.00
5.67	92.17	0.00
10.69	0.12	68.69
10.69
10.45	0.63	65.71
10.45
39.36	1.02	54.95	35.53	0.00	0.00	0.00	0.00	0.00
39.35
9.32	0.72	79.09
9.32
9.63	0.14	87.46
9.63
10.37	0.02	87.22
10.37
13.93	82.71	0.00
7.61	87.36	0.00

Your CPU Core C7 residency is available: 27.69

Checking PCIe Device D state and Bridge Link state:

Available bridge device: 0000:00:01.0 0000:00:07.0 0000:00:1c.0 0000:00:1c.6 10000:e0:06.2
./s0ix-selftest-tool.sh: line 854: xxd: command not found
./s0ix-selftest-tool.sh: line 785: 16#: invalid integer constant (error token is "16#")
./s0ix-selftest-tool.sh: line 785: 16#: invalid integer constant (error token is "16#")
./s0ix-selftest-tool.sh: line 785: 16#: invalid integer constant (error token is "16#")
./s0ix-selftest-tool.sh: line 785: 16#: invalid integer constant (error token is "16#")
./s0ix-selftest-tool.sh: line 785: 16#: invalid integer constant (error token is "16#")
./s0ix-selftest-tool.sh: line 785: 16#: invalid integer constant (error token is "16#")
./s0ix-selftest-tool.sh: line 785: 16#: invalid integer constant (error token is "16#")

The PCIe bridge link power management state is:
./s0ix-selftest-tool.sh: line 785: 16#: invalid integer constant (error token is "16#")
0000:00:01.0 

The link power management state of PCIe bridge: 0000:00:01.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 0000:00:01.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 0000:00:01.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 Device 7d01
           +-01.0-[01]--+-00.0  NVIDIA Corporation AD107M [GeForce RTX 4050 Max-Q / Mobile]
           |            \-00.1  NVIDIA Corporation AD107 High Definition Audio Controller
           +-02.0  Intel Corporation Meteor Lake-P [Intel Arc Graphics]
           +-04.0  Intel Corporation Meteor Lake-P Dynamic Tuning Technology
           +-07.0-[02-2b]--
           +-08.0  Intel Corporation Meteor Lake-P Gaussian & Neural-Network Accelerator
           +-0a.0  Intel Corporation Meteor Lake-P Platform Monitoring Technology
           +-0b.0  Intel Corporation Meteor Lake NPU
           +-0d.0  Intel Corporation Meteor Lake-P Thunderbolt 4 USB Controller
           +-0d.2  Intel Corporation Meteor Lake-P Thunderbolt 4 NHI #0
           +-0e.0  Intel Corporation Volume Management Device NVMe RAID Controller Intel Corporation
           +-12.0  Intel Corporation Meteor Lake-P Integrated Sensor Hub
           +-14.0  Intel Corporation Meteor Lake-P USB 3.2 Gen 2x1 xHCI Host Controller
           +-14.2  Intel Corporation Device 7e7f
           +-14.3  Intel Corporation Meteor Lake PCH CNVi WiFi
           +-15.0  Intel Corporation Meteor Lake-P Serial IO I2C Controller #0
           +-15.1  Intel Corporation Meteor Lake-P Serial IO I2C Controller #1
           +-16.0  Intel Corporation Meteor Lake-P CSME HECI #1
           +-19.0  Intel Corporation Meteor Lake-P Serial IO I2C Controller #4
           +-1c.0-[2c]----00.0  Genesys Logic, Inc GL9755 SD Host Controller
           +-1c.6-[2d]----00.0  Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller
           +-1f.0  Intel Corporation Device 7e02
           +-1f.3  Intel Corporation Meteor Lake-P HD Audio Controller
           +-1f.4  Intel Corporation Meteor Lake-P SMBus Controller
           \-1f.5  Intel Corporation Meteor Lake-P SPI Controller
-[10000:e0]-+-06.0  Intel Corporation RST VMD Managed Controller
            \-06.2-[e1]----00.0  Sandisk Corp WD Black SN770 / PC SN740 256GB / PC SN560 (DRAM-less) NVMe SSD

./s0ix-selftest-tool.sh: line 140: /sys/kernel/debug/dynamic_debug/control: Operation not permitted

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

At first I thought it was the issue found here and here, but disabling wake-on-LAN does not fix mine.
Also I have Nvidia proprietary drivers installed.

2

Added gnome, nvidia, suspend-resume

3

Have you tried forcing S3 sleep instead of s0ix?
Adding the kernel parameter mem_sleep_default=deep should work.
To add kernel parameters, you should add them to /etc/default/grub and then run grub-mkconfig

4

Same issue with my Vivobook 16x, i upgarded from Fedora 40 to 41 and the sleep/suspend does not work anymore, its fine in Fedora 40 but not in 41.

5

Do you also have Nvidia graphics? That could be the cause.

6

yes, did you solve the issue? due to this issue the battery drain is also so much.
also running ./s0ix-selftest-tool.sh -s gives

x@fedora:~$ ./s0ix-selftest-tool.sh -s
bash: ./s0ix-selftest-tool.sh: No such file or directory

am i suppose to run it in a specific directory?

and
$ cat /sys/power/mem_sleep gives me

x@fedora:~$ cat /sys/power/mem_sleep
[s2idle] deep
7

No, the issue is still present. s0ix-selftest-tool.sh is a script, to use it download this code and then execute the script in that directory. You can then copy its output.
As for the second output, it just means that s0ix sleep (i.e. Modern Standby) is available on your device. It would also be help have some of your system’s specifications.

8

there are some other threads around this board, where people saying disabling Bluetooth may help

9

Not for me, even disabling Bluetooth completely in the BIOS does not help.

10

Hello there,

I have the same laptop with the exact same problem with Fedora 40.

But I have identified the source of the issue (sort of) and have a temporary fix.
I just don’t know where I need to report this problem to be really fixed once and for all.

There seems to be an issue with the configuration of this PCI device:

0000:00:01.0 PCI bridge: Intel Corporation Device 7ecc (rev 10)

because when you look at this file /proc/acpi/wakeup with cat, you get this line:

RP12	  S4	*enabled   pci:0000:00:01.0

But I don’t know what this PCI device does, nor why the acpi wakeup is enabled by default.

To fix this issue, simply log in root with sudo -i and type this:

echo "RP12" > /proc/acpi/wakeup

And your laptop will go to sleep without waking up by itself just after it.
The only issue with this method, is that the new setting won’t be saved after your next reboot.

I hope it can help you and that someone can guide us to where we need to report this problem.

Have a nice day,
Clement.

BTW @dawgsome7, if you have the time, could please give a look at this issue and tell me if you have the same problem? That would help me a lot!

11

Hello,

Thank you so much, my laptop can finally go to sleep! I will try automating this command on every start-up. I will look at that issue, I probably also have it.

Have a nice weekend

1 Like
12

You are welcome!
Glad to help.