Re: s2idle on kdell xps 9730 does go to sleep but laptop is warm

Rafael J. Wysocki
2025-06-02T14:23:58Z

On Thu, May 15, 2025 at 9:45 AM Marc MERLIN <marc@merlins.org> wrote:
>
> and burn a lot of battery during full kernel sleep
> Reply-To:
> X-Sysadmin: BOFH
> X-URL: http://marc.merlins.org/
>
> With kernel 6.6.9 when I put the laptop to sleep, syslog shows that the
> laptop was sleeping for 9h, fans were stopped, but when I gabbed my
> laptop it was warm and burned 80% of the battery overnight.

First off, I'd try a newer kernel. Say 6.15.0 (unless you boot with
"nosmt" in the kernel command line).

> And yet, linux was not running, my logs show the kernel went into ACPI
> sleep and back out

It wouldn't be "ACPI sleep" if it was suspend-to-idle.

> Logs show the system slept for 9h and went to sleep with s2idle.
>
> Is it the wrong sleep outside of suspend to disk and full shutdown?

No, it shouldn't be.

> Are there devices that should have been powered off but didn't
> (evidently yes since battery loss was 80% and laptop was warm)

There seems to be driver support missing for some devices.

> logs below
>
> 2025-05-14T00:01:20 merlin root: >>>>>>>>>> suspend #1 1747206080
>
> 2025-05-14T00:01:21 merlin dbus-daemon[2846]: [system] Activating via systemd: service name='org.wicd.daemon' unit='dbus-org.wicd.daemon.service' requested by ':1.1130' (uid=0 pid=3357435 comm="/usr/bin/python3 /usr/share/wicd/daemon/suspend.py")
> 2025-05-14T00:01:21 merlin dbus-daemon[2846]: [system] Activation via systemd failed for unit 'dbus-org.wicd.daemon.service': Unit dbus-org.wicd.daemon.service not found.
> 2025-05-14T00:01:21 merlin kernel: [1388664.621668] PM: suspend entry (s2idle)
> 2025-05-14T00:01:21 merlin kernel: [1388664.625122] Filesystems sync: 0.003 seconds
> 2025-05-14T09:20:43 merlin kernel: [1388664.635518] Freezing user space processes
> 2025-05-14T09:20:43 merlin kernel: [1388664.638313] Freezing user space processes completed (elapsed 0.002 seconds)
> 2025-05-14T09:20:43 merlin kernel: [1388664.638320] OOM killer disabled.
> 2025-05-14T09:20:43 merlin kernel: [1388664.638322] Freezing remaining freezable tasks
> 2025-05-14T09:20:43 merlin kernel: [1388664.640285] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
> 2025-05-14T09:20:43 merlin kernel: [1388664.640290] printk: Suspending console(s) (use no_console_suspend to debug)
> (...)
> 2025-05-14T09:20:43 merlin kernel: [1422225.195325] OOM killer enabled.
> 2025-05-14T09:20:43 merlin kernel: [1422225.195328] Restarting tasks ... done.
> 2025-05-14T09:20:43 merlin kernel: [1422225.204356] vgaarb: client 0x00000000f7b9cd5c called 'target'
> 2025-05-14T09:20:43 merlin kernel: [1422225.204376] vgaarb: PCI:0000:00:02.0 ==> 0000:00:02.0 pdev 00000000dec5b5e7
> 2025-05-14T09:20:43 merlin kernel: [1422225.204383] vgaarb: vgadev 00000000dca48b8a
> 2025-05-14T09:20:43 merlin kernel: [1422225.321870] PM: suspend exit

Well, it obviously is not a complete log.

What processor is there in your system?