Re: Laptop resumes each 1h13 after suspend-to-ram
Thanks for checking that and supplying those lines from the output, Eugen. I've been away and am just getting back to reading through this list, so my apologies if you've already progressed beyond this.
Regarding this line:
Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
There's some discussion of this issue on the Mint forum which is specific to Cinnamon, but in the off chance it helps you can check it out here:
Re: Kernel Lockdown prevents Suspend
What I found interesting, and you might want to try it, is the two different commands to suspend the system and one of them worked correctly.
...there are two different ways to suspend, systemctl suspend or
pm-suspend
The OP over there reported that pm-suspend resolved the issue for them.
Regarding this line:
wlp0s20f3: Limiting TX power to 30 (30 - 0) dBm as advertised by e4:9e:12:bd:3f:ec
That sure looks like power saving is disabled on this interface so it won't throttle the wireless signal strength. If that's true, then your system won't be able to suspend because wlp0s20f3 is requesting full-strength signal. Seems like an Energy Efficient
Ethernet (EEE) or Green Ethernet setting on this interface might be preventing this system from suspending properly. What chip is it and which driver is in use?
On 9/15/2025 3:54 AM, Eugen Dedu wrote:
On 11/09/2025 21:38, Cliff Hayes wrote:
Maybe try to correlate some ACPI messages in the kernel log to the unexpected wake.
I'd suggest a peek using the following command after an unexpected wake:
journalctl --dmesg
I see this during suspend:
Sep 15 12:37:22 snoopy kernel: spd5118 0-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
Sep 15 12:37:22 snoopy kernel: spd5118 0-0050: PM: failed to resume async: error -6
also:
Sep 15 12:37:23 snoopy kernel: iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode
and this:
Sep 15 12:37:27 snoopy kernel: wlp0s20f3: Limiting TX power to 30 (30 - 0) dBm as advertised by e4:9e:12:bd:3f:ec
Sep 15 12:37:28 snoopy kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 15 12:37:28 snoopy kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 15 12:37:28 snoopy kernel: wlp0s20f3: deauthenticating from e4:9e:12:bd:3f:ec by local choice (Reason: 3=DEAUTH_LEAVING)
Sep 15 12:37:29 snoopy kernel: PM: suspend entry (s2idle)
But I think all the above messages are found also in, for ex.:
journalctl --since '2025-09-15 12:37'
On 9/11/25 11:32, Eugen Dedu wrote:
On 11/09/2025 20:14, Kent West wrote:
On Thu, Sep 11, 2025 at 12:47 PM Eugen Dedu
<eugen.dedu@univ-fcomte.fr>
wrote:
I tested it too, disabled it from the UEFI, without success.
On 11/09/2025 19:27, Jeremy Nicoll wrote:
On Thu, 11 Sep 2025, at 16:30, Eugen Dedu wrote:
Hi,
I have a weird problem ...
Could it be due to: Wake-on-LAN
https://en.wikipedia.org/wiki/Wake-on-LAN ?
Some BIOSes, in the Power settings, have an option to power-on at certain
times. Might be worth a look.
I have looked carefully at all BIOS settings, including Power section.
Additionally, I looked at
https://wiki.archlinux.org/title/ Power_management/Wakeup_triggers, in particular to the dmidecode command, to show the reason of the last resume, however it shows:
Wake-up Type: Other
hence again no success to find the culprit.
Reply to: