Re: [UFC : SPAM BAS] Re: Laptop resumes each 1h13 after suspend-to-ram
On 13/09/2025 05:27, Max Nikulin wrote:
On 12/09/2025 19:17, Eugen Dedu wrote:
On 12/09/2025 03:55, Max Nikulin wrote:
On 11/09/2025 22:30, Eugen Dedu wrote:
I have a weird problem with suspend-to-ram with my Dell Precision
3591 laptop, which awakes alone/itself, without touching it
[...]
Thu 11 Sep 04:42:30 CEST 2025
Thu 11 Sep 05:55:58 CEST 2025
Thu 11 Sep 07:09:26 CEST 2025
Have you tried to read logs to see if some task is started
immediately after resume?
sudo journalctl --since '2025-09-11 05:50'
It is very long, I put it at https://imsva91-ctp.trendmicro.com:443/
wis/clicktime/v1/query?
url=https%3a%2f%2fdedu.fr%2flog.txt&umid=10933972-3EA6-5D06-9AD5-
E79C4FAA25CD&auth=0fd6724f999658b6dfc6e5175590485fef79248c-
c6820eb8141af66781ac5a48b5e7ebdeb8a24507.
Have you tried to read it?
I looked at it, but I have tested so many things that I am out of ideas
and do not know what to try next.
kernel: (NULL device *): firmware: failed to load nvidia/ad107/gsp/
gsp-535.113.01.bin (-2)
I expect, you may make it a bit shorter by installing firmware-nvidia-
graphics.
I have this package installed, but ad107 subdirectory is empty, cf.
https://packages.debian.org/sid/all/firmware-nvidia-graphics/filelist
I see 2 tasks started immediately after resume:
systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata
and update motd...
systemd[1]: Starting phpsessionclean.service - Clean php session files...
Is it common pattern for every resume? systemd.timer(5) describes at
least WakeSystem=, so I would inspect suspicious units
systemctl cat fwupd-refresh.timer
systemctl show --property WakeSystem fwupd-refresh.timer
(or something similar for unit name).
I noticed that even if I stop fwupd service, it restarts automatically
after some time. So, to be sure, I removed all packages fwupd*:
snoopy:~$ dpkg -l \*fwup*|cat
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===========================-============-============-=================================
un fwupd <none> <none> (no
description available)
un fwupdate <none> <none> (no
description available)
un gnome-software-plugin-fwupd <none> <none> (no
description available)
snoopy:~$
I also removed php packages:
snoopy:~$ dpkg -l \*php*|cat
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
un libgv-php5 <none> <none> (no description available)
un php-crypt-gpg <none> <none> (no description available)
snoopy:~$
I rebooted the computer, to be sure that no timer left running after
uninstallation. Timers seems ok:
root@snoopy:~# systemctl list-timers --all
NEXT LEFT LAST
PASSED UNIT ACTIVATES >
Mon 2025-09-15 00:00:00 CEST 4h 41min Sun 2025-09-14 01:07:59 CEST
- dpkg-db-backup.timer dpkg-db-backup.servi>
Mon 2025-09-15 00:23:19 CEST 5h 4min Sun 2025-09-14 01:07:59 CEST
- logrotate.timer logrotate.service
Mon 2025-09-15 00:36:45 CEST 5h 17min Mon 2025-09-08 04:45:31 CEST
- fstrim.timer fstrim.service
Mon 2025-09-15 01:51:15 CEST 6h Sun 2025-09-14 01:07:59 CEST
- man-db.timer man-db.service
Mon 2025-09-15 03:40:02 CEST 8h Sun 2025-09-14 16:41:15 CEST
1h 3min ago apt-daily.timer apt-daily.service
Mon 2025-09-15 06:06:36 CEST 10h Sun 2025-09-14 08:24:56 CEST
2h 7min ago apt-daily-upgrade.timer apt-daily-upgrade.se>
Mon 2025-09-15 17:21:34 CEST 22h Sun 2025-09-14 14:56:31 CEST
1h 57min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-cle>
Sun 2025-09-21 03:10:04 CEST 6 days Sun 2025-09-14 03:34:48 CEST
2h 10min ago e2scrub_all.timer e2scrub_all.service
Wed 2025-10-01 00:00:51 CEST 2 weeks 2 days Mon 2025-09-01 02:22:27 CEST
- wtmpdb-rotate.timer wtmpdb-rotate.service
9 timers listed.
root@snoopy:~#
Finally, I do not have any suspicious WakeSystem:
root@snoopy:~# grep -r WakeSystem /etc/systemd/
root@snoopy:~#
The only file related to awaking I modified after installation is
/etc/systemd/logind.conf, for ex. declaring that button on keyboard is
for sleeping; however, I tested putting back original values and the
problem was still there.
However, the awaking problem is still there.
Note that the awake occurs only I suspend by pressing the button on the
keyboard; if I close the lid it does not awake.
kernel: PM: suspend entry (s2idle)
Is it common for both cases of keyboard button and lid? On my laptop I
have "PM: suspend entry (deep)", "ACPI: PM: Preparing to enter system
sleep state S3", "ACPI: PM: Waking up from system sleep state S3".
Perhaps different power states are configured for different event.
For me it is s2idle in both cases:
root@snoopy:~# journalctl --since '2025-09-14 19:07' >button
root@snoopy:~# journalctl --since '2025-09-14 19:09' >lid
root@snoopy:~# ls -l button lid
-rw-rw-r-- 1 root root 22490 Sep 14 19:07 button
-rw-rw-r-- 1 root root 23849 Sep 14 19:09 lid
root@snoopy:~# grep suspend\ entry button
Sep 14 19:07:13 snoopy kernel: PM: suspend entry (s2idle)
root@snoopy:~# grep suspend\ entry lid
Sep 14 19:09:04 snoopy kernel: PM: suspend entry (s2idle)
root@snoopy:~# grep deep *
root@snoopy:~# grep reparing *
root@snoopy:~# grep Waking *
root@snoopy:~#
Sorry if I did something wrong or I forgot something. Please give
instructions to do next.
Reply to: