System needs two wake up calls to wake up once

Support
1

My system wakes up after a keypress and goes back to sleep after a few seconds (screen stays black). It only stays awake after the second wake up trigger. This does not happen all the time, one in three roughly the system stays awake after the first wake up call. I have searched the web but can not find similar behaviour.
It started to happen after I changed from a wifi connection to ethernet. I suspect NetworkManager is involved. But what to do?

Below I have copied output from

journalctl  --no-pager | grep -i "sleep\|suspend\|hibernate"

This is maybe insufficient information, I am happy to provide more on request.
Thanks for your support!

feb 24 19:21:34 manja systemd-logind[694]: Operation 'suspend' finished.
feb 24 19:21:34 manja NetworkManager[686]: <info>  [1740421294.1590] manager: sleep: wake requested (sleeping: yes  enabled: yes)
feb 24 19:21:34 manja NetworkManager[686]: <info>  [1740421294.1591] device (eno1): state change: activated -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
feb 24 19:23:27 manja ddcutil[43770]: dh=Display_Handle[i2c-4: fd=3], Replacing adjusted sleep multiplier 0.00 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
feb 24 19:23:27 manja ddcutil[43770]: dh=Display_Handle[i2c-4: fd=3], Replacing adjusted sleep multiplier 0.00 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
feb 24 21:25:28 manja ddcutil[52616]: dh=Display_Handle[i2c-4: fd=3], Replacing adjusted sleep multiplier 0.00 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
feb 24 21:25:28 manja ddcutil[52616]: dh=Display_Handle[i2c-4: fd=3], Replacing adjusted sleep multiplier 0.00 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
feb 24 21:31:41 manja systemd-logind[694]: The system will suspend now!
feb 24 21:31:41 manja NetworkManager[686]: <info>  [1740429101.6806] manager: sleep: sleep requested (sleeping: no  enabled: yes)
feb 24 21:31:41 manja NetworkManager[686]: <info>  [1740429101.6806] manager: NetworkManager state is now ASLEEP
feb 24 21:31:41 manja systemd[1]: Reached target Sleep.
feb 24 21:31:41 manja systemd[1]: Starting System Suspend...
feb 24 21:31:41 manja systemd-sleep[53072]: Successfully froze unit 'user.slice'.
feb 24 21:31:41 manja systemd-sleep[53072]: Performing sleep operation 'suspend'...
feb 24 21:31:41 manja kernel: PM: suspend entry (deep)
feb 25 16:20:11 manja kernel: printk: Suspending console(s) (use no_console_suspend to debug)
feb 25 16:20:11 manja kernel: ACPI: PM: Preparing to enter system sleep state S3
feb 25 16:20:11 manja kernel: ACPI: PM: Waking up from system sleep state S3
feb 25 16:20:11 manja kernel: PM: suspend exit
feb 25 16:20:11 manja systemd-sleep[53072]: System returned from sleep operation 'suspend'.
feb 25 16:20:11 manja systemd-sleep[53072]: Successfully thawed unit 'user.slice'.
feb 25 16:20:11 manja systemd[1]: systemd-suspend.service: Deactivated successfully.
feb 25 16:20:11 manja systemd[1]: Finished System Suspend.
feb 25 16:20:11 manja systemd[1]: Stopped target Sleep.
feb 25 16:20:11 manja systemd[1]: Reached target Suspend.
feb 25 16:20:11 manja systemd-logind[694]: Operation 'suspend' finished.
feb 25 16:20:11 manja NetworkManager[686]: <info>  [1740496811.1727] manager: sleep: wake requested (sleeping: yes  enabled: yes)
feb 25 16:20:11 manja NetworkManager[686]: <info>  [1740496811.1745] device (eno1): state change: activated -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
feb 25 16:20:11 manja systemd[1]: Stopped target Suspend.
feb 25 16:20:11 manja systemd-logind[694]: The system will suspend now!
feb 25 16:20:11 manja archlinux-keyring-wkd-sync[53156]: Skipping key 91BD8815FE0040FA7FF5D68754C28F4FF5A1A949 with UID dave@sleepmap.de...
feb 25 16:20:11 manja NetworkManager[686]: <info>  [1740496811.5418] manager: sleep: sleep requested (sleeping: no  enabled: yes)
feb 25 16:20:11 manja NetworkManager[686]: <info>  [1740496811.5418] manager: NetworkManager state is now ASLEEP
feb 25 16:20:11 manja systemd[1]: Reached target Sleep.
feb 25 16:20:11 manja systemd[1]: Starting System Suspend...
feb 25 16:20:11 manja archlinux-keyring-wkd-sync[53156]: Skipping key 91BD8815FE0040FA7FF5D68754C28F4FF5A1A949 with UID dave@sleepmap.de...
feb 25 16:20:11 manja systemd-sleep[53232]: Successfully froze unit 'user.slice'.
feb 25 16:20:11 manja systemd-sleep[53232]: Performing sleep operation 'suspend'...
feb 25 16:20:11 manja kernel: PM: suspend entry (deep)
feb 25 16:20:29 manja kernel: printk: Suspending console(s) (use no_console_suspend to debug)
feb 25 16:20:29 manja kernel: ACPI: PM: Preparing to enter system sleep state S3
feb 25 16:20:29 manja kernel: ACPI: PM: Waking up from system sleep state S3
feb 25 16:20:29 manja kernel: PM: suspend exit
feb 25 16:20:29 manja systemd-sleep[53232]: System returned from sleep operation 'suspend'.
feb 25 16:20:29 manja systemd-sleep[53232]: Successfully thawed unit 'user.slice'.
feb 25 16:20:29 manja systemd[1]: systemd-suspend.service: Deactivated successfully.
feb 25 16:20:29 manja systemd[1]: Finished System Suspend.
feb 25 16:20:29 manja systemd[1]: Stopped target Sleep.
feb 25 16:20:29 manja systemd[1]: Reached target Suspend.
feb 25 16:20:29 manja systemd-logind[694]: Operation 'suspend' finished.
feb 25 16:20:29 manja systemd[1]: Stopped target Suspend.
feb 25 16:20:29 manja NetworkManager[686]: <info>  [1740496829.0996] manager: sleep: wake requested (sleeping: yes  enabled: yes)
feb 25 16:20:29 manja NetworkManager[686]: <info>  [1740496829.0996] device (eno1): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
feb 25 16:21:05 manja ddcutil[53575]: dh=Display_Handle[i2c-4: fd=3], Replacing adjusted sleep multiplier 0.00 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
feb 25 16:21:05 manja ddcutil[53575]: dh=Display_Handle[i2c-4: fd=3], Replacing adjusted sleep multiplier 0.00 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
2

