Laptop (probably) heats up while suspended

Cvlc · 2024-12-14 11:39:55

Hi,

This is a follow up to a long standing issue

The symptoms are that the laptop fails to resume from suspend (to ram), only if it as been suspended ~ 30 mins or more.

hibernating is set up and works reliably enough
suspend to ram works
resuming from ram works...
- Ok if waking up after 0 - 10 mins
- Ok but the fans run at full power for a while if waking up after ~15+ mins
- Nothing happens when trying to wake after ~30+ mins, and the laptop goes through a full normal start up when pressing the power button

Because of the fans running at full power after some time suspended, my guess (?) is that maybe some internals heat up when suspended, and that some security kicks in at some point and shuts all power off. Is this possible ?

This is really hard to diagnose as all journalctl logs seem normal and show the laptop going into normal suspend. Then the journal stops and show data from the following normal startup...

Is there anything I've failed to look at to try to fix this ?

Thanks !

jl2 · 2024-12-14 12:30:10

what type of suspend are you using? does any of the other modes work?

cat /sys/power/mem_sleep

https://wiki.archlinux.org/title/Power_ … end_method

Last edited by jl2 (2024-12-14 12:30:32)

Cvlc · 2024-12-15 10:31:13

Hi, thanks taking the time

# cat /sys/power/mem_sleep
[s2idle] deep

However when set to deep, the laptop does not wake from suspend, there's a black screen and a couple leds and the fans run. Really hard to shut down thereafter (~ 15 s press on power button) and the system didn't even boot on the next try. Second 15s press to shut it down and now it booted again...

Last edited by Cvlc (2024-12-15 10:31:59)

seth · 2024-12-15 12:53:45

Please clarify whether the OP symptoms exists w/ s2idle or you're using s2idle because S3 causes the OP symptoms (but s2idle is fine)
Also record the model and see whether you can preserve a journal covering a system sleep, in doubt using the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) + REISUB

Cvlc · 2024-12-15 16:38:43

s2idle: symptoms from first post, with different behavior according to how long the laptop has been suspended
deep: behavior from post above yours, no waking at all and hung state

model is an MSI modern 15. Here is a log from suspend to s2idle, I think it's the same when I leave it suspended a long time. However then the journal resumes from the device boot up.

