Bug ID | 1213830 |
---|---|
Summary | rather current notebook hw (from 2021) has no deep sleep /sys/power/mem_sleep - desktop hw and really old hw does have it |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | Leap 15.5 |
Hardware | x86-64 |
OS | openSUSE Leap 15.5 |
Status | NEW |
Severity | Major |
Priority | P5 - None |
Component | Kernel |
Assignee | kernel-bugs@opensuse.org |
Reporter | abittner@opensuse.org |
QA Contact | qa-bugs@suse.de |
Target Milestone | --- |
Found By | --- |
Blocker | --- |
Hello Opensuse Kernel team, how come that my rather new notebook hardware (hp probook with amd apu, from 2021) does not sleep properly and eats up the battery all the time. barely any difference between when leaving an idle desktop (KDE) sitting around and blanking the screen and when only s2idle sleeping it (lid close, or kde function: sleep) i have tried to make sense of all of this, also reading about the linux folks over at framework-laptop e.g. <https://community.frame.work/t/responded-linux-deep-sleep/2491> all i can find is the value: cat /sys/power/mem_sleep [s2idle] cat /sys/power/state freeze mem disk also added the kernel boot parameter mem_sleep_default=deep command line via yast2 to grub2 or something: ---------- sudo dmesg -e | grep mem_sleep [ +0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.7-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap preempt=full quiet security=apparmor mem_sleep_default=deep mitigations=auto [ +0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.7-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap preempt=full quiet security=apparmor mem_sleep_default=deep mitigations=auto --------------- to sum it up, the system eats away the battery/power at high rates even when sleeping, lid closed etc. how to make this work on leap 15.5 with proper (deep?) memory sleep states and all? is this maybe incompatible with FDE, secureboot? this kernel lockdown stuff? i am not understanding much of this i guess. i am wondering why a really old system and other also older desktop systems just instantly show deep mem_sleep feature activated and working? this system: UEFI ans secureboot system [ +0.109168] smpboot: CPU0: AMD Ryzen 7 5800U with Radeon Graphics (family: 0x19, model: 0x50, stepping: 0x0) full disk encryption on single nvme drive thanks for helping.