Debugging suspend-then-hibernate

gr523 · 2022-11-21 08:53:59

Laptop model is lenovo ideapad 5 pro 14acn6

Problem : When using suspend-then-hibernate system stays in suspend even after HibernateDelaySec in sleep.conf
So normally suspend-then-hibernate works same as suspend but sometimes after waking up the device after HibernateDelaySec, the current sessions freezes and no input makes any change, in that state I can Ctrl-Alt-F2, go to another tty and terminate that user

The output of

 journalctl -fu systemd-suspend-then-hibernate.service

is the same after waking up the system with keyboard input before or after HibernateDelaySec, and no errors are shown

Problem is tested on kernel 6+, lts 5.15.*, all yielding the same result

I have tried downgrading,
linux-firmware, linux-firmware-whence,
amd-ucode,
systemd-libs, systemd-sysvcompat

I tried these specific packages because these were some of the packages that were upgraded after the timeline where this problem was detected, but with no luck

Maybe it's not relevant but I did have an bios update around the same time the problem occurred

Directions for further debugging is requested

cfr · 2022-11-23 04:35:00

What problem are you trying to solve exactly? The staying suspending after HibernateDelaySec or the freezing when waking from suspend after that point?

gr523 · 2022-11-23 15:59:04

cfr wrote:

What problem are you trying to solve exactly? The staying suspending after HibernateDelaySec or the freezing when waking from suspend after that point?

Staying in suspend after HibernateDelaySec is the problem, the second scenario is non-existent if the first problem is fixed,
I mentioned it in case someone had the same problem they would recognize it easily

cfr · 2022-11-24 01:59:29

gr523 wrote:

Staying in suspend after HibernateDelaySec is the problem,

According to systemd, it is not a problem but by design and the previous behaviour was a temporary fix.

However, it seems likely that the old behaviour will be made available in a systemd update. This may or may not require altering the name of the option. When I read the discussion, implementation hadn't been decided, but there did seem to be agreement that the old behaviour could be made available, even if the developers consider it a 'weird' request. (I believe they didn't expect anybody to complain about them finally getting the option working as they'd intended, but have discovered lots of people find the weird case congenial.)

At any rate, there is nothing you can do about this other than downgrade (which would leave your system in an unsupported state, liable to breakage) or wait for the 'new' option to become available.

Edit: https://github.com/systemd/systemd/issues/25269

Last edited by cfr (2022-11-24 02:04:40)

gr523 · 2022-11-28 07:39:47

cfr wrote:

gr523 wrote:
Staying in suspend after HibernateDelaySec is the problem,
According to systemd, it is not a problem but by design and the previous behaviour was a temporary fix.
However, it seems likely that the old behaviour will be made available in a systemd update. This may or may not require altering the name of the option. When I read the discussion, implementation hadn't been decided, but there did seem to be agreement that the old behaviour could be made available, even if the developers consider it a 'weird' request. (I believe they didn't expect anybody to complain about them finally getting the option working as they'd intended, but have discovered lots of people find the weird case congenial.)
At any rate, there is nothing you can do about this other than downgrade (which would leave your system in an unsupported state, liable to breakage) or wait for the 'new' option to become available.
Edit: https://github.com/systemd/systemd/issues/25269

I suppose the meaning of HibernateDelaySec has changed, according to the documentation this is expected behavior and actual problem is the second one, so suspend-then-hibernate is still broken for me
The problem occurs everytime I wake up the system after HibernateDelaySec, the session freezes, I can log in to another session but that freezed session can only be terminated by loginctl terminate-session
The problem does not occur if I wake up the system before HibernateDelaySec, thats all I know for sure for now

cfr · 2022-11-28 23:17:49