17:31:55 systemd-logind[574]: The system will suspend now!
17:31:55 NetworkManager[642]: <info>  [1734280315.8487] manager: sleep: sleep requested (sleeping: no  enabled: yes)
17:31:55 NetworkManager[642]: <info>  [1734280315.8488] device (p2p-dev-wlo1): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
17:31:55 NetworkManager[642]: <info>  [1734280315.8491] manager: NetworkManager state is now ASLEEP
17:31:55 NetworkManager[642]: <info>  [1734280315.8492] device (wlo1): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
17:31:55 systemd[1]: Starting Network Manager Script Dispatcher Service...
17:31:55 systemd[1]: Started Network Manager Script Dispatcher Service.
17:31:55 systemd-networkd[643]: wlo1: Lost carrier
17:31:55 systemd-timesyncd[528]: No network connectivity, watching for changes.
17:31:55 kernel: wlo1: deauthenticating from 30:24:78:33:3d:b4 by local choice (Reason: 3=DEAUTH_LEAVING)
17:31:56 wpa_supplicant[658]: nl80211: send_event_marker failed: Source based routing not supported
17:31:56 wpa_supplicant[658]: wlo1: CTRL-EVENT-DISCONNECTED bssid=30:24:78:33:3d:b4 reason=3 locally_generated=1
17:31:56 wpa_supplicant[658]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all
17:31:56 NetworkManager[642]: <info>  [1734280316.0182] device (wlo1): supplicant interface state: completed -> disconnected
17:31:56 NetworkManager[642]: <info>  [1734280316.0184] device (wlo1): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
17:31:56 NetworkManager[642]: <info>  [1734280316.0186] dhcp4 (wlo1): canceled DHCP transaction
17:31:56 NetworkManager[642]: <info>  [1734280316.0186] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
17:31:56 NetworkManager[642]: <info>  [1734280316.0186] dhcp4 (wlo1): state changed no lease
17:31:56 systemd-networkd[643]: wlo1: Link DOWN
17:31:56 NetworkManager[642]: <info>  [1734280316.0355] device (wlo1): set-hw-addr: set MAC address to D2:E7:15:A9:6F:F2 (scanning)
17:31:56 systemd-networkd[643]: wlo1: Link UP
17:31:56 systemd-resolved[527]: wlo1: Bus client reset search domain list.
17:31:56 systemd-resolved[527]: wlo1: Bus client set default route setting: no
17:31:56 systemd-resolved[527]: wlo1: Bus client reset DNS server list.
17:31:56 NetworkManager[642]: <info>  [1734280316.0879] device (wlo1): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
17:31:56 kgx[2788]: ../gtk/gdk/wayland/gdkcursor-wayland.c:210 cursor image size (32) not an integer multiple of theme size (24)
17:31:56 kgx[2788]: ../gtk/gdk/wayland/gdkcursor-wayland.c:210 cursor image size (32) not an integer multiple of theme size (24)
17:31:56 systemd-networkd[643]: wlo1: Link DOWN
17:31:56 NetworkManager[642]: <info>  [1734280316.2349] device (wlo1): set-hw-addr: reset MAC address to A4:6B:B6:08:41:C0 (unmanage)
17:31:56 geoclue[1049]: WiFi scan failed
17:31:56 systemd-networkd[643]: wlo1: Link UP
17:31:56 wpa_supplicant[658]: p2p-dev-wlo1: CTRL-EVENT-DSCP-POLICY clear_all
17:31:56 wpa_supplicant[658]: p2p-dev-wlo1: CTRL-EVENT-DSCP-POLICY clear_all
17:31:56 wpa_supplicant[658]: nl80211: deinit ifname=p2p-dev-wlo1 disabled_11b_rates=0
17:31:56 wpa_supplicant[658]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all
17:31:56 wpa_supplicant[658]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all
17:31:56 wpa_supplicant[658]: nl80211: deinit ifname=wlo1 disabled_11b_rates=0
17:31:56 gnome-shell[1400]: Failed to get met.no forecast data: Erreur de résolution de « aa037rv1tsaszxi6o.api.met.no » : Nom ou service inconnu
17:31:56 gnome-shell[1400]: Cursor update failed: drmModeAtomicCommit: Argument invalide
17:31:57 systemd-resolved[527]: Switching to fallback DNS server 1.1.1.1#cloudflare-dns.com.
17:31:57 systemd[1]: Reached target Sleep.
17:31:57 systemd[1]: Starting System Suspend...
17:31:57 systemd[1]: user.slice: Unit now frozen.
17:31:57 systemd[1]: user-60303.slice: Unit now frozen-by-parent.
17:31:57 systemd-sleep[2934]: Successfully froze unit 'user.slice'.
17:31:57 systemd[1]: user@60303.service: Unit now frozen-by-parent.
17:31:57 systemd[1]: session-3.scope: Unit now frozen-by-parent.
17:31:57 systemd-sleep[2934]: Performing sleep operation 'suspend'...
17:31:57 kernel: PM: suspend entry (s2idle)
17:31:57 kernel: Filesystems sync: 0.021 seconds
17:31:59 kernel: Freezing user space processes
17:31:59 kernel: Freezing user space processes completed (elapsed 0.001 seconds)
17:31:59 kernel: OOM killer disabled.
17:31:59 kernel: Freezing remaining freezable tasks
17:31:59 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
17:31:59 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
17:31:59 kernel: ACPI: EC: interrupt blocked
17:31:59 kernel: ACPI: EC: interrupt unblocked
17:31:59 kernel: nvme nvme0: D3 entry latency set to 10 seconds
17:31:59 kernel: nvme nvme0: 8/0/0 default/read/poll queues
17:31:59 kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [xe])
17:31:59 kernel: OOM killer enabled.
17:31:59 kernel: Restarting tasks ... done.
17:31:59 kernel: random: crng reseeded on system resumption
17:31:59 systemd-resolved[527]: Clock change detected. Flushing caches.
17:31:59 systemd-sleep[2934]: System returned from sleep operation 'suspend'.
17:31:59 bluetoothd[567]: Controller resume with wake event 0x0
17:31:59 systemd[1]: user.slice: Unit now thawed.
17:31:59 systemd[1]: user-60303.slice: Unit now thawed.
17:31:59 systemd-sleep[2934]: Successfully thawed unit 'user.slice'.
17:31:59 kernel: PM: suspend exit
17:31:59 systemd[1]: session-3.scope: Unit now thawed.
17:31:59 systemd[1]: user@60303.service: Unit now thawed.
17:31:59 systemd[1]: systemd-suspend.service: Deactivated successfully.
17:31:59 systemd[1]: Finished System Suspend.
17:31:59 systemd[1]: Stopped target Sleep.
17:31:59 systemd[1]: Reached target Suspend.
17:31:59 systemd-logind[574]: Operation 'suspend' finished.
17:31:59 systemd-resolved[527]: Closing all remaining TCP connections.
17:31:59 systemd[1]: Stopped target Suspend.

seth · 2024-12-15 22:01:05

I think it's the same when I leave it suspended a long time. However then the journal resumes from the device boot up.

But that's after you rebooted w/ the power button, right?

resuming from ram works...
Ok but the fans run at full power for a while if waking up after ~15+ mins

Sounds interesting, do you have the journal of a boot covering that?
You should also use sensors and powertop to figure what's hot and drawing energy in that case.

Cvlc · 2024-12-16 16:11:50

seth wrote:

I think it's the same when I leave it suspended a long time. However then the journal resumes from the device boot up.
But that's after you rebooted w/ the power button, right?

Yes. When suspended for a long time, the laptop doesn't respond to any keyboard or touchpad presses, but a single press of the power button starts a regular boot.

resuming from ram works...
Ok but the fans run at full power for a while if waking up after ~15+ mins
Sounds interesting, do you have the journal of a boot covering that?

I'll get one, but it's tricky since if I leave it suspended too long, then the laptop is effectively shut down when I try to resume. Here's a log when this happens (i.e. suspended for > 30 mins), regular suspend, then the system boots as new, no errors anywhere, as if nothing happened :

