Timed suspend fails, manual works

krill · 26 December 2020 12:18

Mod-edit: Formatting and layout

Hi.

My desktop machine can’t suspend via the timer if either option to lock the session is enabled under:

Power - Security:
- “Lock session automatically” ➔ when screen saver is disabled/enabled.
- and “Lock screen when system is going to sleep”.

Instead of suspending, the screen remains in standby and a login screen is shown if the screen is woken up.
If I proceed to login, the ethernet link is now down and if I do sudo reboot now then the machine shuts down instead of rebooting.

The journal then looks like this:

dec 26 12:42:30 sunshine kernel: PM: suspend entry (deep)
dec 26 12:42:30 sunshine kernel: Filesystems sync: 0.007 seconds
dec 26 12:42:30 sunshine rtkit-daemon[1246]: Supervising 3 threads of 2 processes of 1 users.
dec 26 12:42:30 sunshine rtkit-daemon[1246]: Successfully made thread 2734 of process 1218 owned by '1000' RT at priority 5.
dec 26 12:42:30 sunshine rtkit-daemon[1246]: Supervising 4 threads of 2 processes of 1 users.
dec 26 12:42:31 sunshine rtkit-daemon[1246]: Supervising 3 threads of 2 processes of 1 users.
dec 26 12:42:31 sunshine rtkit-daemon[1246]: Successfully made thread 2735 of process 1218 owned by '1000' RT at priority 5.
dec 26 12:42:31 sunshine rtkit-daemon[1246]: Supervising 4 threads of 2 processes of 1 users.
dec 26 12:42:32 sunshine audit[2749]: CRED_ACQ pid=2749 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:setcred grantors=pam_env,pam_permit acct="lightdm" exe="/usr/bin/lightdm" hos>
dec 26 12:42:32 sunshine lightdm[2749]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=969) by (uid=0)
dec 26 12:42:32 sunshine kernel: audit: type=1103 audit(1608982952.500:105): pid=2749 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:setcred grantors=pam_env,pam_permit acct="light>
dec 26 12:42:32 sunshine systemd[1]: Created slice User Slice of UID 969.
dec 26 12:42:32 sunshine systemd[1]: Starting User Runtime Directory /run/user/969...
dec 26 12:42:32 sunshine systemd-logind[505]: New session c2 of user lightdm.
dec 26 12:42:32 sunshine systemd[1]: Finished User Runtime Directory /run/user/969.
dec 26 12:42:32 sunshine audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=user-runtime-dir@969 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? ad>
dec 26 12:42:32 sunshine systemd[1]: Starting User Manager for UID 969...
dec 26 12:42:32 sunshine kernel: audit: type=1130 audit(1608982952.513:106): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=user-runtime-dir@969 comm="systemd" exe="/usr/lib/sy>
dec 26 12:42:32 sunshine dbus-daemon[500]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.157' (uid=0 pid=2753 comm=">
dec 26 12:42:32 sunshine dbus-daemon[500]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
dec 26 12:42:32 sunshine systemd[2753]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
dec 26 12:42:32 sunshine audit[2753]: USER_ACCT pid=2753 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:accounting grantors=pam_access,pam_permit,pam_time acct="lightdm" exe="/usr/>

It suspends and wakes fine if I manually select Suspend or if neither “Lock screen” option is enabled under Power - Security.

contrasting log:

dec 26 12:17:36 sunshine kernel: r8169 0000:05:00.0 eno1: Link is Down
dec 26 12:17:36 sunshine systemd[1]: Reached target Sleep.
dec 26 12:17:36 sunshine systemd[1]: Starting Suspend...
dec 26 12:17:37 sunshine wpa_supplicant[1004]: nl80211: deinit ifname=p2p-dev-wlp6s0 disabled_11b_rates=0
dec 26 12:17:37 sunshine wpa_supplicant[1004]: nl80211: deinit ifname=wlp6s0 disabled_11b_rates=0
dec 26 12:17:37 sunshine systemd-sleep[1577]: Suspending system...
dec 26 12:17:37 sunshine kernel: PM: suspend entry (deep)
dec 26 12:17:37 sunshine kernel: Filesystems sync: 0.008 seconds
dec 26 12:17:37 sunshine rtkit-daemon[1246]: Supervising 2 threads of 1 processes of 1 users.
dec 26 12:17:37 sunshine rtkit-daemon[1246]: Successfully made thread 1783 of process 1218 owned by '1000' RT at priority 5.
dec 26 12:17:37 sunshine rtkit-daemon[1246]: Supervising 3 threads of 1 processes of 1 users.
dec 26 12:17:37 sunshine rtkit-daemon[1246]: Supervising 2 threads of 1 processes of 1 users.
dec 26 12:17:37 sunshine rtkit-daemon[1246]: Successfully made thread 1784 of process 1218 owned by '1000' RT at priority 5.
dec 26 12:17:37 sunshine rtkit-daemon[1246]: Supervising 3 threads of 1 processes of 1 users.
dec 26 12:23:15 sunshine kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
dec 26 12:23:15 sunshine kernel: OOM killer disabled.
dec 26 12:23:15 sunshine kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
dec 26 12:23:15 sunshine kernel: printk: Suspending console(s) (use no_console_suspend to debug)
dec 26 12:23:15 sunshine kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
dec 26 12:23:15 sunshine kernel: sd 0:0:0:0: [sda] Stopping disk
dec 26 12:23:15 sunshine kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache
dec 26 12:23:15 sunshine kernel: sd 3:0:0:0: [sdc] Synchronizing SCSI cache
dec 26 12:23:15 sunshine kernel: sd 2:0:0:0: [sdb] Stopping disk
dec 26 12:23:15 sunshine kernel: sd 3:0:0:0: [sdc] Stopping disk
dec 26 12:23:15 sunshine kernel: ACPI: Preparing to enter system sleep state S

Tried running xfce4-power-manager in debug but didn’t get much out of it.
When sleep is about to be triggered it said:

TRACE[xfpm-manager.c:493] xfpm_manager_alarm_timeout_cb(): Alarm inactivity timeout id 3

xfconf-query -c xfce4-power-manager -lv gives:

/xfce4-power-manager/inactivity-on-ac     16
/xfce4-power-manager/power-button-action  1
/xfce4-power-manager/show-tray-icon       1

Saw several thread on waking from suspend but I haven’t seen this problem precisely.
If I missed it; I’m sorry and would appreciate a pointer to the related thread

My sys:
5.9.11-3-MANJARO x86_64
Ryzen 5 3600
B550 motherboard
Nvidia RTX 2060

Connected peripherals are possibly irrelevant since the issue seems account/authentication-based.
Same version of Manjaro but with gnome has no issues going into suspend on a timer.

Thanks for reading.

megavolt · 26 December 2020 18:23

Hey @krill

The logs show nothing really special.

Just a thought, but i think light-locker conflicts somehow with the xfce power management. I had a similar issue on my laptop with xfce.

Just completely disable or remove light-locker solved my problem.

However… display power management and light-locker don’t work great together at the same time, if you use a laptop, which have usually more options in display power management. On Systems with basic functions (usually a tower) there it works great.

Hope that helps…

krill · 26 December 2020 18:43

Hi @megavolt !

Thanks for your reply. Yes, disabling both options under the Security tab in the XFCE power management gui resolves the issue, but it also leaves the machine accessible* .

Are you saying a desktop (non-laptop), with few options under display power management, like on my desktop machine, the light-locker usually works alright together with display power management?

I would ideally like the display go to standby after a short while and for the machine to suspend after an hour or two. It isn’t that important when the screen locks but it would be nice if it did.

*I’d have bigger issues if someone accessed my machine as this is a one person household bar a couple of cats but it’s an an ingrained habit to have the screen lock when the machine suspends or the screen goes into standby, as well as mandatory in the workplace.

megavolt · 26 December 2020 19:26

Ok that is the main thing, that does not work. I must admit, that i never used timed suspend on my tower, but on my laptop it suspend after 1h successfully.

I am going to test timed suspend on my main system… will report later.

Update

Confirmed… timed suspend does not work on my main system. As i see in my logs…

working manual triggered suspend