Post the journal. (See the link below for ways to post it to a pastebin service from the tty if that's easiest.)

gr523 · 2022-12-03 10:38:50

cfr wrote:

Post the journal. (See the link below for ways to post it to a pastebin service from the tty if that's easiest.)

Dec 03 16:28:17 ip5 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Dec 03 16:28:17 ip5 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 03 16:28:17 ip5 kernel: audit: type=1131 audit(1670063297.228:138): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 03 16:28:17 ip5 audit: BPF prog-id=0 op=UNLOAD
Dec 03 16:28:17 ip5 audit: BPF prog-id=0 op=UNLOAD
Dec 03 16:28:17 ip5 audit: BPF prog-id=0 op=UNLOAD
Dec 03 16:28:17 ip5 kernel: audit: type=1334 audit(1670063297.265:139): prog-id=0 op=UNLOAD
Dec 03 16:28:17 ip5 kernel: audit: type=1334 audit(1670063297.265:140): prog-id=0 op=UNLOAD
Dec 03 16:28:17 ip5 kernel: audit: type=1334 audit(1670063297.265:141): prog-id=0 op=UNLOAD
Dec 03 16:28:17 ip5 polkitd[1123]: Registered Authentication Agent for unix-process:1729:3353 (system bus name :1.48 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Dec 03 16:28:17 ip5 systemd-logind[552]: The system will suspend and later hibernate now!
Dec 03 16:28:17 ip5 polkitd[1123]: Unregistered Authentication Agent for unix-process:1729:3353 (system bus name :1.48, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Dec 03 16:28:17 ip5 renzhamin[1735]: [psd-suspend-sync] Issuing suspend-sync request...
Dec 03 16:28:18 ip5 profile-sync-daemon[1737]: brave resync successful
Dec 03 16:28:18 ip5 profile-sync-daemon[1737]: firefox resync successful
Dec 03 16:28:18 ip5 profile-sync-daemon[1737]: firefox resync successful
Dec 03 16:28:18 ip5 systemd[1]: Reached target Sleep.
Dec 03 16:28:18 ip5 systemd[1]: Starting Suspend; Hibernate if not used for a period of time...
Dec 03 16:28:18 ip5 systemd-sleep[1802]: Entering sleep state 'suspend'...
Dec 03 16:28:18 ip5 kernel: PM: suspend entry (deep)
Dec 03 16:28:18 ip5 kernel: Filesystems sync: 0.031 seconds
Dec 03 16:31:42 ip5 kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Dec 03 16:31:42 ip5 kernel: OOM killer disabled.
Dec 03 16:31:42 ip5 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Dec 03 16:31:42 ip5 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dec 03 16:31:42 ip5 kernel: [drm] free PSP TMR buffer
Dec 03 16:31:42 ip5 kernel: ACPI: EC: interrupt blocked
Dec 03 16:31:42 ip5 kernel: ACPI: PM: Preparing to enter system sleep state S3
Dec 03 16:31:42 ip5 kernel: ACPI: EC: event blocked
Dec 03 16:31:42 ip5 kernel: ACPI: EC: EC stopped
Dec 03 16:31:42 ip5 kernel: ACPI: PM: Saving platform NVS memory
Dec 03 16:31:42 ip5 kernel: Disabling non-boot CPUs ...
Dec 03 16:31:42 ip5 kernel: smpboot: CPU 1 is now offline
Dec 03 16:31:42 ip5 kernel: smpboot: CPU 2 is now offline
Dec 03 16:31:42 ip5 kernel: smpboot: CPU 3 is now offline
Dec 03 16:31:42 ip5 kernel: smpboot: CPU 4 is now offline
Dec 03 16:31:42 ip5 kernel: smpboot: CPU 5 is now offline
Dec 03 16:31:42 ip5 kernel: smpboot: CPU 6 is now offline
Dec 03 16:31:42 ip5 kernel: smpboot: CPU 7 is now offline
Dec 03 16:31:42 ip5 kernel: smpboot: CPU 8 is now offline
Dec 03 16:31:42 ip5 kernel: smpboot: CPU 9 is now offline
Dec 03 16:31:42 ip5 kernel: smpboot: CPU 10 is now offline
Dec 03 16:31:42 ip5 kernel: smpboot: CPU 11 is now offline
Dec 03 16:31:42 ip5 kernel: smpboot: CPU 12 is now offline
Dec 03 16:31:42 ip5 kernel: smpboot: CPU 13 is now offline
Dec 03 16:31:42 ip5 kernel: smpboot: CPU 14 is now offline
Dec 03 16:31:42 ip5 kernel: smpboot: CPU 15 is now offline
Dec 03 16:31:42 ip5 kernel: ACPI: PM: Low-level resume complete
Dec 03 16:31:42 ip5 kernel: ACPI: EC: EC started
Dec 03 16:31:42 ip5 kernel: ACPI: PM: Restoring platform NVS memory
Dec 03 16:31:42 ip5 kernel: AMD-Vi: Virtual APIC enabled
Dec 03 16:31:42 ip5 kernel: AMD-Vi: Virtual APIC enabled
Dec 03 16:31:42 ip5 kernel: LVT offset 0 assigned for vector 0x400
Dec 03 16:31:42 ip5 kernel: Enabling non-boot CPUs ...
Dec 03 16:31:42 ip5 kernel: x86: Booting SMP configuration:
Dec 03 16:31:42 ip5 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Dec 03 16:31:42 ip5 kernel: microcode: CPU1: patch_level=0x0a50000d
Dec 03 16:31:42 ip5 kernel: ACPI: \_SB_.PLTF.C001: Found 3 idle states
Dec 03 16:31:42 ip5 kernel: CPU1 is up
Dec 03 16:31:42 ip5 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Dec 03 16:31:42 ip5 kernel: microcode: CPU2: patch_level=0x0a50000d
Dec 03 16:31:42 ip5 kernel: ACPI: \_SB_.PLTF.C002: Found 3 idle states
Dec 03 16:31:42 ip5 kernel: CPU2 is up
Dec 03 16:31:42 ip5 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Dec 03 16:31:42 ip5 kernel: microcode: CPU3: patch_level=0x0a50000d
Dec 03 16:31:42 ip5 kernel: ACPI: \_SB_.PLTF.C003: Found 3 idle states
Dec 03 16:31:42 ip5 kernel: CPU3 is up
Dec 03 16:31:42 ip5 kernel: smpboot: Booting Node 0 Processor 4 APIC 0x4
Dec 03 16:31:42 ip5 kernel: microcode: CPU4: patch_level=0x0a50000d
Dec 03 16:31:42 ip5 kernel: ACPI: \_SB_.PLTF.C004: Found 3 idle states
Dec 03 16:31:42 ip5 kernel: CPU4 is up
Dec 03 16:31:42 ip5 kernel: smpboot: Booting Node 0 Processor 5 APIC 0x5
Dec 03 16:31:42 ip5 kernel: microcode: CPU5: patch_level=0x0a50000d
Dec 03 16:31:42 ip5 kernel: ACPI: \_SB_.PLTF.C005: Found 3 idle states
Dec 03 16:31:42 ip5 kernel: CPU5 is up
Dec 03 16:31:42 ip5 kernel: smpboot: Booting Node 0 Processor 6 APIC 0x6
Dec 03 16:31:42 ip5 kernel: microcode: CPU6: patch_level=0x0a50000d
Dec 03 16:31:42 ip5 kernel: ACPI: \_SB_.PLTF.C006: Found 3 idle states
Dec 03 16:31:42 ip5 kernel: CPU6 is up
Dec 03 16:31:42 ip5 kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
Dec 03 16:31:42 ip5 kernel: microcode: CPU7: patch_level=0x0a50000d
Dec 03 16:31:42 ip5 kernel: ACPI: \_SB_.PLTF.C007: Found 3 idle states
Dec 03 16:31:42 ip5 kernel: CPU7 is up
Dec 03 16:31:42 ip5 kernel: smpboot: Booting Node 0 Processor 8 APIC 0x8
Dec 03 16:31:42 ip5 kernel: microcode: CPU8: patch_level=0x0a50000d
Dec 03 16:31:42 ip5 kernel: ACPI: \_SB_.PLTF.C008: Found 3 idle states
Dec 03 16:31:42 ip5 kernel: CPU8 is up
Dec 03 16:31:42 ip5 kernel: smpboot: Booting Node 0 Processor 9 APIC 0x9
Dec 03 16:31:42 ip5 kernel: microcode: CPU9: patch_level=0x0a50000d
Dec 03 16:31:42 ip5 kernel: ACPI: \_SB_.PLTF.C009: Found 3 idle states
Dec 03 16:31:42 ip5 kernel: CPU9 is up
Dec 03 16:31:42 ip5 kernel: smpboot: Booting Node 0 Processor 10 APIC 0xa
Dec 03 16:31:42 ip5 kernel: microcode: CPU10: patch_level=0x0a50000d
Dec 03 16:31:42 ip5 kernel: ACPI: \_SB_.PLTF.C00A: Found 3 idle states
Dec 03 16:31:42 ip5 kernel: CPU10 is up
Dec 03 16:31:42 ip5 kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Dec 03 16:31:42 ip5 kernel: microcode: CPU11: patch_level=0x0a50000d
Dec 03 16:31:42 ip5 kernel: ACPI: \_SB_.PLTF.C00B: Found 3 idle states
Dec 03 16:31:42 ip5 kernel: CPU11 is up
Dec 03 16:31:42 ip5 kernel: smpboot: Booting Node 0 Processor 12 APIC 0xc
Dec 03 16:31:42 ip5 kernel: microcode: CPU12: patch_level=0x0a50000d
Dec 03 16:31:42 ip5 kernel: ACPI: \_SB_.PLTF.C00C: Found 3 idle states
Dec 03 16:31:42 ip5 kernel: CPU12 is up
Dec 03 16:31:42 ip5 kernel: smpboot: Booting Node 0 Processor 13 APIC 0xd
Dec 03 16:31:42 ip5 kernel: microcode: CPU13: patch_level=0x0a50000d
Dec 03 16:31:42 ip5 kernel: ACPI: \_SB_.PLTF.C00D: Found 3 idle states
Dec 03 16:31:42 ip5 kernel: CPU13 is up
Dec 03 16:31:42 ip5 kernel: smpboot: Booting Node 0 Processor 14 APIC 0xe
Dec 03 16:31:42 ip5 kernel: microcode: CPU14: patch_level=0x0a50000d
Dec 03 16:31:42 ip5 kernel: ACPI: \_SB_.PLTF.C00E: Found 3 idle states
Dec 03 16:31:42 ip5 kernel: CPU14 is up
Dec 03 16:31:42 ip5 kernel: smpboot: Booting Node 0 Processor 15 APIC 0xf
Dec 03 16:31:42 ip5 kernel: microcode: CPU15: patch_level=0x0a50000d
Dec 03 16:31:42 ip5 kernel: ACPI: \_SB_.PLTF.C00F: Found 3 idle states
Dec 03 16:31:42 ip5 kernel: CPU15 is up
Dec 03 16:31:42 ip5 kernel: ACPI: PM: Waking up from system sleep state S3
Dec 03 16:31:42 ip5 kernel: ACPI: EC: interrupt unblocked
Dec 03 16:31:42 ip5 kernel: ACPI: EC: event unblocked
Dec 03 16:31:42 ip5 kernel: [drm] PCIE GART of 1024M enabled.
Dec 03 16:31:42 ip5 kernel: [drm] PTB located at 0x000000F400A00000
Dec 03 16:31:42 ip5 kernel: [drm] PSP is resuming...
Dec 03 16:31:42 ip5 kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
Dec 03 16:31:42 ip5 kernel: pci 0000:00:00.2: PCI INT A: no GSI
Dec 03 16:31:42 ip5 kernel: nvme nvme0: Shutdown timeout set to 8 seconds
Dec 03 16:31:42 ip5 kernel: [drm] reserve 0x400000 from 0xf47f800000 for PSP TMR
Dec 03 16:31:42 ip5 kernel: nvme nvme0: 16/0/0 default/read/poll queues
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: RAS: optional ras ta ucode is not available
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: RAP: optional rap ta ucode is not available
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
Dec 03 16:31:42 ip5 kernel: [drm] DMUB hardware initialized: version=0x0101001F
Dec 03 16:31:42 ip5 kernel: [drm] kiq ring mec 2 pipe 1 q 0
Dec 03 16:31:42 ip5 kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Dec 03 16:31:42 ip5 kernel: [drm] JPEG decode initialized successfully.
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1
Dec 03 16:31:42 ip5 kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1
Dec 03 16:31:42 ip5 kernel: OOM killer enabled.
Dec 03 16:31:42 ip5 kernel: Restarting tasks ... done.
Dec 03 16:31:42 ip5 kernel: random: crng reseeded on system resumption
Dec 03 16:31:42 ip5 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dec 03 16:31:42 ip5 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 03 16:31:42 ip5 kernel: audit: type=1131 audit(1670063502.994:142): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 03 16:31:43 ip5 systemd-sleep[1802]: System returned from sleep state.
Dec 03 16:31:43 ip5 bluetoothd[548]: Controller resume with wake event 0x0
Dec 03 16:31:43 ip5 kernel: PM: suspend exit
Dec 03 16:31:43 ip5 systemd[1]: systemd-suspend-then-hibernate.service: Deactivated successfully.
Dec 03 16:31:43 ip5 systemd[1]: Finished Suspend; Hibernate if not used for a period of time.
Dec 03 16:31:43 ip5 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend-then-hibernate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 03 16:31:43 ip5 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend-then-hibernate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 03 16:31:43 ip5 kernel: audit: type=1130 audit(1670063503.153:143): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend-then-hibernate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 03 16:31:43 ip5 kernel: audit: type=1131 audit(1670063503.153:144): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend-then-hibernate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 03 16:31:43 ip5 systemd[1]: Stopped target Sleep.
Dec 03 16:31:43 ip5 systemd[1]: Reached target Suspend; Hibernate if not used for a period of time.
Dec 03 16:31:43 ip5 systemd-logind[552]: Operation 'sleep' finished.
Dec 03 16:31:43 ip5 renzhamin[1864]: [psd-suspend-sync] re-taking inhibit lock...
Dec 03 16:31:43 ip5 systemd[1]: Starting enable the infrared emitter...
Dec 03 16:31:43 ip5 systemd[1]: Stopped target Suspend; Hibernate if not used for a period of time.
Dec 03 16:31:43 ip5 systemd[1]: linux-enable-ir-emitter.service: Deactivated successfully.
Dec 03 16:31:43 ip5 systemd[1]: Finished enable the infrared emitter.
Dec 03 16:31:43 ip5 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=linux-enable-ir-emitter comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 03 16:31:43 ip5 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=linux-enable-ir-emitter comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 03 16:31:43 ip5 kernel: audit: type=1130 audit(1670063503.233:145): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=linux-enable-ir-emitter comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 03 16:31:43 ip5 kernel: audit: type=1131 audit(1670063503.233:146): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=linux-enable-ir-emitter comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Arch Linux

#1 2022-11-21 08:53:59

Debugging suspend-then-hibernate

#2 2022-11-23 04:35:00

Re: Debugging suspend-then-hibernate

#3 2022-11-23 15:59:04

Re: Debugging suspend-then-hibernate

#4 2022-11-24 01:59:29

Re: Debugging suspend-then-hibernate

#5 2022-11-28 07:39:47

Re: Debugging suspend-then-hibernate

#6 2022-11-28 23:17:49

Re: Debugging suspend-then-hibernate

#7 2022-12-03 10:38:50

Re: Debugging suspend-then-hibernate

Board footer