13:36:53 systemd[1]: Reached target Sleep.
13:36:53 systemd[1]: Starting System Suspend...
13:36:53 systemd[1]: user-120.slice: Unit now frozen-by-parent.
13:36:53 systemd[1]: user@120.service: Unit now frozen-by-parent.
13:36:53 systemd[1]: session-3.scope: Unit now frozen-by-parent.
13:36:53 systemd[1]: user@60303.service: Unit now frozen-by-parent.
13:36:53 systemd[1]: user-60303.slice: Unit now frozen-by-parent.
13:36:53 systemd[1]: user.slice: Unit now frozen.
13:36:53 systemd-sleep[2011]: Successfully froze unit 'user.slice'.
13:36:53 systemd-sleep[2011]: Performing sleep operation 'suspend'...
13:36:53 kernel: PM: suspend entry (s2idle)
-- Boot ec0686f1062a451e83134aa5e8c0f7ba --
16:57:57 archlinux kernel: Linux version 6.12.4-arch1-1 (linux@archlinux) (gcc (GCC) 14.2.1 20240910, GNU ld (GNU Binutils) 2.43.0) #1 SMP PREEMPT_DYNAMIC Mon, 09 Dec 2024 14:31:57 >
16:57:57 archlinux kernel: Command line: rootflags=compress-force=zstd,autodefrag quiet bgrt_disable nowatchdog systemd.machine_id=9a957deed6504f4a8af1d08fb2170e04 zswap.enabled=1 i>
16:57:57 archlinux kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
16:57:57 archlinux kernel: BIOS-provided physical RAM map:
16:57:57 archlinux kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
16:57:57 archlinux kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
16:57:57 archlinux kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000061a66fff] usable
16:57:57 archlinux kernel: BIOS-e820: [mem 0x0000000061a67000-0x0000000064b66fff] reserved
16:57:57 archlinux kernel: BIOS-e820: [mem 0x0000000064b67000-0x0000000064c32fff] ACPI data
16:57:57 archlinux kernel: BIOS-e820: [mem 0x0000000064c33000-0x0000000064ce8fff] ACPI NVS
16:57:57 archlinux kernel: BIOS-e820: [mem 0x0000000064ce9000-0x0000000067efefff] reserved
16:57:57 archlinux kernel: BIOS-e820: [mem 0x0000000067eff000-0x0000000067efffff] usable
16:57:57 archlinux kernel: BIOS-e820: [mem 0x0000000067f00000-0x000000006dffffff] reserved
16:57:57 archlinux kernel: BIOS-e820: [mem 0x000000006e800000-0x000000006e9fffff] reserved
16:57:57 archlinux kernel: BIOS-e820: [mem 0x000000006f000000-0x00000000743fffff] reserved
16:57:57 archlinux kernel: BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
16:57:57 archlinux kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
16:57:57 archlinux kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
16:57:57 archlinux kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
16:57:57 archlinux kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
16:57:57 archlinux kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
16:57:57 archlinux kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
16:57:57 archlinux kernel: BIOS-e820: [mem 0x0000000100000000-0x000000048bbfffff] usable
16:57:57 archlinux kernel: NX (Execute Disable) protection: active
16:57:57 archlinux kernel: APIC: Static calls initialized
16:57:57 archlinux kernel: efi: EFI v2.7 by American Megatrends
16:57:57 archlinux kernel: efi: ACPI=0x64c32000 ACPI 2.0=0x64c32014 TPMFinalLog=0x64c76000 SMBIOS=0x67ca4000 SMBIOS 3.0=0x67ca3000 MEMATTR=0x5be10018 ESRT=0x5fa00a98 RNG=0x64b9ff18 >
16:57:57 archlinux kernel: random: crng init done
16:57:57 archlinux kernel: efi: Remove mem71: MMIO range=[0xc0000000-0xcfffffff] (256MB) from e820 map
16:57:57 archlinux kernel: e820: remove [mem 0xc0000000-0xcfffffff] reserved
16:57:57 archlinux kernel: efi: Not removing mem72: MMIO range=[0xfe000000-0xfe010fff] (68KB) from e820 map
16:57:57 archlinux kernel: efi: Not removing mem73: MMIO range=[0xfec00000-0xfec00fff] (4KB) from e820 map
16:57:57 archlinux kernel: efi: Not removing mem74: MMIO range=[0xfed00000-0xfed00fff] (4KB) from e820 map
16:57:57 archlinux kernel: efi: Not removing mem76: MMIO range=[0xfee00000-0xfee00fff] (4KB) from e820 map
16:57:57 archlinux kernel: efi: Remove mem77: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
16:57:57 archlinux kernel: e820: remove [mem 0xff000000-0xffffffff] reserved
16:57:57 archlinux kernel: SMBIOS 3.3.0 present.
16:57:57 archlinux kernel: DMI: Micro-Star International Co., Ltd. Modern 15 A11M/MS-1552, BIOS E1552IMS.121 04/13/2022
16:57:57 archlinux kernel: DMI: Memory slots populated: 2/2
16:57:57 archlinux kernel: tsc: Detected 2800.000 MHz processor
16:57:57 archlinux kernel: tsc: Detected 2803.200 MHz TSC
16:57:57 archlinux kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
16:57:57 archlinux kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
16:57:57 archlinux kernel: last_pfn = 0x48bc00 max_arch_pfn = 0x400000000
16:57:57 archlinux kernel: MTRR map: 5 entries (3 fixed + 2 variable; max 23), built from 10 variable MTRRs
16:57:57 archlinux kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
16:57:57 archlinux kernel: last_pfn = 0x67f00 max_arch_pfn = 0x400000000
16:57:57 archlinux kernel: esrt: Reserving ESRT space from 0x000000005fa00a98 to 0x000000005fa00b20.
16:57:57 archlinux kernel: e820: update [mem 0x5fa00000-0x5fa00fff] usable ==> reserved
16:57:57 archlinux kernel: Using GB pages for direct mapping
16:57:57 archlinux kernel: Secure boot enabled
16:57:57 archlinux kernel: RAMDISK: [mem 0x5762b000-0x58e2efff]

I'll get a log for when the fans run high

seth · 2024-12-16 16:25:59

You can access older logs, if you've encountered this somewhat recently.

For five boots ago:

sudo journalctl -b -5

Cvlc · 2024-12-19 11:56:28

Here is a log where the fans run at full speed when resuming, after 20 mins suspended. A previous try with 15 mins suspended didn't trigger the fans. The temperatures look normal, and so does the log

