Power Consumption on Suspend

[JudgeFudge]

Hello there, newbie here!

I have the Pinephone in the 3 GB Version with the Keyboard case, using it as a PDA with Gnome 3 (NOT phosh) as the DE, modem disabled via hardware switch.
Software works great, Performance as expected and battery time in combination with the battery case no problem in active use. However, in suspend, the battery consumption stays unreasonably high, draining battery of phone and case in around 24 hours, thats more than 1 Watt in suspend to RAM.

I've tried around a lot by now, but I've hit a wall here and wanted to ask if there are similar problems and workarounds.

First, the suspend is triggered via systemd, so the /etc/systemd/sleep.conf is used. I've set the SuspendState to mem, drain remains high. The drain is even higher when set to standby or freeze, although not much. Gnome 3 uses systemd for this, I've tested it by setting hibernate settings into the suspendvariables with the expected outcome.

So forward to the logs. Journalctl says

Code:

Jul 10 22:35:46 mobian systemd[1]: Reached target sleep.target - Sleep.
Jul 10 22:35:46 mobian systemd[1]: Starting systemd-suspend.service - System Suspend...
Jul 10 22:35:46 mobian systemd-sleep[7427]: Entering sleep state 'suspend'...
Jul 10 22:35:46 mobian kernel: PM: suspend entry (deep)
Jul 11 01:51:03 mobian kernel: Filesystems sync: 0.115 seconds
Jul 11 01:51:03 mobian kernel: Freezing user space processes
Jul 11 01:51:03 mobian kernel: Freezing user space processes completed (elapsed 0.012 seconds)
Jul 11 01:51:03 mobian kernel: OOM killer disabled.
Jul 11 01:51:03 mobian kernel: Freezing remaining freezable tasks
Jul 11 01:51:03 mobian kernel: Freezing remaining freezable tasks completed (elapsed 0.006 seconds)
Jul 11 01:51:03 mobian kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jul 11 01:51:03 mobian kernel: musb-sunxi 1c19000.usb: sunxi-musb does not have ULPI bus control register
Jul 11 01:51:03 mobian kernel: Disabling non-boot CPUs ...
Jul 11 01:51:03 mobian kernel: psci: CPU1 killed (polled 4 ms)
Jul 11 01:51:03 mobian kernel: psci: CPU2 killed (polled 4 ms)
Jul 11 01:51:03 mobian kernel: psci: CPU3 killed (polled 4 ms)
Jul 11 01:51:03 mobian kernel: Enabling non-boot CPUs ...
Jul 11 01:51:03 mobian kernel: Detected VIPT I-cache on CPU1
Jul 11 01:51:03 mobian kernel: arch_timer: CPU1: Trapping CNTVCT access
Jul 11 01:51:03 mobian kernel: CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
Jul 11 01:51:03 mobian kernel: CPU1 is up
Jul 11 01:51:03 mobian kernel: Detected VIPT I-cache on CPU2
Jul 11 01:51:03 mobian kernel: arch_timer: CPU2: Trapping CNTVCT access
Jul 11 01:51:03 mobian kernel: CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
Jul 11 01:51:03 mobian kernel: CPU2 is up
Jul 11 01:51:03 mobian kernel: Detected VIPT I-cache on CPU3
Jul 11 01:51:03 mobian kernel: arch_timer: CPU3: Trapping CNTVCT access
Jul 11 01:51:03 mobian kernel: CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
Jul 11 01:51:03 mobian kernel: CPU3 is up
Jul 11 01:51:03 mobian kernel: sunxi-rsb 1f03400.rsb: RSB running at 4000000 Hz
Jul 11 01:51:03 mobian kernel: pinephone-keyboard 2-0015: Failed to read scan data: -13
Jul 11 01:51:03 mobian kernel: musb-sunxi 1c19000.usb: sunxi-musb does not have ULPI bus control register
Jul 11 01:51:03 mobian kernel: OOM killer enabled.
Jul 11 01:51:03 mobian kernel: Restarting tasks ... done.
Jul 11 01:51:03 mobian kernel: PM: suspend exit

As can be seen, the suspend entry is deep, so this is done to RAM in theory, this is no problem with falling back to s2idle or anything like that.
The interesting and thing here seems to be the fact that the 

Code:

Freezing user space processes

Is done at wakeup, not at sleep. I am relatively sure that this is the issue, as I've found unrelated issues several years old referring to this as the culprit for high suspend energy consumption on laptops of different kinds. 
https://askubuntu.com/questions/828486/k...pend-tasks
Some were fixed by bios settings, some by ACPI Settings, for what I've seen. Both don't show up in the wiki, so I am asking here for two things:


1. Is this a normal behavior others are experiencing? A suspend that high would drain a Pinephone in about 8 Hours, no usage and no active modem. 

2. Any Idea how to fix this? Is this due to a newer kernel? This is freshly setup, so I dont have a specific fallback right now.



Before settling for Gnome, I've played around with lomiri, but I've uninstalled it. Otherwise the image is pretty clean from a software standpoint (no system installations, just userspace programs like chromium or gedit). All Packages are up to date of course, no external repos were added.

Code:

mobian@mobian:~$ uname -a
Linux mobian 6.1-sunxi64 #1 SMP Mon Jul  3 04:42:56 UTC 2023 aarch64 GNU/Linux
mobian@mobian:~$ cat /etc/debian_version
12.0

If you need more debugging information, don't hesitate to ask. If you think this is the wrong place for those questions I apologize and would be glad to get a hint were I can find some help.