Dez 26 20:59:10 bolobi systemd-sleep[3156]: Suspending system...
Dez 26 20:59:10 bolobi kernel: PM: suspend entry (deep)
Dez 26 20:59:12 bolobi lightdm[3301]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=969) by (uid=0)
Dez 26 20:59:12 bolobi systemd[1]: Created slice User Slice of UID 969.
Dez 26 20:59:12 bolobi systemd[1]: Starting User Runtime Directory /run/user/969...
Dez 26 20:59:12 bolobi systemd-logind[603]: New session c2 of user lightdm.
Dez 26 20:59:12 bolobi systemd[1]: Finished User Runtime Directory /run/user/969.
Dez 26 20:59:12 bolobi systemd[1]: Starting User Manager for UID 969...
Dez 26 20:59:12 bolobi dbus-daemon[597]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.78' (uid=0 pid=3306 comm="(systemd) ")
Dez 26 20:59:12 bolobi dbus-daemon[597]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Dez 26 20:59:12 bolobi systemd[3306]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Dez 26 20:59:12 bolobi systemd[3306]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[lightdm] ruser=[<unknown>] rhost=[<unknown>]
Dez 26 20:59:12 bolobi systemd[3306]: pam_unix(systemd-user:session): session opened for user lightdm(uid=969) by (uid=0)
Dez 26 20:59:12 bolobi systemd[3306]: pam_env(systemd-user:session): deprecated reading of user environment enabled
Dez 26 20:59:12 bolobi systemd-xdg-autostart-generator[3314]: Configuration file /etc/xdg/autostart/msm_notifier.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Dez 26 20:59:13 bolobi systemd[3306]: Queued start job for default target Main User Target.
Dez 26 20:59:13 bolobi systemd[3306]: -.slice: Failed to migrate controller cgroups from /user.slice/user-969.slice/user@969.service, ignoring: Permission denied
Dez 26 20:59:13 bolobi systemd[3306]: Created slice User Application Slice.
Dez 26 20:59:13 bolobi systemd[3306]: Reached target Paths.
Dez 26 20:59:13 bolobi systemd[3306]: Reached target Timers.
Dez 26 20:59:13 bolobi systemd[3306]: Starting D-Bus User Message Bus Socket.
Dez 26 20:59:13 bolobi systemd[3306]: Listening on GnuPG network certificate management daemon.
Dez 26 20:59:13 bolobi systemd[3306]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dez 26 20:59:13 bolobi systemd[3306]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Dez 26 20:59:13 bolobi systemd[3306]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dez 26 20:59:13 bolobi systemd[3306]: Listening on GnuPG cryptographic agent and passphrase cache.
Dez 26 20:59:13 bolobi systemd[3306]: Listening on p11-kit server.
Dez 26 20:59:13 bolobi systemd[3306]: Listening on Multimedia System.
Dez 26 20:59:13 bolobi systemd[3306]: Listening on Sound System.
Dez 26 20:59:13 bolobi systemd[3306]: Listening on D-Bus User Message Bus Socket.
Dez 26 20:59:13 bolobi systemd[3306]: Reached target Sockets.
Dez 26 20:59:13 bolobi systemd[3306]: Reached target Basic System.
Dez 26 20:59:13 bolobi systemd[1]: Started User Manager for UID 969.
Dez 26 20:59:13 bolobi systemd[3306]: Starting Update XDG user dir configuration...
Dez 26 20:59:13 bolobi systemd[1]: Started Session c2 of user lightdm.
Dez 26 20:59:13 bolobi systemd[3306]: xdg-user-dirs-update.service: Succeeded.
Dez 26 20:59:13 bolobi systemd[3306]: Finished Update XDG user dir configuration.
Dez 26 20:59:13 bolobi systemd[3306]: Reached target Main User Target.
Dez 26 20:59:13 bolobi systemd[3306]: Startup finished in 139ms.
Dez 26 20:59:13 bolobi systemd[3306]: Started D-Bus User Message Bus.
Dez 26 20:59:13 bolobi dbus-daemon[3320]: [session uid=969 pid=3320] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=969 pid=3318 comm="/usr/bin/lightdm-gtk-greeter ")
Dez 26 20:59:13 bolobi systemd[3306]: Starting Accessibility services bus...
Dez 26 20:59:13 bolobi dbus-daemon[3320]: [session uid=969 pid=3320] Successfully activated service 'org.a11y.Bus'
Dez 26 20:59:13 bolobi systemd[3306]: Started Accessibility services bus.
Dez 26 20:59:13 bolobi dbus-daemon[3320]: [session uid=969 pid=3320] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=969 pid=3318 comm="/usr/bin/lightdm-gtk-greeter ")
Dez 26 20:59:13 bolobi systemd[3306]: Starting Virtual filesystem service...
Dez 26 20:59:13 bolobi dbus-daemon[3320]: [session uid=969 pid=3320] Successfully activated service 'org.gtk.vfs.Daemon'
Dez 26 20:59:13 bolobi systemd[3306]: Started Virtual filesystem service.
Dez 26 20:59:13 bolobi polkitd[601]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Dez 26 20:59:13 bolobi polkitd[601]: <no filename>:4: subject=[Subject pid=3318 user='lightdm' groups=lightdm seat='seat0' session='c2' local=true active=true]
Dez 26 20:59:13 bolobi polkitd[601]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Dez 26 20:59:13 bolobi polkitd[601]: <no filename>:4: subject=[Subject pid=3318 user='lightdm' groups=lightdm seat='seat0' session='c2' local=true active=true]
Dez 26 20:59:13 bolobi polkitd[601]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Dez 26 20:59:13 bolobi polkitd[601]: <no filename>:4: subject=[Subject pid=3318 user='lightdm' groups=lightdm seat='seat0' session='c2' local=true active=true]
Dez 26 20:59:13 bolobi kernel: Filesystems sync: 3.035 seconds
Dez 26 20:59:13 bolobi at-spi-bus-launcher[3327]: dbus-daemon[3327]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=969 pid=3318 comm="/usr/bin/lightdm-gtk-greeter ")
Dez 26 20:59:13 bolobi at-spi-bus-launcher[3327]: dbus-daemon[3327]: Successfully activated service 'org.a11y.atspi.Registry'
Dez 26 20:59:13 bolobi at-spi-bus-launcher[3349]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Dez 26 20:59:23 bolobi kernel: Freezing user space processes ... (elapsed 0.003 seconds) done.
Dez 26 20:59:23 bolobi kernel: OOM killer disabled.
Dez 26 20:59:23 bolobi kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Dez 26 20:59:23 bolobi kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dez 26 20:59:23 bolobi kernel: sd 3:0:0:0: [sdd] Synchronizing SCSI cache
Dez 26 20:59:23 bolobi kernel: sd 3:0:0:0: [sdd] Stopping disk
Dez 26 20:59:23 bolobi kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Dez 26 20:59:23 bolobi kernel: sd 1:0:0:0: [sdb] Stopping disk
Dez 26 20:59:23 bolobi kernel: sd 2:0:0:0: [sdc] Synchronizing SCSI cache
Dez 26 20:59:23 bolobi kernel: sd 2:0:0:0: [sdc] Stopping disk
Dez 26 20:59:23 bolobi kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Dez 26 20:59:23 bolobi kernel: sd 0:0:0:0: [sda] Stopping disk
Dez 26 20:59:23 bolobi kernel: ACPI: Preparing to enter system sleep state S3
Dez 26 20:59:23 bolobi kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Dez 26 20:59:23 bolobi kernel: PM: Saving platform NVS memory
Dez 26 20:59:23 bolobi kernel: Disabling non-boot CPUs ...
Dez 26 20:59:23 bolobi kernel: smpboot: CPU 1 is now offline
Dez 26 20:59:23 bolobi kernel: smpboot: CPU 2 is now offline
Dez 26 20:59:23 bolobi kernel: smpboot: CPU 3 is now offline
Dez 26 20:59:23 bolobi kernel: ACPI: Low-level resume complete
Dez 26 20:59:23 bolobi kernel: PM: Restoring platform NVS memory
Dez 26 20:59:23 bolobi kernel: LVT offset 0 assigned for vector 0x400
Dez 26 20:59:23 bolobi kernel: Enabling non-boot CPUs ...
Dez 26 20:59:23 bolobi kernel: x86: Booting SMP configuration:
Dez 26 20:59:23 bolobi kernel: smpboot: Booting Node 0 Processor 1 APIC 0x11
Dez 26 20:59:23 bolobi kernel: microcode: CPU1: patch_level=0x06001119
Dez 26 20:59:23 bolobi kernel: ACPI: \_PR_.P001: Found 2 idle states
Dez 26 20:59:23 bolobi kernel: CPU1 is up
Dez 26 20:59:23 bolobi kernel: smpboot: Booting Node 0 Processor 2 APIC 0x12
Dez 26 20:59:23 bolobi kernel: microcode: CPU2: patch_level=0x06001119
Dez 26 20:59:23 bolobi kernel: ACPI: \_PR_.P002: Found 2 idle states
Dez 26 20:59:23 bolobi kernel: CPU2 is up
Dez 26 20:59:23 bolobi kernel: smpboot: Booting Node 0 Processor 3 APIC 0x13
Dez 26 20:59:23 bolobi kernel: microcode: CPU3: patch_level=0x06001119
Dez 26 20:59:23 bolobi kernel: ACPI: \_PR_.P003: Found 2 idle states
Dez 26 20:59:23 bolobi kernel: CPU3 is up
Dez 26 20:59:23 bolobi kernel: ACPI: Waking up from system sleep state S3
Dez 26 20:59:23 bolobi kernel: sd 0:0:0:0: [sda] Starting disk
Dez 26 20:59:23 bolobi kernel: sd 1:0:0:0: [sdb] Starting disk
Dez 26 20:59:23 bolobi kernel: sd 3:0:0:0: [sdd] Starting disk
Dez 26 20:59:23 bolobi kernel: sd 2:0:0:0: [sdc] Starting disk
Dez 26 20:59:23 bolobi kernel: usb 1-5: reset high-speed USB device number 2 using ehci-pci
Dez 26 20:59:23 bolobi kernel: usb 4-3: reset full-speed USB device number 2 using ohci-pci
Dez 26 20:59:23 bolobi kernel: ata5: SATA link down (SStatus 0 SControl 300)
Dez 26 20:59:23 bolobi kernel: ata6: SATA link down (SStatus 0 SControl 300)
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: Wait for MC idle timedout !
Dez 26 20:59:23 bolobi kernel: [drm] PCIE GART of 1024M enabled (table at 0x00000000001D6000).
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: WB enabled
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000030000c00
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 6 use gpu addr 0x0000000030000c18
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000030000c1c
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000030000c04
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000030000c08
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000030000c0c
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000030000c10
Dez 26 20:59:23 bolobi kernel: [drm] ring test on 0 succeeded in 2 usecs
Dez 26 20:59:23 bolobi kernel: [drm] ring test on 3 succeeded in 4 usecs
Dez 26 20:59:23 bolobi kernel: [drm] ring test on 4 succeeded in 4 usecs
Dez 26 20:59:23 bolobi kernel: [drm] ring test on 5 succeeded in 2 usecs
Dez 26 20:59:23 bolobi kernel: [drm] UVD initialized successfully.
Dez 26 20:59:23 bolobi kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dez 26 20:59:23 bolobi kernel: ata1.00: configured for UDMA/133
Dez 26 20:59:23 bolobi kernel: [drm] ring test on 6 succeeded in 10 usecs
Dez 26 20:59:23 bolobi kernel: [drm] ring test on 7 succeeded in 3 usecs
Dez 26 20:59:23 bolobi kernel: [drm] VCE initialized successfully.
Dez 26 20:59:23 bolobi kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Dez 26 20:59:23 bolobi kernel: [drm] ib test on ring 3 succeeded in 0 usecs
Dez 26 20:59:23 bolobi kernel: [drm] ib test on ring 4 succeeded in 0 usecs
Dez 26 20:59:23 bolobi kernel: [drm] ib test on ring 5 succeeded
Dez 26 20:59:23 bolobi kernel: [drm] ib test on ring 6 succeeded
Dez 26 20:59:23 bolobi kernel: [drm] ib test on ring 7 succeeded
Dez 26 20:59:23 bolobi kernel: OOM killer enabled.
Dez 26 20:59:23 bolobi kernel: Restarting tasks ... done.
Dez 26 20:59:23 bolobi kernel: PM: suspend exit
Dez 26 20:59:23 bolobi systemd-sleep[3156]: System resumed.
Dez 26 20:59:23 bolobi upowerd[1301]: treating change event as add on /sys/devices/pci0000:00/0000:00:13.0/usb4/4-3
Dez 26 20:59:23 bolobi upowerd[1301]: treating change event as add on /sys/devices/pci0000:00/0000:00:13.0/usb4/4-3
Dez 26 20:59:23 bolobi systemd[1]: systemd-suspend.service: Succeeded.
Dez 26 20:59:23 bolobi systemd[1]: Finished Suspend.
Dez 26 20:59:23 bolobi systemd[1]: Stopped target Sleep.
Dez 26 20:59:23 bolobi systemd[1]: Reached target Suspend.
Dez 26 20:59:23 bolobi systemd[1]: Stopped target Suspend.
Dez 26 20:59:23 bolobi systemd-logind[603]: Operation 'sleep' finished.