12:23:57 systemd-resolved[535]: Switching to fallback DNS server 1.1.1.1#cloudflare-dns.com.
12:23:57 systemd[1]: Reached target Sleep.
12:23:57 systemd[1]: Starting System Suspend...
12:23:57 systemd[1]: user.slice: Unit now frozen.
12:23:57 systemd[1]: user-60303.slice: Unit now frozen-by-parent.
12:23:57 systemd-sleep[2499]: Successfully froze unit 'user.slice'.
12:23:57 systemd[1]: user@60303.service: Unit now frozen-by-parent.
12:23:57 kernel: PM: suspend entry (s2idle)
12:23:57 systemd[1]: session-3.scope: Unit now frozen-by-parent.
12:23:57 systemd-sleep[2499]: Performing sleep operation 'suspend'...
12:23:57 kernel: Filesystems sync: 0.021 seconds
12:45:10 kernel: Freezing user space processes
12:45:10 kernel: Freezing user space processes completed (elapsed 0.001 seconds)
12:45:10 kernel: OOM killer disabled.
12:45:10 kernel: Freezing remaining freezable tasks
12:45:10 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
12:45:10 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
12:45:10 kernel: ACPI: EC: interrupt blocked
12:45:10 kernel: ACPI: EC: interrupt unblocked
12:45:10 kernel: nvme nvme0: D3 entry latency set to 10 seconds
12:45:10 kernel: nvme nvme0: 8/0/0 default/read/poll queues
12:45:10 kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [xe])
12:45:10 kernel: OOM killer enabled.
12:45:10 kernel: Restarting tasks ... done.
12:45:10 kernel: random: crng reseeded on system resumption
12:45:10 systemd-resolved[535]: Clock change detected. Flushing caches.
12:45:10 systemd-sleep[2499]: System returned from sleep operation 'suspend'.
12:45:10 gnome-shell[1404]: libinput error: event2  - Power Button: client bug: event processing lagging behind by 234ms, your system is too slow
12:45:10 kernel: PM: suspend exit
12:45:10 systemd[1]: user.slice: Unit now thawed.
12:45:10 systemd[1]: user-60303.slice: Unit now thawed.
12:45:10 systemd[1]: user@60303.service: Unit now thawed.
12:45:10 systemd[1]: session-3.scope: Unit now thawed.
12:45:10 systemd-sleep[2499]: Successfully thawed unit 'user.slice'.
12:45:10 systemd[1]: systemd-suspend.service: Deactivated successfully.
12:45:10 systemd[1]: Finished System Suspend.
12:45:10 systemd[1]: Stopped target Sleep.
12:45:10 systemd[1]: Reached target Suspend.
12:45:10 systemd-logind[568]: Operation 'suspend' finished.
12:45:10 systemd[1]: Stopped target Suspend.
12:45:10 systemd-resolved[535]: Closing all remaining TCP connections.
12:45:10 systemd-resolved[535]: Resetting learnt feature levels on all servers.
12:45:10 NetworkManager[559]: <info>  [1734608710.6096] manager: sleep: wake requested (sleeping: yes  enabled: yes)
12:45:10 NetworkManager[559]: <info>  [1734608710.6098] device (wlo1): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
12:45:10 systemd-networkd[402]: wlo1: Link DOWN
12:45:10 NetworkManager[559]: <info>  [1734608710.6759] device (wlo1): set-hw-addr: set MAC address to 26:D4:6D:10:1A:71 (scanning)
12:45:10 systemd-networkd[402]: wlo1: Link UP
12:45:10 NetworkManager[559]: <info>  [1734608710.8740] device (p2p-dev-wlo1): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
12:45:10 NetworkManager[559]: <info>  [1734608710.8745] manager: NetworkManager state is now DISCONNECTED
12:45:10 NetworkManager[559]: <info>  [1734608710.9156] device (wlo1): supplicant interface state: internal-starting -> disconnected
12:45:10 NetworkManager[559]: <info>  [1734608710.9157] device (p2p-dev-wlo1): state change: unavailable -> unmanaged (reason 'unmanaged-link-not-init', managed-type: 'removed')
12:45:10 NetworkManager[559]: <info>  [1734608710.9164] Wi-Fi P2P device controlled by interface wlo1 created
12:45:10 NetworkManager[559]: <info>  [1734608710.9169] manager: (p2p-dev-wlo1): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/7)
12:45:10 NetworkManager[559]: <info>  [1734608710.9173] device (p2p-dev-wlo1): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
12:45:10 NetworkManager[559]: <info>  [1734608710.9181] device (wlo1): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
12:45:10 NetworkManager[559]: <info>  [1734608710.9191] device (p2p-dev-wlo1): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
12:45:11 systemd-homed[562]: name: changing state active → authenticating-for-acquire
12:45:11 systemd-homework[2531]: None of the supplied plaintext passwords unlock the user record's hashed passwords.
12:45:11 systemd-homed[562]: Authentication failed: Security token requires presence confirmation.
12:45:11 systemd-homed[562]: name: changing state authenticating-for-acquire → active
12:45:11 systemd-homed[562]: name: changing state active → authenticating-for-acquire
12:45:11 systemd-homework[2532]: None of the supplied plaintext passwords unlock the user record's hashed passwords.
12:45:11 systemd-homed[562]: Authentication failed: Password for home name is incorrect or not sufficient, and configured security token not found either.
12:45:11 systemd-homed[562]: name: changing state authenticating-for-acquire → active
12:45:14 wpa_supplicant[1069]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=FR
12:45:14 wpa_supplicant[1069]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=FR
12:45:14 NetworkManager[559]: <info>  [1734608714.6488] policy: auto-activating connection '73CF10F' (8deecf3d-7290-4895-8017-ada09fc8ad53)
12:45:14 NetworkManager[559]: <info>  [1734608714.6490] device (wlo1): Activation: starting connection '73CF10F' (8deecf3d-7290-4895-8017-ada09fc8ad53)
12:45:14 NetworkManager[559]: <info>  [1734608714.6491] device (wlo1): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
12:45:14 NetworkManager[559]: <info>  [1734608714.6492] manager: NetworkManager state is now CONNECTING
12:45:14 systemd-networkd[402]: wlo1: Link DOWN
12:45:14 NetworkManager[559]: <info>  [1734608714.6787] device (wlo1): set-hw-addr: reset MAC address to A4:6B:B6:08:41:C0 (preserve)
12:45:14 systemd-networkd[402]: wlo1: Link UP
12:45:14 NetworkManager[559]: <info>  [1734608714.6830] device (wlo1): state change: prepare -> config (reason 'none', managed-type: 'full')
12:45:14 NetworkManager[559]: <info>  [1734608714.6831] device (wlo1): Activation: (wifi) access point '73CF10F' has security, but secrets are required.
12:45:14 NetworkManager[559]: <info>  [1734608714.6831] device (wlo1): state change: config -> need-auth (reason 'none', managed-type: 'full')
12:45:14 NetworkManager[559]: <info>  [1734608714.6832] sup-iface[eb68005461edd7bf,1,wlo1]: wps: type pbc start...
12:45:14 NetworkManager[559]: <info>  [1734608714.6837] device (wlo1): supplicant interface state: disconnected -> inactive
12:45:14 NetworkManager[559]: <info>  [1734608714.6837] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> inactive
12:45:14 NetworkManager[559]: <info>  [1734608714.6838] device (wlo1): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
12:45:14 wpa_supplicant[1069]: wlo1: WPS-PBC-ACTIVE
12:45:14 NetworkManager[559]: <info>  [1734608714.6839] device (wlo1): state change: prepare -> config (reason 'none', managed-type: 'full')
12:45:14 NetworkManager[559]: <info>  [1734608714.6841] device (wlo1): Activation: (wifi) connection '73CF10F' has security, and secrets exist.  No new secrets needed.
12:45:14 NetworkManager[559]: <info>  [1734608714.6841] Config: added 'ssid' value '73CF10F'
12:45:14 NetworkManager[559]: <info>  [1734608714.6841] Config: added 'scan_ssid' value '1'
12:45:14 NetworkManager[559]: <info>  [1734608714.6841] Config: added 'bgscan' value 'simple:30:-65:300'
12:45:14 NetworkManager[559]: <info>  [1734608714.6841] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
12:45:14 NetworkManager[559]: <info>  [1734608714.6841] Config: added 'auth_alg' value 'OPEN'
12:45:14 NetworkManager[559]: <info>  [1734608714.6841] Config: added 'psk' value '<hidden>'
12:45:14 wpa_supplicant[1069]: wlo1: WPS-CANCEL
12:45:14 NetworkManager[559]: <info>  [1734608714.6859] device (wlo1): supplicant interface state: inactive -> scanning
12:45:14 NetworkManager[559]: <info>  [1734608714.6859] device (p2p-dev-wlo1): supplicant management interface state: inactive -> scanning
12:45:14 wpa_supplicant[1069]: wlo1: SME: Trying to authenticate with f0:4d:d4:2e:fd:04 (SSID='73CF10F' freq=5500 MHz)
12:45:14 kernel: wlo1: authenticate with f0:4d:d4:2e:fd:04 (local address=a4:6b:b6:08:41:c0)
12:45:14 kernel: wlo1: send auth to f0:4d:d4:2e:fd:04 (try 1/3)
12:45:14 NetworkManager[559]: <info>  [1734608714.7256] device (wlo1): supplicant interface state: scanning -> authenticating
12:45:14 NetworkManager[559]: <info>  [1734608714.7257] device (p2p-dev-wlo1): supplicant management interface state: scanning -> authenticating
12:45:14 wpa_supplicant[1069]: wlo1: Trying to associate with f0:4d:d4:2e:fd:04 (SSID='73CF10F' freq=5500 MHz)
12:45:14 kernel: wlo1: authenticated
12:45:14 kernel: wlo1: associate with f0:4d:d4:2e:fd:04 (try 1/3)
12:45:14 NetworkManager[559]: <info>  [1734608714.7556] device (wlo1): supplicant interface state: authenticating -> associating
12:45:14 NetworkManager[559]: <info>  [1734608714.7556] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating
12:45:14 kernel: wlo1: RX AssocResp from f0:4d:d4:2e:fd:04 (capab=0x511 status=0 aid=94)
12:45:14 systemd-networkd[402]: wlo1: Connected WiFi access point: 73CF10F (f0:4d:d4:2e:fd:04)
12:45:14 wpa_supplicant[1069]: wlo1: Associated with f0:4d:d4:2e:fd:04
12:45:14 wpa_supplicant[1069]: wlo1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
12:45:14 kernel: wlo1: associated
12:45:14 NetworkManager[559]: <info>  [1734608714.8137] device (wlo1): supplicant interface state: associating -> associated
12:45:14 NetworkManager[559]: <info>  [1734608714.8137] device (p2p-dev-wlo1): supplicant management interface state: associating -> associated
12:45:14 kernel: wlo1: Limiting TX power to 30 (30 - 0) dBm as advertised by f0:4d:d4:2e:fd:04
12:45:14 NetworkManager[559]: <info>  [1734608714.8381] device (wlo1): supplicant interface state: associated -> 4way_handshake
12:45:14 NetworkManager[559]: <info>  [1734608714.8382] device (p2p-dev-wlo1): supplicant management interface state: associated -> 4way_handshake
12:45:14 wpa_supplicant[1069]: wlo1: WPA: Key negotiation completed with f0:4d:d4:2e:fd:04 [PTK=CCMP GTK=CCMP]
12:45:14 wpa_supplicant[1069]: wlo1: CTRL-EVENT-CONNECTED - Connection to f0:4d:d4:2e:fd:04 completed [id=0 id_str=]
12:45:14 systemd-networkd[402]: wlo1: Gained carrier
12:45:14 NetworkManager[559]: <info>  [1734608714.9852] device (wlo1): supplicant interface state: 4way_handshake -> completed
12:45:14 NetworkManager[559]: <info>  [1734608714.9853] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "73CF10F"
12:45:14 NetworkManager[559]: <info>  [1734608714.9853] device (p2p-dev-wlo1): supplicant management interface state: 4way_handshake -> completed
12:45:14 NetworkManager[559]: <info>  [1734608714.9856] device (wlo1): state change: config -> ip-config (reason 'none', managed-type: 'full')
12:45:14 NetworkManager[559]: <info>  [1734608714.9871] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
12:45:14 wpa_supplicant[1069]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-31 noise=9999 txrate=234000
12:45:15 NetworkManager[559]: <info>  [1734608715.0187] dhcp4 (wlo1): state changed new lease, address=192.168.1.58, acd pending
12:45:15 NetworkManager[559]: <info>  [1734608715.2223] dhcp4 (wlo1): state changed new lease, address=192.168.1.58
12:45:15 NetworkManager[559]: <info>  [1734608715.2230] policy: set '73CF10F' (wlo1) as default for IPv4 routing and DNS
12:45:15 systemd-timesyncd[544]: Network configuration changed, trying to establish connection.
12:45:15 systemd-resolved[535]: wlo1: Bus client set search domain list to: lan
12:45:15 systemd-resolved[535]: wlo1: Bus client set default route setting: yes
12:45:15 systemd-resolved[535]: wlo1: Bus client set DNS server list to: 192.168.1.254
12:45:15 NetworkManager[559]: <info>  [1734608715.2465] device (wlo1): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
12:45:15 NetworkManager[559]: <info>  [1734608715.2490] device (wlo1): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
12:45:15 NetworkManager[559]: <info>  [1734608715.2492] device (wlo1): state change: secondaries -> activated (reason 'none', managed-type: 'full')
12:45:15 NetworkManager[559]: <info>  [1734608715.2498] manager: NetworkManager state is now CONNECTED_SITE
12:45:15 NetworkManager[559]: <info>  [1734608715.2510] device (wlo1): Activation: successful, device activated.
12:45:15 geoclue[1026]: Failed to query location: No WiFi networks found
12:45:15 systemd-timesyncd[544]: Contacted time server 129.250.35.250:123 (2.arch.pool.ntp.org).
12:45:15 NetworkManager[559]: <info>  [1734608715.5492] manager: NetworkManager state is now CONNECTED_GLOBAL
12:45:16 systemd-networkd[402]: wlo1: Gained IPv6LL
12:45:18 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
12:45:22 systemd-homed[562]: name: changing state active → authenticating-for-acquire
12:45:22 systemd-homework[2605]: Provided password unlocks user record.
12:45:23 systemd-homework[2605]: Discovered used LUKS device /dev/mapper/home-name, and validated password.
12:45:23 systemd-homework[2605]: Successfully re-activated LUKS device.
12:45:23 systemd-homework[2605]: Provided password unlocks user record.
12:45:23 systemd-homework[2605]: Discovered used loopback device /dev/loop0.
12:45:23 systemd-homework[2605]: Read embedded .identity file.
12:45:23 systemd-homework[2605]: Provided password unlocks user record.
12:45:23 systemd-homework[2605]: Reconciling user identities completed (host and header version were identical).
12:45:23 systemd-homework[2605]: Reconciling embedded user identity completed (host and embedded version were identical).
12:45:23 systemd-homework[2605]: Everything completed.
12:45:23 systemd-homed[562]: name: changing state authenticating-for-acquire → active
12:45:23 gdm-password][2526]: pam_systemd_home(gdm-password:auth): Home for user name successfully acquired.
12:45:23 gdm-password][2526]: gkr-pam: unlocked login keyring
12:45:23 gnome-shell[1404]: clutter_actor_insert_child_at_index: assertion 'child->priv->parent == NULL' failed
12:45:23 gnome-shell[1404]: st_widget_get_theme_node called on the widget [0x5d74fd7e9030 StBoxLayout ("…")] which is not in the stage.
12:45:23 gnome-shell[1404]: st_widget_get_theme_node called on the widget [0x5d74fd470320 StLabel.vitals-panel-label:insensitive ("…")] which is not in the stage.
12:45:23 gnome-shell[1404]: st_widget_get_theme_node called on the widget [0x5d74fd7e9030 StBoxLayout ("…")] which is not in the stage.
12:45:23 gnome-shell[1404]: st_widget_get_theme_node called on the widget [0x5d74fd7eb250 StLabel.vitals-panel-label:insensitive ("…")] which is not in the stage.
12:45:23 gnome-shell[1404]: st_widget_get_theme_node called on the widget [0x5d74fd7e9030 StBoxLayout ("…")] which is not in the stage.
12:45:23 gnome-shell[1404]: st_widget_get_theme_node called on the widget [0x5d74fd7348b0 StLabel.vitals-panel-label:insensitive ("…")] which is not in the stage.
12:45:23 gnome-shell[1404]: [impatience] enabled
12:45:23 gnome-shell[1404]: [impatience] setting new speed: 0.5
12:45:23 NetworkManager[559]: <info>  [1734608723.7489] agent-manager: agent[c70970355a5a00ba,:1.67/org.gnome.Shell.NetworkAgent/60303]: agent registered
12:45:39 systemd[1]: Unmounting EFI System Partition Automount...
12:45:39 systemd[1]: boot.mount: Deactivated successfully.
12:45:39 systemd[1]: Unmounted EFI System Partition Automount.

