Linux Slow wake up from sleep mode [s2idle] on Thinkpad L13 Yoga

Linux Betriebssystem
T

Todeskissen

New member
Themenstarter
Registriert
14 Juni 2025
Beiträge
3
Hello, I am stated using Linux (Fedora 42 with KDE) and noticed a long wake up time (~ 10 seconds) from sleep mode.
What I already tried:
  • Boot from USB
  • Tried with Gnome
  • Used newer Kernel, but stayed on old one because it fixed other issue
There are no programs that are running while waking up from sleep mode.
My specs are:
Memory:
System RAM: total: 32 GiB available: 30.14 GiB used: 6.18 GiB (20.5%)
Array-1: capacity: 64 GiB slots: 2 modules: 2 EC: None
Device-1: Channel-A DIMM 0 type: DDR4 size: 16 GiB speed: 3200 MT/s
Device-2: Channel-B DIMM 0 type: DDR4 size: 16 GiB speed: 3200 MT/s
CPU:
Info: 8-core model: AMD Ryzen 7 PRO 7730U with Radeon Graphics bits: 64
type: MT MCP cache: L2: 4 MiB
Speed (MHz): avg: 1095 min/max: 400/4547 cores: 1: 1095 2: 1095 3: 1095
4: 1095 5: 1095 6: 1095 7: 1095 8: 1095 9: 1095 10: 1095 11: 1095 12: 1095
13: 1095 14: 1095 15: 1095 16: 1095
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Barcelo driver: amdgpu v: kernel
Device-2: Syntek Integrated Camera driver: uvcvideo type: USB
Display: wayland server: Xwayland v: 24.1.6 compositor: kwin_wayland
driver: gpu: amdgpu resolution: 1920x1200~60Hz
API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.7 renderer: AMD
Radeon Graphics (radeonsi renoir ACO DRM 3.61 6.14.9-300.fc42.x86_64)
API: Vulkan v: 1.4.313 drivers: radv,llvmpipe surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
xdpyinfo, xprop, xrandr
Kernel:
6.14.9-300.fc42.x86_64
Would appreciate any help!
 
Willkommen in diesem Forum. Unsere bevorzugte Sprache hier ist deutsch.

Findest Du im Syslog vielleicht fehlermeldungen, die auf ein Problem beim "Resume" hinweisen?
Um welches L13 Yoga handelt es sich genau (Type-Nummer, z.B. 21LU) ?
 
Zuletzt bearbeitet:
Mornsgrans schrieb:
Willkommen in diesem Forum. Unsere bevorzugte Sprache hier ist deutsch.

Findest Du im Syslog vielleicht fehlermeldungen, die auf ein Problem beim "Resume" hinweisen?
Um welches X13 Yoga handelt es sich genau (Type-Nummer, z.B. 21LU) ?
Zum Vergrößern anklicken....
Hallo Mornsgrans,
nein es scheint laut den Logs keine Probleme zu geben:
Jun 15 09:08:25 fedora kernel: amdgpu 0000:07:00.0: amdgpu: SMU is resumed successfully!
Jun 15 09:08:25 fedora kernel: PM: resume devices took 10.002 seconds
Jun 15 09:08:25 fedora kernel: Component: resume devices, time: 10002

Die Typnummer lautet 21FR-001GG.
 
Also L13 Yoga Gen 4 (AMD).

Der Log-Auszug ist etwas kurz geraten. Interessant wären die Einträge darüber, vom Zeitstempel her ab dem "Resume"-Befehl. Direkt davor sollten die Zeilen stehen, in dem der Sleep-Mode eingenommen wurde.

Wie verhält sich der Rechner eigentlich, wenn Du statt S2-Sleep den S3 wählst?

Ab hier muss ich leider das Feld zugunsten der Linux-Experten räumen, die Dir sicher mehr helfen können als ich.
 
Sorry für die kurzen Logs, habe jetzt mal nach Warnings direkt nach dem Einnehmen des Sleep-Modes gesucht:

s2idle
Jun 15 09:05:08 fedora kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
Jun 15 09:05:08 fedora kernel: ACPI: button: Sleep Button [SLPB]
Jun 15 09:05:08 fedora kernel: rtc_cmos 00:01: RTC can wake from S4
Jun 15 09:05:08 fedora dracut-cmdline[419]: Using kernel command line parameters: rd.driver.pre=btrfs BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.14.9-300.fc42.x86_64 root=UUID=cae3eadd-6c28-4d53-8de3-f3dbac22b6f3 r
o rootflags=subvol=root rhgb quiet mem_sleep_default=s2idle
Jun 15 09:05:08 fedora kernel: nvme 0000:01:00.0: platform quirk: setting simple suspend
Jun 15 09:05:15 fedora systemd-logind[1106]: Watching system buttons on /dev/input/event2 (Sleep Button)
Jun 15 09:05:17 fedora containerd[1309]: time="2025-06-15T09:05:17+02:00" level=warning msg="containerd config version `1` has been deprecated and will be converted on each startup in containerd v2.0, use `
containerd config migrate` after upgrading to containerd 2.0 to avoid conversion on startup"
Jun 15 09:05:17 fedora containerd[1309]: time="2025-06-15T09:05:17.047496335+02:00" level=info msg="loading plugin \"io.containerd.warning.v1.deprecations\"..." type=io.containerd.warning.v1
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D PREROUTING -m addrtype --dst-type LOCAL -j DOCKER' failed: iptables v1.8.11 (nf_tables): Chain 'DOCKER' do
es not exist
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D OUTPUT -m addrtype --dst-type LOCAL ! --dst 127.0.0.0/8 -j DOCKER' failed: iptables v1.8.11 (nf_tables): C
hain 'DOCKER' does not exist
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D OUTPUT -m addrtype --dst-type LOCAL -j DOCKER' failed: iptables v1.8.11 (nf_tables): Chain 'DOCKER' does n
ot exist
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D PREROUTING' failed: iptables: Bad rule (does a matching rule exist in that chain?).
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -D OUTPUT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -F DOCKER' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t nat -X DOCKER' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -F DOCKER' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -F DOCKER-FORWARD' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER-FORWARD' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -F DOCKER-BRIDGE' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER-BRIDGE' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -F DOCKER-CT' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER-CT' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -F DOCKER-ISOLATION-STAGE-1' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER-ISOLATION-STAGE-1' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -F DOCKER-ISOLATION-STAGE-2' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER-ISOLATION-STAGE-2' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -F DOCKER-ISOLATION' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w10 -t filter -X DOCKER-ISOLATION' failed: iptables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t nat -D PREROUTING -m addrtype --dst-type LOCAL -j DOCKER' failed: ip6tables v1.8.11 (nf_tables): Chain 'DOCKER'
does not exist
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t nat -D OUTPUT -m addrtype --dst-type LOCAL ! --dst ::1/128 -j DOCKER' failed: ip6tables v1.8.11 (nf_tables): Cha
in 'DOCKER' does not exist
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t nat -D OUTPUT -m addrtype --dst-type LOCAL -j DOCKER' failed: ip6tables v1.8.11 (nf_tables): Chain 'DOCKER' does
not exist
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t nat -D PREROUTING' failed: ip6tables: Bad rule (does a matching rule exist in that chain?).
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t nat -D OUTPUT' failed: ip6tables: Bad rule (does a matching rule exist in that chain?).
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t nat -F DOCKER' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t nat -X DOCKER' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t filter -F DOCKER' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t filter -X DOCKER' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t filter -F DOCKER-FORWARD' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t filter -X DOCKER-FORWARD' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t filter -F DOCKER-BRIDGE' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t filter -X DOCKER-BRIDGE' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t filter -F DOCKER-CT' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t filter -X DOCKER-CT' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t filter -F DOCKER-ISOLATION-STAGE-1' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t filter -X DOCKER-ISOLATION-STAGE-1' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t filter -F DOCKER-ISOLATION-STAGE-2' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:17 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t filter -X DOCKER-ISOLATION-STAGE-2' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:18 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t filter -F DOCKER-ISOLATION' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:18 fedora firewalld[1202]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w10 -t filter -X DOCKER-ISOLATION' failed: ip6tables: No chain/target/match by that name.
Jun 15 09:05:18 fedora dockerd[1358]: time="2025-06-15T09:05:18.766794266+02:00" level=warning msg="Error (Unable to complete atomic operation, key modified) deleting object [endpoint_count 87b4b56ded9b0bbb
0fee470ea86587dbc046aaf8adbdb874d12698d127480d71], retrying...."
Jun 15 09:05:19 fedora dockerd[1358]: time="2025-06-15T09:05:19.109794745+02:00" level=warning msg="CDI setup error /etc/cdi: failed to monitor for changes: no such file or directory"
Jun 15 09:05:19 fedora dockerd[1358]: time="2025-06-15T09:05:19.109812228+02:00" level=warning msg="CDI setup error /var/run/cdi: failed to monitor for changes: no such file or directory"
Jun 15 09:05:41 fedora NetworkManager[1270]: <warn> [1749971141.0970] device (wlp6s0): no secrets: No agents were available for this request.
Jun 15 09:05:41 fedora NetworkManager[1270]: <warn> [1749971141.1587] device (wlp6s0): Activation: failed for connection 'ConnectoPatronum'
Jun 15 09:05:41 fedora imsettings-daemon[1943]: [ 41.828280]: IMSettings-Daemon[1943]: WARNING **: Child process exited with code 1
Jun 15 09:05:43 fedora kwin_wayland_wrapper[2314]: > Warning: Could not resolve keysym XF86RefreshRateToggle
Jun 15 09:05:43 fedora kwin_wayland_wrapper[2314]: > Warning: Could not resolve keysym XF86Accessibility
Jun 15 09:05:43 fedora kwin_wayland_wrapper[2314]: > Warning: Could not resolve keysym XF86DoNotDisturb
Jun 15 09:05:43 fedora kwin_wayland_wrapper[2328]: > Warning: Unsupported maximum keycode 708, clipping.
Jun 15 09:05:43 fedora kwin_wayland_wrapper[2328]: > Warning: Could not resolve keysym XF86RefreshRateToggle
Jun 15 09:05:43 fedora kwin_wayland_wrapper[2328]: > Warning: Could not resolve keysym XF86Accessibility
Jun 15 09:05:43 fedora kwin_wayland_wrapper[2328]: > Warning: Could not resolve keysym XF86DoNotDisturb
Jun 15 09:05:45 fedora imsettings-daemon[1943]: [ 45.907741]: IMSettings-Daemon[1943]: WARNING **: Child process exited with code 1
Jun 15 09:05:45 fedora imsettings-daemon[1943]: [ 45.909544]: IMSettings-Daemon[1943]: WARNING **: Unable to open X Display. Input Method may not work.
Jun 15 09:08:10 fedora.fritz.box systemd-logind[1106]: The system will suspend now!

Hoffe das gibt noch etwas mehr Einsicht.
S3 scheint nicht bereitgestellt zu werden, habe im BIOS keine entsrepchende Option diesbezüglich gefunden.
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
  • ok1.de
  • IT Refresh - IT Teile & mehr
  • thinkstore24.de
  • Preiswerte-IT - Gebrauchte Lenovo Notebooks kaufen

Werbung

Zurück
Oben