Whilst I might not be specifically able to help here, the output of inxi -zv8 is often useful (and this or similar will usually be asked for in Support threads).

This gives some (privacy-filtered) information about your system.

4

thanks, see below

System:
  Kernel: 6.6.75-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=adcda0b2-d3e3-4d08-a9bd-802191d2faf3 ro nowatchdog quiet
    apparmor=1 security=apparmor udev.log_priority=3
  Desktop: KDE Plasma v: 6.2.5 tk: Qt v: N/A info: frameworks v: 6.10.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B360M-C v: Rev X.0x
    serial: <superuser required> part-nu: ASUS_MB_CNL uuid: <superuser required>
    UEFI: American Megatrends v: 3202 date: 07/10/2021
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 16 GiB available: 15.06 GiB used: 4.15 GiB (27.6%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 4 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: ChannelA-DIMM1 type: no module installed
  Device-2: ChannelA-DIMM2 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2400 MT/s volts: curr: 1 width (bits): data: 64 total: 64
    manufacturer: Crucial part-no: CT8G4DFS824A.C8FDD1 serial: <filter>
  Device-3: ChannelB-DIMM1 type: no module installed
  Device-4: ChannelB-DIMM2 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2400 MT/s volts: curr: 1 width (bits): data: 64 total: 64
    manufacturer: Micron part-no: 8ATF1G64AZ-2G3E1 serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i5-9500 bits: 64 type: MCP arch: Coffee Lake
    gen: core 9 level: v3 note: check built: 2018 process: Intel 14nm family: 6
    model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xF8
  Topology: cpus: 1x dies: 1 clusters: 6 cores: 6 smt: <unsupported> cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 9 MiB desc: 1x9 MiB
  Speed (MHz): avg: 4197 min/max: 800/4400 scaling: driver: intel_pstate
    governor: performance cores: 1: 4197 2: 4197 3: 4197 4: 4197 5: 4197 6: 4197
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.5
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: DP-1 model: Dell P2415Q  GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.303 layers: 4 device: 0 type: integrated-gpu name: Intel
    UHD Graphics 630 (CFL GT2) driver: N/A device-ID: 8086:3e92
    surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: BEHRINGER GmbH UMC202HD 192k driver: snd-usb-audio type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:3 chip-ID: 1397:0507
    class-ID: fe01
  API: ALSA v: k6.6.75-2-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
    status: active 2: pipewire-media-session status: active 3: pipewire-alsa
    type: plugin 4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bc class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager,systemd-timesyncd
  WAN IP: <filter>
5

Not really surprising, but it looks like the system wakes up and then another suspend is called through systemd-logind. I don’t know how Network Manager could do that.

The grep could obscure details, check without the grep to see if anything useful has been missed out.

The only thing I can think of atm:

Do you have a systemd timer putting the device to sleep?

If so, and it misses one or more runs…then it will run once as soon as the device wakes up.

When a system is temporarily put to sleep (i.e. system suspend or hibernation) the realtime clock does not pause. When a calendar timer elapses while the system is sleeping it will not be acted on immediately, but once the system is later resumed it will catch up and process all timers that triggered while the system was sleeping. Note that if a calendar timer elapsed more than once while the system was continuously sleeping the timer will only result in a single service activation.

https://man.archlinux.org/man/systemd.timer.5

If that’s the case then the service (or a script the service runs) can check the journal for when the system woke up and only suspend if a certain amount of time has elapsed, 60s should do the job.

6

I do not have a systemd timer (I think). Below I have copied the same log file without grep. I have added empty lines after a line related to this issue (?), but I could very well be wrong. I still do not now what creates this strange cycle of Resume followed by Suspend.

Please have a look at this:

feb 24 21:31:41 manja kernel: PM: suspend entry (deep)
feb 24 21:31:41 manja kernel: Filesystems sync: 0.010 seconds


feb 25 16:20:11 manja kernel: Freezing user space processes
feb 25 16:20:11 manja kernel: Freezing user space processes completed (elapsed 0.001 seconds)
feb 25 16:20:11 manja kernel: OOM killer disabled.
feb 25 16:20:11 manja kernel: Freezing remaining freezable tasks
feb 25 16:20:11 manja kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
feb 25 16:20:11 manja kernel: printk: Suspending console(s) (use no_console_suspend to debug)
feb 25 16:20:11 manja kernel: e1000e: EEE TX LPI TIMER: 00000011
feb 25 16:20:11 manja kernel: sd 4:0:0:0: [sda] Synchronizing SCSI cache
feb 25 16:20:11 manja kernel: ata5.00: Entering standby power mode
feb 25 16:20:11 manja kernel: ACPI: PM: Preparing to enter system sleep state S3
feb 25 16:20:11 manja kernel: ACPI: PM: Saving platform NVS memory
feb 25 16:20:11 manja kernel: Disabling non-boot CPUs ...
feb 25 16:20:11 manja kernel: smpboot: CPU 1 is now offline
feb 25 16:20:11 manja kernel: smpboot: CPU 2 is now offline
feb 25 16:20:11 manja kernel: smpboot: CPU 3 is now offline
feb 25 16:20:11 manja kernel: smpboot: CPU 4 is now offline
feb 25 16:20:11 manja kernel: smpboot: CPU 5 is now offline
feb 25 16:20:11 manja kernel: ACPI: PM: Low-level resume complete
feb 25 16:20:11 manja kernel: ACPI: PM: Restoring platform NVS memory
feb 25 16:20:11 manja kernel: Enabling non-boot CPUs ...
feb 25 16:20:11 manja kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
feb 25 16:20:11 manja kernel: CPU1 is up
feb 25 16:20:11 manja kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
feb 25 16:20:11 manja kernel: CPU2 is up
feb 25 16:20:11 manja kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
feb 25 16:20:11 manja kernel: CPU3 is up
feb 25 16:20:11 manja kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
feb 25 16:20:11 manja kernel: CPU4 is up
feb 25 16:20:11 manja kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
feb 25 16:20:11 manja kernel: CPU5 is up


feb 25 16:20:11 manja kernel: ACPI: PM: Waking up from system sleep state S3
feb 25 16:20:11 manja kernel: i915 0000:00:02.0: [drm] [ENCODER:94:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
feb 25 16:20:11 manja kernel: i915 0000:00:02.0: [drm] [ENCODER:111:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it
feb 25 16:20:11 manja kernel: i915 0000:00:02.0: [drm] [ENCODER:121:DDI D/PHY D] is disabled/in DSI mode with an ungated DDI clock, gate it
feb 25 16:20:11 manja kernel: i915 0000:00:02.0: [drm] [ENCODER:125:DDI E/PHY E] is disabled/in DSI mode with an ungated DDI clock, gate it
feb 25 16:20:11 manja kernel: nvme nvme0: Shutdown timeout set to 8 seconds
feb 25 16:20:11 manja kernel: nvme nvme0: 6/0/0 default/read/poll queues
feb 25 16:20:11 manja kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
feb 25 16:20:11 manja kernel: nvme nvme1: 6/0/0 default/read/poll queues
feb 25 16:20:11 manja kernel: ata6: SATA link down (SStatus 4 SControl 300)
feb 25 16:20:11 manja kernel: ata4: SATA link down (SStatus 0 SControl 300)
feb 25 16:20:11 manja kernel: ata2: SATA link down (SStatus 4 SControl 300)
feb 25 16:20:11 manja kernel: ata3: SATA link down (SStatus 0 SControl 300)
feb 25 16:20:11 manja kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
feb 25 16:20:11 manja kernel: pci_bus 0000:04: Allocating resources
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: bridge window [io  0x1000-0x0fff] to [bus 04] add_size 1000
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 04] add_size 200000 add_align 100000
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: bridge window [mem 0x00100000-0x000fffff] to [bus 04] add_size 200000 add_align 100000
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: BAR 14: no space for [mem size 0x00200000]
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: BAR 14: failed to assign [mem size 0x00200000]
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: BAR 13: no space for [io  size 0x1000]
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: BAR 13: failed to assign [io  size 0x1000]
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: BAR 14: no space for [mem size 0x00200000]
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: BAR 14: failed to assign [mem size 0x00200000]
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: BAR 13: no space for [io  size 0x1000]
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: BAR 13: failed to assign [io  size 0x1000]
feb 25 16:20:11 manja kernel: pci 0000:03:00.0: PCI bridge to [bus 04]
feb 25 16:20:11 manja kernel: OOM killer enabled.
feb 25 16:20:11 manja kernel: Restarting tasks ... 
feb 25 16:20:11 manja kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
feb 25 16:20:11 manja kernel: done.
feb 25 16:20:11 manja kernel: random: crng reseeded on system resumption
feb 25 16:20:11 manja kernel: PM: suspend exit


feb 25 16:20:11 manja systemd-sleep[53072]: System returned from sleep operation 'suspend'.
feb 25 16:20:11 manja systemd[1]: Starting Network Manager Wait Online...
feb 25 16:20:11 manja systemd[1]: Starting Rotate log files...
feb 25 16:20:11 manja systemd[1]: Starting Daily man-db regeneration...
feb 25 16:20:11 manja systemd[1]: Started Verify integrity of password and group files.
feb 25 16:20:11 manja systemd[1]: session-1.scope: Unit now thawed.
feb 25 16:20:11 manja systemd[1]: user.slice: Unit now thawed.
feb 25 16:20:11 manja systemd[1]: user-1000.slice: Unit now thawed.
feb 25 16:20:11 manja systemd[1]: user@1000.service: Unit now thawed.
feb 25 16:20:11 manja systemd-sleep[53072]: Successfully thawed unit 'user.slice'.
feb 25 16:20:11 manja systemd[1]: systemd-suspend.service: Deactivated successfully.
feb 25 16:20:11 manja systemd[1]: Finished System Suspend.
feb 25 16:20:11 manja systemd[1]: Finished Network Manager Wait Online.
feb 25 16:20:11 manja systemd[1]: Reached target Network is Online.
feb 25 16:20:11 manja systemd[1]: Stopped target Sleep.
feb 25 16:20:11 manja systemd[1]: Reached target Suspend.
feb 25 16:20:11 manja systemd-logind[694]: Operation 'suspend' finished.


feb 25 16:20:11 manja NetworkManager[686]: <info>  [1740496811.1727] manager: sleep: wake requested (sleeping: yes  enabled: yes)
feb 25 16:20:11 manja NetworkManager[686]: <info>  [1740496811.1745] device (eno1): state change: activated -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
feb 25 16:20:11 manja avahi-daemon[688]: Withdrawing address record for 192.168.2.38 on eno1.
feb 25 16:20:11 manja NetworkManager[686]: <info>  [1740496811.1747] dhcp4 (eno1): canceled DHCP transaction
feb 25 16:20:11 manja avahi-daemon[688]: Leaving mDNS multicast group on interface eno1.IPv4 with address 192.168.2.38.
feb 25 16:20:11 manja NetworkManager[686]: <info>  [1740496811.1747] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
feb 25 16:20:11 manja avahi-daemon[688]: Interface eno1.IPv4 no longer relevant for mDNS.
feb 25 16:20:11 manja NetworkManager[686]: <info>  [1740496811.1747] dhcp4 (eno1): state changed no lease
feb 25 16:20:11 manja avahi-daemon[688]: Withdrawing address record for fd4c:4b32:3230:0:3e2e:c1f2:a3eb:24e1 on eno1.
feb 25 16:20:11 manja NetworkManager[686]: <info>  [1740496811.1748] dhcp6 (eno1): canceled DHCP transaction
feb 25 16:20:11 manja avahi-daemon[688]: Withdrawing address record for 2a02:a460:4647:0:bfe4:8d0b:5362:d089 on eno1.
feb 25 16:20:11 manja NetworkManager[686]: <info>  [1740496811.1748] dhcp6 (eno1): activation: beginning transaction (timeout in 45 seconds)
feb 25 16:20:11 manja avahi-daemon[688]: Leaving mDNS multicast group on interface eno1.IPv6 with address 2a02:a460:4647:0:bfe4:8d0b:5362:d089.
feb 25 16:20:11 manja NetworkManager[686]: <info>  [1740496811.1748] dhcp6 (eno1): state changed no lease
feb 25 16:20:11 manja avahi-daemon[688]: Joining mDNS multicast group on interface eno1.IPv6 with address fe80::7fe:42a2:3949:d69.
feb 25 16:20:11 manja avahi-daemon[688]: Registering new address record for fe80::7fe:42a2:3949:d69 on eno1.*.
feb 25 16:20:11 manja avahi-daemon[688]: Withdrawing address record for fe80::7fe:42a2:3949:d69 on eno1.
feb 25 16:20:11 manja avahi-daemon[688]: Leaving mDNS multicast group on interface eno1.IPv6 with address fe80::7fe:42a2:3949:d69.
feb 25 16:20:11 manja avahi-daemon[688]: Interface eno1.IPv6 no longer relevant for mDNS.
feb 25 16:20:11 manja systemd[1]: Started Refresh existing keys of archlinux-keyring.
feb 25 16:20:11 manja systemd[1]: Stopped target Suspend.


feb 25 16:20:11 manja systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
feb 25 16:20:11 manja kdeconnectd[1269]: 2025-02-25T16:20:11 kdeconnect.core: No local bluetooth adapter found
feb 25 16:20:11 manja kdeconnectd[1269]: 2025-02-25T16:20:11 default: Error sending UDP packet: QAbstractSocket::NetworkError
feb 25 16:20:11 manja kdeconnectd[1269]: 2025-02-25T16:20:11 kdeconnect.core: Failed to open any MDNS server sockets
feb 25 16:20:11 manja systemd[1]: logrotate.service: Deactivated successfully.
feb 25 16:20:11 manja systemd[1]: Finished Rotate log files.
feb 25 16:20:11 manja systemd[1]: shadow.service: Deactivated successfully.
feb 25 16:20:11 manja NetworkManager[686]: <info>  [1740496811.2646] manager: NetworkManager state is now CONNECTED_GLOBAL
feb 25 16:20:11 manja kdeconnectd[1269]: 2025-02-25T16:20:11 default: Error sending UDP packet: QAbstractSocket::NetworkError
feb 25 16:20:11 manja systemd-logind[694]: The system will suspend now!
feb 25 16:20:11 manja kdeconnectd[1269]: 2025-02-25T16:20:11 kdeconnect.core: Failed to open any MDNS server sockets
feb 25 16:20:11 manja NetworkManager[686]: <info>  [1740496811.3471] manager: NetworkManager state is now DISCONNECTED


feb 25 16:20:11 manja kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Down
feb 25 16:20:11 manja NetworkManager[686]: <info>  [1740496811.3478] device (eno1): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
feb 25 16:20:11 manja systemd[1]: Starting Network Manager Script Dispatcher Service...
feb 25 16:20:11 manja archlinux-keyring-wkd-sync[53156]: Skipping key 22FB370AFFE7096627CCF9A8466D71A4D7FE33AA with UID pacman@localhost...
feb 25 16:20:11 manja archlinux-keyring-wkd-sync[53156]: Skipping key AB19265E5D7D20687D303246BA1DFB64FFF979E7 with UID allan@master-key.archlinux.org...
feb 25 16:20:11 manja archlinux-keyring-wkd-sync[53156]: Refreshing key D8AFDDA07A5B6EDFA7D8CCDAD6D055F927843F1C with UID anthraxx@master-key.archlinux.org...
feb 25 16:20:11 manja systemd[1]: Started GnuPG network certificate management daemon for /etc/pacman.d/gnupg.
feb 25 16:20:11 manja systemd[1]: Started Network Manager Script Dispatcher Service.
feb 25 16:20:11 manja dirmngr[53190]: permanently loaded certificates: 150
feb 25 16:20:11 manja dirmngr[53190]:     runtime cached certificates: 0
feb 25 16:20:11 manja dirmngr[53190]:            trusted certificates: 150 (150,0,0,0)
feb 25 16:20:11 manja dirmngr[53190]: number of system provided CAs: 175
feb 25 16:20:11 manja dirmngr[53190]: resolving 'master-key.archlinux.org' failed: Server indicated a failure


<manually removed ~ 1800 lines of skipping to sync keys gpg (probably because network is not up?)>


feb 25 16:20:12 manja kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
feb 25 16:20:12 manja kernel: ata5.00: Entering active power mode
feb 25 16:20:13 manja kernel: sd 4:0:0:0: [sda] Starting disk
feb 25 16:20:13 manja kernel: ata5.00: configured for UDMA/133
feb 25 16:20:29 manja kernel: Filesystems sync: 1.482 seconds
feb 25 16:20:29 manja kernel: Freezing user space processes
feb 25 16:20:29 manja kernel: Freezing user space processes completed (elapsed 0.001 seconds)
feb 25 16:20:29 manja kernel: OOM killer disabled.
feb 25 16:20:29 manja kernel: Freezing remaining freezable tasks
feb 25 16:20:29 manja kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
feb 25 16:20:29 manja kernel: printk: Suspending console(s) (use no_console_suspend to debug)
feb 25 16:20:29 manja kernel: e1000e: EEE TX LPI TIMER: 00000011
feb 25 16:20:29 manja kernel: sd 4:0:0:0: [sda] Synchronizing SCSI cache
feb 25 16:20:29 manja kernel: ata5.00: Entering standby power mode
feb 25 16:20:29 manja kernel: ACPI: PM: Preparing to enter system sleep state S3
feb 25 16:20:29 manja kernel: ACPI: PM: Saving platform NVS memory


feb 25 16:20:29 manja kernel: Disabling non-boot CPUs ...
feb 25 16:20:29 manja kernel: smpboot: CPU 1 is now offline
feb 25 16:20:29 manja kernel: smpboot: CPU 2 is now offline
feb 25 16:20:29 manja kernel: smpboot: CPU 3 is now offline
feb 25 16:20:29 manja kernel: smpboot: CPU 4 is now offline
feb 25 16:20:29 manja kernel: smpboot: CPU 5 is now offline
feb 25 16:20:29 manja kernel: ACPI: PM: Low-level resume complete
feb 25 16:20:29 manja kernel: ACPI: PM: Restoring platform NVS memory
feb 25 16:20:29 manja kernel: Enabling non-boot CPUs ...
feb 25 16:20:29 manja kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
feb 25 16:20:29 manja kernel: CPU1 is up
feb 25 16:20:29 manja kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
feb 25 16:20:29 manja kernel: CPU2 is up
feb 25 16:20:29 manja kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
feb 25 16:20:29 manja kernel: CPU3 is up
feb 25 16:20:29 manja kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
feb 25 16:20:29 manja kernel: CPU4 is up
feb 25 16:20:29 manja kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
feb 25 16:20:29 manja kernel: CPU5 is up
feb 25 16:20:29 manja kernel: ACPI: PM: Waking up from system sleep state S3


feb 25 16:20:29 manja kernel: i915 0000:00:02.0: [drm] [ENCODER:94:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
feb 25 16:20:29 manja kernel: i915 0000:00:02.0: [drm] [ENCODER:111:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it
feb 25 16:20:29 manja kernel: i915 0000:00:02.0: [drm] [ENCODER:121:DDI D/PHY D] is disabled/in DSI mode with an ungated DDI clock, gate it
feb 25 16:20:29 manja kernel: i915 0000:00:02.0: [drm] [ENCODER:125:DDI E/PHY E] is disabled/in DSI mode with an ungated DDI clock, gate it
feb 25 16:20:29 manja kernel: nvme nvme0: Shutdown timeout set to 8 seconds
feb 25 16:20:29 manja kernel: nvme nvme0: 6/0/0 default/read/poll queues
feb 25 16:20:29 manja kernel: nvme nvme1: 6/0/0 default/read/poll queues
feb 25 16:20:29 manja kernel: ata4: SATA link down (SStatus 0 SControl 300)
feb 25 16:20:29 manja kernel: ata3: SATA link down (SStatus 0 SControl 300)
feb 25 16:20:29 manja kernel: ata2: SATA link down (SStatus 4 SControl 300)
feb 25 16:20:29 manja kernel: ata6: SATA link down (SStatus 4 SControl 300)
feb 25 16:20:29 manja kernel: pci_bus 0000:04: Allocating resources
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: bridge window [io  0x1000-0x0fff] to [bus 04] add_size 1000
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 04] add_size 200000 add_align 100000
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: bridge window [mem 0x00100000-0x000fffff] to [bus 04] add_size 200000 add_align 100000
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: BAR 14: no space for [mem size 0x00200000]
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: BAR 14: failed to assign [mem size 0x00200000]
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: BAR 13: no space for [io  size 0x1000]
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: BAR 13: failed to assign [io  size 0x1000]
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: BAR 14: no space for [mem size 0x00200000]
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: BAR 14: failed to assign [mem size 0x00200000]
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: BAR 13: no space for [io  size 0x1000]
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: BAR 13: failed to assign [io  size 0x1000]
feb 25 16:20:29 manja kernel: pci 0000:03:00.0: PCI bridge to [bus 04]
feb 25 16:20:29 manja kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
feb 25 16:20:29 manja kernel: OOM killer enabled.
feb 25 16:20:29 manja kernel: Restarting tasks ... done.
feb 25 16:20:29 manja kernel: random: crng reseeded on system resumption
feb 25 16:20:29 manja kernel: PM: suspend exit
feb 25 16:20:29 manja systemd-sleep[53232]: System returned from sleep operation 'suspend'.
feb 25 16:20:29 manja systemd[1]: user.slice: Unit now thawed.
feb 25 16:20:29 manja systemd[1]: user-1000.slice: Unit now thawed.
feb 25 16:20:29 manja systemd[1]: user@1000.service: Unit now thawed.
feb 25 16:20:29 manja systemd[1]: session-1.scope: Unit now thawed.
feb 25 16:20:29 manja systemd-sleep[53232]: Successfully thawed unit 'user.slice'.
feb 25 16:20:29 manja systemd[1]: systemd-suspend.service: Deactivated successfully.
feb 25 16:20:29 manja systemd[1]: Finished System Suspend.
feb 25 16:20:29 manja systemd[1]: Stopped target Sleep.
feb 25 16:20:29 manja systemd[1]: Reached target Suspend.
feb 25 16:20:29 manja systemd-logind[694]: Operation 'suspend' finished.
feb 25 16:20:29 manja systemd[1]: Stopped target Suspend.


feb 25 16:20:29 manja NetworkManager[686]: <info>  [1740496829.0996] manager: sleep: wake requested (sleeping: yes  enabled: yes)
feb 25 16:20:29 manja NetworkManager[686]: <info>  [1740496829.0996] device (eno1): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
feb 25 16:20:29 manja systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
feb 25 16:20:29 manja kdeconnectd[1269]: 2025-02-25T16:20:29 kdeconnect.core: No local bluetooth adapter found
feb 25 16:20:29 manja kdeconnectd[1269]: 2025-02-25T16:20:29 default: Error sending UDP packet: QAbstractSocket::NetworkError
feb 25 16:20:29 manja kdeconnectd[1269]: 2025-02-25T16:20:29 kdeconnect.core: Failed to open any MDNS client sockets
feb 25 16:20:29 manja kdeconnectd[1269]: 2025-02-25T16:20:29 kdeconnect.core: Failed to open any MDNS server sockets
feb 25 16:20:29 manja kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Down
feb 25 16:20:29 manja NetworkManager[686]: <info>  [1740496829.1815] device (eno1): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
feb 25 16:20:29 manja NetworkManager[686]: <info>  [1740496829.3694] manager: NetworkManager state is now DISCONNECTED
feb 25 16:20:31 manja kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
feb 25 16:20:31 manja kernel: ata5.00: Entering active power mode
feb 25 16:20:31 manja kernel: sd 4:0:0:0: [sda] Starting disk
feb 25 16:20:31 manja kernel: ata5.00: configured for UDMA/133
feb 25 16:20:31 manja rtkit-daemon[908]: Supervising 3 threads of 2 processes of 1 users.
feb 25 16:20:31 manja rtkit-daemon[908]: Supervising 3 threads of 2 processes of 1 users.
feb 25 16:20:32 manja kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
feb 25 16:20:32 manja NetworkManager[686]: <info>  [1740496832.3650] device (eno1): carrier: link connected
feb 25 16:20:32 manja NetworkManager[686]: <info>  [1740496832.3652] device (eno1): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')
feb 25 16:20:32 manja NetworkManager[686]: <info>  [1740496832.3657] policy: auto-activating connection 'Wired connection 1' (8e3a3511-54a8-3bcd-9d81-64f9aab29653)
feb 25 16:20:32 manja NetworkManager[686]: <info>  [1740496832.3660] device (eno1): Activation: starting connection 'Wired connection 1' (8e3a3511-54a8-3bcd-9d81-64f9aab29653)
feb 25 16:20:32 manja NetworkManager[686]: <info>  [1740496832.3661] device (eno1): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
feb 25 16:20:32 manja NetworkManager[686]: <info>  [1740496832.3662] manager: NetworkManager state is now CONNECTING
feb 25 16:20:32 manja NetworkManager[686]: <info>  [1740496832.3663] device (eno1): state change: prepare -> config (reason 'none', managed-type: 'full')
feb 25 16:20:32 manja NetworkManager[686]: <info>  [1740496832.3667] device (eno1): state change: config -> ip-config (reason 'none', managed-type: 'full')
feb 25 16:20:32 manja NetworkManager[686]: <info>  [1740496832.3670] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
feb 25 16:20:32 manja avahi-daemon[688]: Joining mDNS multicast group on interface eno1.IPv6 with address fe80::7fe:42a2:3949:d69.
feb 25 16:20:32 manja avahi-daemon[688]: New relevant interface eno1.IPv6 for mDNS.
feb 25 16:20:32 manja avahi-daemon[688]: Registering new address record for fe80::7fe:42a2:3949:d69 on eno1.*.
feb 25 16:20:34 manja NetworkManager[686]: <info>  [1740496834.3994] dhcp6 (eno1): activation: beginning transaction (timeout in 45 seconds)
feb 25 16:20:34 manja NetworkManager[686]: <info>  [1740496834.3996] policy: set 'Wired connection 1' (eno1) as default for IPv6 routing and DNS
feb 25 16:20:34 manja avahi-daemon[688]: Leaving mDNS multicast group on interface eno1.IPv6 with address fe80::7fe:42a2:3949:d69.
feb 25 16:20:34 manja avahi-daemon[688]: Joining mDNS multicast group on interface eno1.IPv6 with address 2a02:a460:4647:0:bfe4:8d0b:5362:d089.
feb 25 16:20:34 manja NetworkManager[686]: <info>  [1740496834.4226] dhcp6 (eno1): state changed new lease
feb 25 16:20:34 manja avahi-daemon[688]: Registering new address record for 2a02:a460:4647:0:bfe4:8d0b:5362:d089 on eno1.*.
feb 25 16:20:34 manja avahi-daemon[688]: Withdrawing address record for fe80::7fe:42a2:3949:d69 on eno1.
feb 25 16:20:34 manja avahi-daemon[688]: Registering new address record for fd4c:4b32:3230:0:3e2e:c1f2:a3eb:24e1 on eno1.*.
feb 25 16:20:34 manja NetworkManager[686]: <info>  [1740496834.4232] dhcp4 (eno1): state changed new lease, address=192.168.2.38, acd pending
feb 25 16:20:34 manja NetworkManager[686]: <info>  [1740496834.6053] dhcp4 (eno1): state changed new lease, address=192.168.2.38
feb 25 16:20:34 manja NetworkManager[686]: <info>  [1740496834.6055] policy: set 'Wired connection 1' (eno1) as default for IPv4 routing and DNS
feb 25 16:20:34 manja avahi-daemon[688]: Joining mDNS multicast group on interface eno1.IPv4 with address 192.168.2.38.
feb 25 16:20:34 manja avahi-daemon[688]: New relevant interface eno1.IPv4 for mDNS.
feb 25 16:20:34 manja avahi-daemon[688]: Registering new address record for 192.168.2.38 on eno1.IPv4.
feb 25 16:20:34 manja NetworkManager[686]: <info>  [1740496834.6122] device (eno1): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
feb 25 16:20:34 manja NetworkManager[686]: <info>  [1740496834.6134] device (eno1): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
feb 25 16:20:34 manja NetworkManager[686]: <info>  [1740496834.6135] device (eno1): state change: secondaries -> activated (reason 'none', managed-type: 'full')
feb 25 16:20:34 manja NetworkManager[686]: <info>  [1740496834.6138] manager: NetworkManager state is now CONNECTED_SITE
feb 25 16:20:34 manja NetworkManager[686]: <info>  [1740496834.6139] device (eno1): Activation: successful, device activated.
feb 25 16:20:34 manja NetworkManager[686]: <info>  [1740496834.6541] manager: NetworkManager state is now CONNECTED_GLOBAL
feb 25 16:20:35 manja systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
feb 25 16:20:38 manja plasmashell[1062]: :3:../common/rclinit.cpp:411::Recoll 1.42.0 + Xapian 1.4.25 [/home/hans/.recoll]
feb 25 16:20:38 manja plasmashell[1062]: RecollRunner::match: recoll query: j
feb 25 16:20:38 manja plasmashell[1062]: RecollRunner::match: recoll query: jo
feb 25 16:20:41 manja plasmashell[1062]: RecollRunner::match: recoll query: jou
feb 25 16:20:43 manja systemd[823]: Started KSystemLog - System Log Viewer.