automatically timed triggered suspend

Dez 26 20:43:07 bolobi systemd-sleep[394470]: Suspending system...
Dez 26 20:43:07 bolobi kernel: PM: suspend entry (deep)
Dez 26 20:43:07 bolobi kernel: Filesystems sync: 0.061 seconds
Dez 26 20:43:08 bolobi lightdm[394619]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=969) by (uid=0)
Dez 26 20:43:08 bolobi systemd[1]: Created slice User Slice of UID 969.
Dez 26 20:43:08 bolobi systemd[1]: Starting User Runtime Directory /run/user/969...
Dez 26 20:43:08 bolobi systemd-logind[572]: New session c2 of user lightdm.
Dez 26 20:43:08 bolobi systemd[1]: Finished User Runtime Directory /run/user/969.
Dez 26 20:43:08 bolobi systemd[1]: Starting User Manager for UID 969...
Dez 26 20:43:08 bolobi dbus-daemon[564]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.402' (uid=0 pid=394624 comm="(systemd) ")
Dez 26 20:43:08 bolobi dbus-daemon[564]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Dez 26 20:43:08 bolobi systemd[394624]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Dez 26 20:43:08 bolobi systemd[394624]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[lightdm] ruser=[<unknown>] rhost=[<unknown>]
Dez 26 20:43:08 bolobi systemd[394624]: pam_unix(systemd-user:session): session opened for user lightdm(uid=969) by (uid=0)
Dez 26 20:43:08 bolobi systemd[394624]: pam_env(systemd-user:session): deprecated reading of user environment enabled
Dez 26 20:43:09 bolobi systemd-xdg-autostart-generator[394633]: Configuration file /etc/xdg/autostart/msm_notifier.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Dez 26 20:43:09 bolobi systemd[394624]: Queued start job for default target Main User Target.
Dez 26 20:43:09 bolobi systemd[394624]: -.slice: Failed to migrate controller cgroups from /user.slice/user-969.slice/user@969.service, ignoring: Permission denied
Dez 26 20:43:09 bolobi systemd[394624]: Created slice User Application Slice.
Dez 26 20:43:09 bolobi systemd[394624]: Reached target Paths.
Dez 26 20:43:09 bolobi systemd[394624]: Reached target Timers.
Dez 26 20:43:09 bolobi systemd[394624]: Starting D-Bus User Message Bus Socket.
Dez 26 20:43:09 bolobi systemd[394624]: Listening on GnuPG network certificate management daemon.
Dez 26 20:43:09 bolobi systemd[394624]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dez 26 20:43:09 bolobi systemd[394624]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Dez 26 20:43:09 bolobi systemd[394624]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dez 26 20:43:09 bolobi systemd[394624]: Listening on GnuPG cryptographic agent and passphrase cache.
Dez 26 20:43:09 bolobi systemd[394624]: Listening on p11-kit server.
Dez 26 20:43:09 bolobi systemd[394624]: Listening on Multimedia System.
Dez 26 20:43:09 bolobi systemd[394624]: Listening on Sound System.
Dez 26 20:43:09 bolobi systemd[394624]: Listening on D-Bus User Message Bus Socket.
Dez 26 20:43:09 bolobi systemd[394624]: Reached target Sockets.
Dez 26 20:43:09 bolobi systemd[394624]: Reached target Basic System.
Dez 26 20:43:09 bolobi systemd[1]: Started User Manager for UID 969.
Dez 26 20:43:09 bolobi systemd[1]: Started Session c2 of user lightdm.
Dez 26 20:43:09 bolobi systemd[394624]: Starting Update XDG user dir configuration...
Dez 26 20:43:09 bolobi systemd[394624]: xdg-user-dirs-update.service: Succeeded.
Dez 26 20:43:09 bolobi systemd[394624]: Finished Update XDG user dir configuration.
Dez 26 20:43:09 bolobi systemd[394624]: Reached target Main User Target.
Dez 26 20:43:09 bolobi systemd[394624]: Startup finished in 157ms.
Dez 26 20:43:09 bolobi systemd[394624]: Started D-Bus User Message Bus.
Dez 26 20:43:09 bolobi dbus-daemon[394639]: [session uid=969 pid=394639] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=969 pid=394637 comm="/usr/bin/lightdm-gtk-greeter ")
Dez 26 20:43:09 bolobi systemd[394624]: Starting Accessibility services bus...
Dez 26 20:43:09 bolobi dbus-daemon[394639]: [session uid=969 pid=394639] Successfully activated service 'org.a11y.Bus'
Dez 26 20:43:09 bolobi systemd[394624]: Started Accessibility services bus.
Dez 26 20:43:09 bolobi dbus-daemon[394639]: [session uid=969 pid=394639] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=969 pid=394637 comm="/usr/bin/lightdm-gtk-greeter ")
Dez 26 20:43:09 bolobi systemd[394624]: Starting Virtual filesystem service...
Dez 26 20:43:09 bolobi dbus-daemon[394639]: [session uid=969 pid=394639] Successfully activated service 'org.gtk.vfs.Daemon'
Dez 26 20:43:09 bolobi systemd[394624]: Started Virtual filesystem service.
Dez 26 20:43:09 bolobi polkitd[568]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Dez 26 20:43:09 bolobi polkitd[568]: <no filename>:4: subject=[Subject pid=394637 user='lightdm' groups=lightdm seat='seat0' session='c2' local=true active=true]
Dez 26 20:43:09 bolobi polkitd[568]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Dez 26 20:43:09 bolobi polkitd[568]: <no filename>:4: subject=[Subject pid=394637 user='lightdm' groups=lightdm seat='seat0' session='c2' local=true active=true]
Dez 26 20:43:09 bolobi polkitd[568]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Dez 26 20:43:09 bolobi polkitd[568]: <no filename>:4: subject=[Subject pid=394637 user='lightdm' groups=lightdm seat='seat0' session='c2' local=true active=true]
Dez 26 20:43:09 bolobi at-spi-bus-launcher[394646]: dbus-daemon[394646]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=969 pid=394637 comm="/usr/bin/lightdm-gtk-greeter ")
Dez 26 20:43:09 bolobi at-spi-bus-launcher[394646]: dbus-daemon[394646]: Successfully activated service 'org.a11y.atspi.Registry'
Dez 26 20:43:09 bolobi at-spi-bus-launcher[394668]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Dez 26 20:43:17 bolobi systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Dez 26 20:43:51 bolobi nmbd[753]: [2020/12/26 20:43:51.291054,  0] ../../source3/nmbd/nmbd.c:359(reload_interfaces)
Dez 26 20:43:51 bolobi nmbd[753]:   reload_interfaces: No subnets to listen to. Waiting..
Dez 26 20:45:01 bolobi crond[394754]: pam_unix(crond:session): session opened for user henuk(uid=1000) by (uid=0)
Dez 26 20:45:01 bolobi CROND[394759]: (henuk) CMD (/usr/bin/nice -n19 /usr/bin/ionice -c2 -n7 /usr/bin/backintime backup-job >/dev/null)
Dez 26 20:45:01 bolobi crond[394761]: sendmail: /home/henuk/.msmtprc: enthält Passwörter und darf daher Lese-/Schreibrecht nur für den Eigentümer haben
Dez 26 20:45:01 bolobi CROND[394754]: (henuk) MAIL (mailed 99 bytes of output but got status 0x004e
                                      )