seth · 2024-12-20 16:21:04

Please don't cut random lines from the journal - breaks syntax highlighting.

However

Dec 20  12:23:57 kernel: PM: suspend entry (s2idle)
…
Dec 20  12:23:57 kernel: Filesystems sync: 0.021 seconds
Dec 20  12:45:10 kernel: Freezing user space processes
…
Dec 20  12:45:10 kernel: PM: suspend exit

There's nothing really going on OS-wise during the s2idle

Certainly disable systemd-networkd.

Dec 20  12:45:10 gnome-shell[1404]: libinput error: event2  - Power Button: client bug: event processing lagging behind by 234ms, your system is too slow

certainly indicates some undue load.
Does any process consume a lot of CPU at this point?

wrt 30 minutes and the additional networkd service and resolved switching to cloudflare after you probably lost the network before the sleep: 28 minutes is a typical imap timeout

Sanity check: no parallel windows?
What's going on a bit ahead of the sleep (we can see resolved responding to the lost network but not the network cut etc.)

Also

Dec 20  12:45:11 systemd-homed[562]: name: changing state active → authenticating-for-acquire
Dec 20  12:45:11 systemd-homework[2531]: None of the supplied plaintext passwords unlock the user record's hashed passwords.
Dec 20  12:45:11 systemd-homed[562]: Authentication failed: Security token requires presence confirmation.
Dec 20  12:45:11 systemd-homed[562]: name: changing state authenticating-for-acquire → active
Dec 20  12:45:11 systemd-homed[562]: name: changing state active → authenticating-for-acquire
Dec 20  12:45:11 systemd-homework[2532]: None of the supplied plaintext passwords unlock the user record's hashed passwords.
Dec 20  12:45:11 systemd-homed[562]: Authentication failed: Password for home name is incorrect or not sufficient, and configured security token not found either.
Dec 20  12:45:11 systemd-homed[562]: name: changing state authenticating-for-acquire → active

would be a candidate to cause fringe stuff because virtually nobody is using that…

Cvlc · 2025-01-27 12:59:43

Sorry for the late reply, busy end of year / beginning of next

seth wrote:

Please don't cut random lines from the journal - breaks syntax highlighting.

Did I ? I piped the output to a text file so maybe that's why. I did remove hostname and date on every line for readability, maybe that's what you mean ?

seth wrote:

Certainly disable systemd-networkd.

Tried with and without, makes no difference.

seth wrote:

Dec 20  12:45:10 gnome-shell[1404]: libinput error: event2  - Power Button: client bug: event processing lagging behind by 234ms, your system is too slow
certainly indicates some undue load.
Does any process consume a lot of CPU at this point?

I don't notice anything strange at all.

seth wrote:

Sanity check: no parallel windows?

If you mean dual boot with windows, nope, this laptop's clean

I wouldn't bet on systemd-homed being a problem here, since the issue happens while the laptop is off...

I've found somewhat of a workaround, with

/etc/systemd/sleep.conf.d/00.conf
[Sleep]
HibernateDelaySec=720

"systemctl sleep" now hibernates after 12 min, I'll see if the issue still happens this way. Just have to lookup how to force gnome to use suspend-then-hibernate as well.

seth · 2025-01-27 14:48:23

maybe that's what you mean ?

Yes, removing those columns breaks the syntax highlighting of the journal.
If it's less about readability and more "privacy" (it's not sensitive data but whatever) you can replace the hostnae, but leave the timestamps alone - there're important data that strutures the events.

https://bbs.archlinux.org/viewtopic.php … 4#p2222374 wa down to the nvme and probably bogus APST…

Cvlc · 2025-01-28 14:12:17

hmm, interesting. I do have the following in the logs:

janv. 28 10:34:58 archlinux kernel: nvme 0000:01:00.0: platform quirk: setting simple suspend

I don't have any error mentioning APST though, nor do I see any of the errors listed on the wiki. I have two nvme SSDs inside, a Kingston that was in the laptop when I bought it and an additional (now main) samsung 980. I don't think any of the drives have any firmware upgrades but I'll look that up again. The suspend problem already existed when I only had the Kingston drive and Arch was installed on it. I can try pulling it out, but is it worth it if I don't see any of the errors from the wiki ?

[off topic] how do you read the logs to get syntax highlighting on the forum ? copy and paste them to journalctl ?

seth · 2025-01-28 14:58:43

* sqriptor (greatest and best text editor in the world. By my unbiased opinion backed science)
* lnav (is in the repos)

Instead of yanking the nvme out, just try to disable APST, maybe use the soft IOMMU as well.

Cvlc · 2025-01-28 17:32:39

Alright, after a first quick test, it looks like disabling APST via kernel cmdline does fix the suspend issue !

I'll have to confirm with longer tests though.

does it make sense to disable some power states for the drive only, instead of disabling APST completely (for both drives) ?

as in https://forums.debian.net/viewtopic.php?t=155053

seth · 2025-01-28 21:32:16

Or see https://wiki.archlinux.org/title/Solid_ … wer_saving and the following troubleshooting paragraph

Depends on
1. how critical battery time is to you
2. what you get to save (and in relation to the total draw - if you an get an additional 0.02W on a 20W total that's maybe a bit micro-optimizing…)
2. how much time you're willing to spend to fiddle around with that

But yes, ideally you only want to disable what's breaking the s2idle behavior.
You esp. want to avoid pcie_aspm=off because that affects *every* PCI device.

Cvlc · 2025-01-28 23:01:20

Well, spoke too fast, only seemed to work on a short test..... after being suspended for a few hours, the same happens again:

janv. 28 18:35:09 hostname systemd[1]: user.slice: Unit now frozen.
janv. 28 18:35:09 hostname systemd[1]: user-120.slice: Unit now frozen-by-parent.
janv. 28 18:35:09 hostname systemd[1]: session-7.scope: Unit now frozen-by-parent.
janv. 28 18:35:09 hostname systemd-sleep[2957]: Successfully froze unit 'user.slice'.
janv. 28 18:35:09 hostname systemd-sleep[2957]: Performing sleep operation 'suspend'...
janv. 28 18:35:09 hostname kernel: PM: suspend entry (s2idle)
-- Boot d009940caa044277b54a0114a65f5165 --
janv. 28 23:48:23 archlinux kernel: Linux version 6.12.10-arch1-1 (linux@archlinux) (gcc (GCC) 14.2.1 20240910, GNU ld (GNU Binutils) 2.43.1) #1 SMP PREEMPT_DYNAMIC Sat, 18 Jan 2025 02:26:57 +0000
janv. 28 23:48:23 archlinux kernel: Command line: rootflags=compress-force=zstd,autodefrag quiet bgrt_disable nowatchdog systemd.machine_id=9a957deed6504f4a8af1d08fb2170e04 nvme_core.default_ps_max_latency_us=0 i915.force_probe=!9a49 xe.force_probe=9a49
janv. 28 23:48:23 archlinux kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
janv. 28 23:48:23 archlinux kernel: BIOS-provided physical RAM map:
janv. 28 23:48:23 archlinux kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
janv. 28 23:48:23 archlinux kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
janv. 28 23:48:23 archlinux kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000061a66fff] usable
janv. 28 23:48:23 archlinux kernel: BIOS-e820: [mem 0x0000000061a67000-0x0000000064b66fff] reserved

I'll try soft IOMMU

seth · 2025-01-29 08:25:54

I'd throw the entirety of "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off iommu=soft" at the problem and see whether this is a viable vector at all.

Cvlc · 2025-01-29 12:31:28

seth wrote:

I'd throw the entirety of "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off iommu=soft" at the problem and see whether this is a viable vector at all.

Good point so I did that.... but sadly, the system still dies when suspended a long time.

Back to square one I guess...

seth · 2025-01-29 17:11:34

Yes. When suspended for a long time, the laptop doesn't respond to any keyboard or touchpad presses, but a single press of the power button starts a regular boot.

You did try the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) + REISUB?

Do you have an nvidia GPU?

Cvlc · 2025-01-31 10:47:24

seth wrote:

You did try the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) + REISUB?

The thing is, it's not that the laptop is unresponsive, it's just effectively shut down already.

Do you have an nvidia GPU?

No, Intel integrated graphics..

Last edited by Cvlc (2025-01-31 15:22:42)

seth · 2025-01-31 15:38:18

If it's "shut down" it won't consume any battery.
The problem is that you're trying to sleep+hibernate and the rtansition from sleep to hibernation fails.
The system wake up from the sleep for that state and then initiates the hibernation - this is the stage where it's presumingly hanging and sucking way your battery.

What if you only suspend for a really long time and try to wake the system from that S2idle manually?
Make sure to activate the sysrq beforehand and see whether you can use that at this point.

Arch Linux

#1 2024-12-14 11:39:55

Laptop (probably) heats up while suspended

#2 2024-12-14 12:30:10

Re: Laptop (probably) heats up while suspended

#3 2024-12-15 10:31:13

Re: Laptop (probably) heats up while suspended

#4 2024-12-15 12:53:45

Re: Laptop (probably) heats up while suspended

#5 2024-12-15 16:38:43

Re: Laptop (probably) heats up while suspended

#6 2024-12-15 22:01:05

Re: Laptop (probably) heats up while suspended

#7 2024-12-16 16:11:50

Re: Laptop (probably) heats up while suspended

#8 2024-12-16 16:25:59

Re: Laptop (probably) heats up while suspended

#9 2024-12-19 11:56:28

Re: Laptop (probably) heats up while suspended

#10 2024-12-20 16:21:04

Re: Laptop (probably) heats up while suspended

#11 2025-01-27 12:59:43

Re: Laptop (probably) heats up while suspended

#12 2025-01-27 14:48:23

Re: Laptop (probably) heats up while suspended

#13 2025-01-28 14:12:17

Re: Laptop (probably) heats up while suspended

#14 2025-01-28 14:58:43

Re: Laptop (probably) heats up while suspended

#15 2025-01-28 17:32:39

Re: Laptop (probably) heats up while suspended

#16 2025-01-28 21:32:16

Re: Laptop (probably) heats up while suspended

#17 2025-01-28 23:01:20

Re: Laptop (probably) heats up while suspended

#18 2025-01-29 08:25:54

Re: Laptop (probably) heats up while suspended

#19 2025-01-29 12:31:28

Re: Laptop (probably) heats up while suspended

#20 2025-01-29 17:11:34

Re: Laptop (probably) heats up while suspended

#21 2025-01-31 10:47:24

Re: Laptop (probably) heats up while suspended

#22 2025-01-31 15:38:18

Re: Laptop (probably) heats up while suspended

Board footer