Dez 26 20:45:01 bolobi CROND[394754]: pam_unix(crond:session): session closed for user henuk
Dez 26 20:49:54 bolobi lightdm[394666]: gkr-pam: unable to locate daemon control file
Dez 26 20:49:54 bolobi lightdm[394666]: gkr-pam: stashed password to try later in open session
Dez 26 20:49:54 bolobi dbus-daemon[564]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.405' (uid=0 pid=394666 comm="lightdm --session-child 13 22 ")
Dez 26 20:49:54 bolobi dbus-daemon[564]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Dez 26 20:49:54 bolobi lightdm[394666]: pam_systemd_home(lightdm:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Dez 26 20:49:55 bolobi systemd[1]: Stopping Session c2 of user lightdm.
Dez 26 20:49:55 bolobi lightdm[394619]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Dez 26 20:49:55 bolobi systemd[1]: session-c2.scope: Succeeded.
Dez 26 20:49:55 bolobi systemd[1]: Stopped Session c2 of user lightdm.
Dez 26 20:49:55 bolobi systemd-logind[572]: Removed session c2.
Dez 26 20:50:05 bolobi systemd[1]: Stopping User Manager for UID 969...
Dez 26 20:50:05 bolobi systemd[394624]: Stopped target Main User Target.
Dez 26 20:50:05 bolobi gvfsd[394648]: A connection to the bus can't be made
Dez 26 20:50:05 bolobi systemd[394624]: Stopping Accessibility services bus...
Dez 26 20:50:05 bolobi systemd[394624]: Stopping D-Bus User Message Bus...
Dez 26 20:50:05 bolobi systemd[394624]: Stopping Virtual filesystem service...
Dez 26 20:50:05 bolobi systemd[394624]: dbus.service: Succeeded.
Dez 26 20:50:05 bolobi systemd[394624]: Stopped D-Bus User Message Bus.
Dez 26 20:50:05 bolobi systemd[394624]: at-spi-dbus-bus.service: Main process exited, code=exited, status=1/FAILURE
Dez 26 20:50:05 bolobi at-spi-bus-launcher[394640]: Failed to launch bus: Bus exited with code 0
Dez 26 20:50:05 bolobi systemd[394624]: at-spi-dbus-bus.service: Failed with result 'exit-code'.
Dez 26 20:50:05 bolobi systemd[394624]: Stopped Accessibility services bus.
Dez 26 20:50:05 bolobi systemd[992]: run-user-969-gvfs.mount: Succeeded.
Dez 26 20:50:05 bolobi systemd[1]: run-user-969-gvfs.mount: Succeeded.
Dez 26 20:50:05 bolobi systemd[394624]: run-user-969-gvfs.mount: Succeeded.
Dez 26 20:50:05 bolobi systemd[394624]: gvfs-daemon.service: Succeeded.
Dez 26 20:50:05 bolobi systemd[394624]: Stopped Virtual filesystem service.
Dez 26 20:50:05 bolobi systemd[394624]: Stopped target Basic System.
Dez 26 20:50:05 bolobi systemd[394624]: Stopped target Paths.
Dez 26 20:50:05 bolobi systemd[394624]: Stopped target Sockets.
Dez 26 20:50:05 bolobi systemd[394624]: Stopped target Timers.
Dez 26 20:50:05 bolobi systemd[394624]: dbus.socket: Succeeded.
Dez 26 20:50:05 bolobi systemd[394624]: Closed D-Bus User Message Bus Socket.
Dez 26 20:50:05 bolobi systemd[394624]: dirmngr.socket: Succeeded.
Dez 26 20:50:05 bolobi systemd[394624]: Closed GnuPG network certificate management daemon.
Dez 26 20:50:05 bolobi systemd[394624]: gpg-agent-browser.socket: Succeeded.
Dez 26 20:50:05 bolobi systemd[394624]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dez 26 20:50:05 bolobi systemd[394624]: gpg-agent-extra.socket: Succeeded.
Dez 26 20:50:05 bolobi systemd[394624]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Dez 26 20:50:05 bolobi systemd[394624]: gpg-agent-ssh.socket: Succeeded.
Dez 26 20:50:05 bolobi systemd[394624]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Dez 26 20:50:05 bolobi systemd[394624]: gpg-agent.socket: Succeeded.
Dez 26 20:50:05 bolobi systemd[394624]: Closed GnuPG cryptographic agent and passphrase cache.
Dez 26 20:50:05 bolobi systemd[394624]: p11-kit-server.socket: Succeeded.
Dez 26 20:50:05 bolobi systemd[394624]: Closed p11-kit server.
Dez 26 20:50:05 bolobi systemd[394624]: pipewire.socket: Succeeded.
Dez 26 20:50:05 bolobi systemd[394624]: Closed Multimedia System.
Dez 26 20:50:05 bolobi systemd[394624]: pulseaudio.socket: Succeeded.
Dez 26 20:50:05 bolobi systemd[394624]: Closed Sound System.
Dez 26 20:50:05 bolobi systemd[394624]: Removed slice User Application Slice.
Dez 26 20:50:05 bolobi systemd[394624]: Reached target Shutdown.
Dez 26 20:50:05 bolobi systemd[394624]: systemd-exit.service: Succeeded.
Dez 26 20:50:05 bolobi systemd[394624]: Finished Exit the Session.
Dez 26 20:50:05 bolobi systemd[394624]: Reached target Exit the Session.
Dez 26 20:50:05 bolobi systemd[394628]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[lightdm] ruser=[<unknown>] rhost=[<unknown>]
Dez 26 20:50:05 bolobi systemd[1]: user@969.service: Succeeded.
Dez 26 20:50:05 bolobi systemd[1]: Stopped User Manager for UID 969.
Dez 26 20:50:05 bolobi systemd[1]: Stopping User Runtime Directory /run/user/969...
Dez 26 20:50:05 bolobi systemd[992]: run-user-969.mount: Succeeded.
Dez 26 20:50:05 bolobi systemd[1]: run-user-969.mount: Succeeded.
Dez 26 20:50:05 bolobi systemd[1]: user-runtime-dir@969.service: Succeeded.
Dez 26 20:50:05 bolobi systemd[1]: Stopped User Runtime Directory /run/user/969.
Dez 26 20:50:05 bolobi systemd[1]: Removed slice User Slice of UID 969.

It seems it just skip this part somehow:

skipped part

Dez 26 20:59:23 bolobi kernel: Freezing user space processes ... (elapsed 0.003 seconds) done.
Dez 26 20:59:23 bolobi kernel: OOM killer disabled.
Dez 26 20:59:23 bolobi kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Dez 26 20:59:23 bolobi kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dez 26 20:59:23 bolobi kernel: sd 3:0:0:0: [sdd] Synchronizing SCSI cache
Dez 26 20:59:23 bolobi kernel: sd 3:0:0:0: [sdd] Stopping disk
Dez 26 20:59:23 bolobi kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Dez 26 20:59:23 bolobi kernel: sd 1:0:0:0: [sdb] Stopping disk
Dez 26 20:59:23 bolobi kernel: sd 2:0:0:0: [sdc] Synchronizing SCSI cache
Dez 26 20:59:23 bolobi kernel: sd 2:0:0:0: [sdc] Stopping disk
Dez 26 20:59:23 bolobi kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Dez 26 20:59:23 bolobi kernel: sd 0:0:0:0: [sda] Stopping disk
Dez 26 20:59:23 bolobi kernel: ACPI: Preparing to enter system sleep state S3
Dez 26 20:59:23 bolobi kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Dez 26 20:59:23 bolobi kernel: PM: Saving platform NVS memory
Dez 26 20:59:23 bolobi kernel: Disabling non-boot CPUs ...
Dez 26 20:59:23 bolobi kernel: smpboot: CPU 1 is now offline
Dez 26 20:59:23 bolobi kernel: smpboot: CPU 2 is now offline
Dez 26 20:59:23 bolobi kernel: smpboot: CPU 3 is now offline
Dez 26 20:59:23 bolobi kernel: ACPI: Low-level resume complete
Dez 26 20:59:23 bolobi kernel: PM: Restoring platform NVS memory
Dez 26 20:59:23 bolobi kernel: LVT offset 0 assigned for vector 0x400
Dez 26 20:59:23 bolobi kernel: Enabling non-boot CPUs ...
Dez 26 20:59:23 bolobi kernel: x86: Booting SMP configuration:
Dez 26 20:59:23 bolobi kernel: smpboot: Booting Node 0 Processor 1 APIC 0x11
Dez 26 20:59:23 bolobi kernel: microcode: CPU1: patch_level=0x06001119
Dez 26 20:59:23 bolobi kernel: ACPI: \_PR_.P001: Found 2 idle states
Dez 26 20:59:23 bolobi kernel: CPU1 is up
Dez 26 20:59:23 bolobi kernel: smpboot: Booting Node 0 Processor 2 APIC 0x12
Dez 26 20:59:23 bolobi kernel: microcode: CPU2: patch_level=0x06001119
Dez 26 20:59:23 bolobi kernel: ACPI: \_PR_.P002: Found 2 idle states
Dez 26 20:59:23 bolobi kernel: CPU2 is up
Dez 26 20:59:23 bolobi kernel: smpboot: Booting Node 0 Processor 3 APIC 0x13
Dez 26 20:59:23 bolobi kernel: microcode: CPU3: patch_level=0x06001119
Dez 26 20:59:23 bolobi kernel: ACPI: \_PR_.P003: Found 2 idle states
Dez 26 20:59:23 bolobi kernel: CPU3 is up
Dez 26 20:59:23 bolobi kernel: ACPI: Waking up from system sleep state S3
Dez 26 20:59:23 bolobi kernel: sd 0:0:0:0: [sda] Starting disk
Dez 26 20:59:23 bolobi kernel: sd 1:0:0:0: [sdb] Starting disk
Dez 26 20:59:23 bolobi kernel: sd 3:0:0:0: [sdd] Starting disk
Dez 26 20:59:23 bolobi kernel: sd 2:0:0:0: [sdc] Starting disk
Dez 26 20:59:23 bolobi kernel: usb 1-5: reset high-speed USB device number 2 using ehci-pci
Dez 26 20:59:23 bolobi kernel: usb 4-3: reset full-speed USB device number 2 using ohci-pci
Dez 26 20:59:23 bolobi kernel: ata5: SATA link down (SStatus 0 SControl 300)
Dez 26 20:59:23 bolobi kernel: ata6: SATA link down (SStatus 0 SControl 300)
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: Wait for MC idle timedout !
Dez 26 20:59:23 bolobi kernel: [drm] PCIE GART of 1024M enabled (table at 0x00000000001D6000).
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: WB enabled
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000030000c00
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 6 use gpu addr 0x0000000030000c18
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000030000c1c
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000030000c04
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000030000c08
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000030000c0c
Dez 26 20:59:23 bolobi kernel: radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000030000c10
Dez 26 20:59:23 bolobi kernel: [drm] ring test on 0 succeeded in 2 usecs
Dez 26 20:59:23 bolobi kernel: [drm] ring test on 3 succeeded in 4 usecs
Dez 26 20:59:23 bolobi kernel: [drm] ring test on 4 succeeded in 4 usecs
Dez 26 20:59:23 bolobi kernel: [drm] ring test on 5 succeeded in 2 usecs
Dez 26 20:59:23 bolobi kernel: [drm] UVD initialized successfully.
Dez 26 20:59:23 bolobi kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dez 26 20:59:23 bolobi kernel: ata1.00: configured for UDMA/133
Dez 26 20:59:23 bolobi kernel: [drm] ring test on 6 succeeded in 10 usecs
Dez 26 20:59:23 bolobi kernel: [drm] ring test on 7 succeeded in 3 usecs
Dez 26 20:59:23 bolobi kernel: [drm] VCE initialized successfully.
Dez 26 20:59:23 bolobi kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Dez 26 20:59:23 bolobi kernel: [drm] ib test on ring 3 succeeded in 0 usecs
Dez 26 20:59:23 bolobi kernel: [drm] ib test on ring 4 succeeded in 0 usecs
Dez 26 20:59:23 bolobi kernel: [drm] ib test on ring 5 succeeded
Dez 26 20:59:23 bolobi kernel: [drm] ib test on ring 6 succeeded
Dez 26 20:59:23 bolobi kernel: [drm] ib test on ring 7 succeeded
Dez 26 20:59:23 bolobi kernel: OOM killer enabled.
Dez 26 20:59:23 bolobi kernel: Restarting tasks ... done.
Dez 26 20:59:23 bolobi kernel: PM: suspend exit
Dez 26 20:59:23 bolobi systemd-sleep[3156]: System resumed.
Dez 26 20:59:23 bolobi upowerd[1301]: treating change event as add on /sys/devices/pci0000:00/0000:00:13.0/usb4/4-3
Dez 26 20:59:23 bolobi upowerd[1301]: treating change event as add on /sys/devices/pci0000:00/0000:00:13.0/usb4/4-3
Dez 26 20:59:23 bolobi systemd[1]: systemd-suspend.service: Succeeded.
Dez 26 20:59:23 bolobi systemd[1]: Finished Suspend.
Dez 26 20:59:23 bolobi systemd[1]: Stopped target Sleep.
Dez 26 20:59:23 bolobi systemd[1]: Reached target Suspend.
Dez 26 20:59:23 bolobi systemd[1]: Stopped target Suspend.
Dez 26 20:59:23 bolobi systemd-logind[603]: Operation 'sleep' finished.
Dez 26 20:59:23 bolobi ModemManager[656]: <info>  [sleep-monitor] system is resuming
Dez 26 20:59:23 bolobi NetworkManager[598]: <info>  [1609012763.7897] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Dez 26 20:59:23 bolobi NetworkManager[598]: <info>  [1609012763.7898] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Dez 26 20:59:23 bolobi kernel: RTL8211E Gigabit Ethernet r8169-400:00: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=r8169-400:00, irq=IGNORE)
Dez 26 20:59:24 bolobi kernel: r8169 0000:04:00.0 enp4s0: Link is Down
Dez 26 20:59:24 bolobi NetworkManager[598]: <info>  [1609012764.0149] manager: NetworkManager state is now DISCONNECTED
Dez 26 20:59:24 bolobi kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dez 26 20:59:24 bolobi kernel: ata2.00: configured for UDMA/100
Dez 26 20:59:25 bolobi kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dez 26 20:59:25 bolobi kernel: ata4.00: configured for UDMA/133
Dez 26 20:59:25 bolobi kernel: r8169 0000:04:00.0 enp4s0: Link is Up - 100Mbps/Full - flow control rx/tx
Dez 26 20:59:25 bolobi kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
Dez 26 20:59:25 bolobi NetworkManager[598]: <info>  [1609012765.4972] device (enp4s0): carrier: link connected
Dez 26 20:59:25 bolobi NetworkManager[598]: <info>  [1609012765.4975] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Dez 26 20:59:25 bolobi NetworkManager[598]: <info>  [1609012765.4988] policy: auto-activating connection 'Auto-Ethernet' (bc2e9289-03a2-4704-bd5f-a9460b749d4f)
Dez 26 20:59:25 bolobi NetworkManager[598]: <info>  [1609012765.4996] device (enp4s0): Activation: starting connection 'Auto-Ethernet' (bc2e9289-03a2-4704-bd5f-a9460b749d4f)
Dez 26 20:59:25 bolobi NetworkManager[598]: <info>  [1609012765.4999] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dez 26 20:59:25 bolobi NetworkManager[598]: <info>  [1609012765.5004] manager: NetworkManager state is now CONNECTING
Dez 26 20:59:25 bolobi NetworkManager[598]: <info>  [1609012765.5007] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dez 26 20:59:25 bolobi NetworkManager[598]: <info>  [1609012765.5012] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Dez 26 20:59:25 bolobi NetworkManager[598]: <info>  [1609012765.5015] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Dez 26 20:59:25 bolobi avahi-daemon[595]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::fcea:2b72:bf79:7693.
Dez 26 20:59:25 bolobi avahi-daemon[595]: New relevant interface enp4s0.IPv6 for mDNS.
Dez 26 20:59:25 bolobi avahi-daemon[595]: Registering new address record for fe80::fcea:2b72:bf79:7693 on enp4s0.*.
Dez 26 20:59:25 bolobi kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dez 26 20:59:25 bolobi kernel: ata3.00: configured for UDMA/133
Dez 26 20:59:26 bolobi ModemManager[656]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:15.2/0000:04:00.0': not supported by any plugin

Myself i am out of ideas for now. It seems that the timed suspend triggers another mode, maybe the software suspend, instead of the hardware suspend, which triggers the ACPI. The software mode just emulates it.

krill · 27 December 2020 09:45

Mod-edit: Formatting
Please use shorter sentences and start a new line after a sentence ends, thank you.

@megavolt Hi again, cheers for the feedback!

I recalled something I did initially when I got the machine in an attempt to not make the LEDs on the RAM continue their lightshow when the machine was suspended.
It failed but the setting remained, which on Gigabyte’s boards is called “ERP”.
If enabled it lets the machine attempt to consume less power in standby as I understand it.
Anyway I disabled it and now either setting under the Light lock tab works:

“To lock the screen - When the screensaver is activated”

I didn’t initially understand that XFCE meant that the default power save options under the Screen tab were the screensaver (since they aren’t employing a ‘screen saver’) but I can now logically see how that is the case), as well as “Lock screen when the system is going to sleep”.
(I haven’t tried both at the same time, let’s not tempt fate)

May be that your tower PC’s motherboard has a similar setting?

TriMoon · 27 December 2020 12:30

On my ASUS board (desktop) it is called “ERP ready”.
If the issue is related to that then i guess it has to do with power mode support of your motherboard, eg. APM in combination with your CPU and GPU.
Things like C(0->number) mode/support…

megavolt · 27 December 2020 18:10

I guess because we use an ASUS Board it has the same issue…

Machine:   Type: Desktop Mobo: ASUSTeK model: F2A55-M LK2 v: Rev X.0x serial: 131017451901936
           UEFI: American Megatrends v: 6308 date: 11/25/2014

I have mothing like this in my UEFI. It is called APM here? There i could set the S3 state.

Ok I exprienced something really weird. Ok have set suspend when idle to 15min in xfce settings. Was waiting the time. Nothing happend. Normally the Power LED would blinking and everything would be shutdown. But this was not the case.

Nothing different from the last test.

But now, i moved my mouse and unlock the screen after 20min. Network was freezed… i guess it tried to initiate a freeze and then shutdown to deep sleep. I triggered then shutdown or restart, idk which one exactly, but then it shutdown to deep sleep as it should.

I guess there is something that stops the sleep process…

But to be clear: If i manually trigger suspend, hibernation or hybrid with xfce (no terminal), it works as expected.