My system wakes up immediately from hibernation

aaditmshah · 2024-03-22 17:29:27

I set up my system for hibernation and I have been using it for several months without any issue. However, recently when I try to put my system into hibernation, it wakes up immediately. Here's the relevant output of dmesg.

[ 1601.829280] PM: Using 3 thread(s) for compression
[ 1601.829285] PM: Compressing and saving image data (1227235 pages)...
[ 1601.829300] PM: Image saving progress:   0%
[ 1602.243632] PM: Image saving progress:  10%
[ 1602.604229] PM: Image saving progress:  20%
[ 1602.981136] PM: Image saving progress:  30%
[ 1603.350421] PM: Image saving progress:  40%
[ 1603.746793] PM: Image saving progress:  50%
[ 1604.128095] PM: Image saving progress:  60%
[ 1604.487065] PM: Image saving progress:  70%
[ 1604.843625] PM: Image saving progress:  80%
[ 1605.177455] PM: Image saving progress:  90%
[ 1605.499952] PM: Image saving progress: 100%
[ 1605.500131] PM: Image saving done
[ 1605.500132] PM: hibernation: Wrote 4908940 kbytes in 3.67 seconds (1337.58 MB/s)
[ 1605.500210] PM: S|
[ 1605.597014] printk: Suspending console(s) (use no_console_suspend to debug)
[ 1605.635623] PM: hibernation: Wakeup event detected during hibernation, rolling back.
[ 1605.635662] PM: hibernation: Basic memory bitmaps freed
[ 1605.636640] OOM killer enabled.
[ 1605.636641] Restarting tasks ... done.
[ 1605.720185] PM: hibernation: hibernation exit

So, immediately after hibernation there's a wakeup event. I followed the Instantaneous wakeups from suspend article to troubleshoot the issue, but I couldn't find the wakeup trigger. What else can I do to troubleshoot the issue?

Last edited by aaditmshah (2024-03-23 03:33:50)

seth · 2024-03-22 19:54:12

Your linked article is 404/bogus

Can you S3 w/o wakeup and is there a parallel windows installation?
What's the output of

cat /proc/acpi/wakeup

and also post the system journal covering the incident (there might be some telling userspace event causing this)

aaditmshah · 2024-03-23 04:08:37

Your linked article is 404/bogus

My bad. Fixed the link.

Can you S3 w/o wakeup

Yes, I can suspend to RAM without wakeup.

and is there a parallel windows installation?

Yes, I am dual booting Arch Linux and Windows. My laptop came with an official version of Windows pre-installed, and I didn't want to format it even though I never use it.

What's the output of
cat /proc/acpi/wakeup

Here's the complete output.

Device  S-state   Status   Sysfs node
PEG0      S3    *disabled  pci:0000:00:06.0
PEGP      S4    *disabled
PEG1      S3    *disabled
PEGP      S4    *disabled
PEG2      S3    *disabled
PEGP      S4    *disabled
XHCI      S0    *enabled   pci:0000:00:14.0
XDCI      S4    *disabled
HDAS      S4    *disabled  pci:0000:00:1f.3
CNVW      S4    *disabled  pci:0000:00:14.3
RP01      S4    *disabled
PXSX      S4    *disabled
RP02      S4    *disabled
PXSX      S4    *disabled
RP03      S4    *disabled
PXSX      S4    *disabled
RP04      S4    *disabled
PXSX      S4    *disabled
RP05      S4    *disabled
PXSX      S4    *disabled
RP06      S4    *disabled
PXSX      S4    *disabled
RP07      S4    *disabled
PXSX      S4    *disabled
RP08      S4    *disabled
PXSX      S4    *disabled
RP09      S4    *disabled
PXSX      S4    *disabled
RP10      S4    *disabled
PXSX      S4    *disabled
RP11      S4    *disabled
PXSX      S4    *disabled
RP12      S4    *disabled
PXSX      S4    *disabled
RP13      S4    *disabled
PXSX      S4    *disabled
RP14      S4    *disabled
PXSX      S4    *disabled
RP15      S4    *disabled
PXSX      S4    *disabled
RP16      S4    *disabled
PXSX      S4    *disabled
RP17      S4    *disabled
PXSX      S4    *disabled
RP18      S4    *disabled
PXSX      S4    *disabled
RP19      S4    *disabled
PXSX      S4    *disabled
RP20      S4    *disabled
PXSX      S4    *disabled
RP21      S4    *disabled
PXSX      S4    *disabled
RP22      S4    *disabled
PXSX      S4    *disabled
RP23      S4    *disabled
PXSX      S4    *disabled
RP24      S4    *disabled
PXSX      S4    *disabled
TXHC      S4    *enabled   pci:0000:00:0d.0
TDM0      S4    *enabled   pci:0000:00:0d.2
TDM1      S4    *disabled
TRP0      S4    *enabled   pci:0000:00:07.0
PXSX      S4    *disabled
TRP1      S4    *disabled
PXSX      S4    *disabled
TRP2      S4    *disabled
PXSX      S4    *disabled
TRP3      S4    *disabled
PXSX      S4    *disabled
AWAC      S4    *enabled   platform:ACPI000E:00
LID0      S3    *enabled   platform:PNP0C0D:00
PBTN      S3    *enabled   platform:PNP0C0C:00

And here is the list of enabled devices.

Device  S-state   Status   Sysfs node
XHCI      S0    *enabled   pci:0000:00:14.0
TXHC      S4    *enabled   pci:0000:00:0d.0
TDM0      S4    *enabled   pci:0000:00:0d.2
TRP0      S4    *enabled   pci:0000:00:07.0
AWAC      S4    *enabled   platform:ACPI000E:00
LID0      S3    *enabled   platform:PNP0C0D:00
PBTN      S3    *enabled   platform:PNP0C0C:00

and also post the system journal covering the incident (there might be some telling userspace event causing this)

Mar 23 09:35:06 home systemd[698]: Started dbus-:1.2-org.kde.LogoutPrompt@2.service.
Mar 23 09:35:06 home ksmserver-logout-greeter[11330]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
Mar 23 09:35:07 home systemd-logind[435]: The system will hibernate now!
Mar 23 09:35:07 home NetworkManager[433]: <info>  [1711166707.8281] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Mar 23 09:35:07 home NetworkManager[433]: <info>  [1711166707.8284] device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Mar 23 09:35:07 home NetworkManager[433]: <info>  [1711166707.8288] manager: NetworkManager state is now ASLEEP
Mar 23 09:35:07 home NetworkManager[433]: <info>  [1711166707.8299] device (wlp0s20f3): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Mar 23 09:35:07 home plasmashell[1725]: [1720:1746:0323/093507.830972:ERROR:connection_factory_impl.cc(483)] ConnectionHandler failed with net error: -2
Mar 23 09:35:07 home kded6[883]: org.kde.plasma.nm.kded: Unhandled active connection state change:  3
Mar 23 09:35:07 home systemd[698]: dbus-:1.2-org.kde.LogoutPrompt@2.service: Main process exited, code=exited, status=1/FAILURE
Mar 23 09:35:07 home systemd[698]: dbus-:1.2-org.kde.LogoutPrompt@2.service: Failed with result 'exit-code'.
Mar 23 09:35:07 home systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 23 09:35:07 home systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 23 09:35:07 home dhcpcd[437]: wlp0s20f3: carrier lost
Mar 23 09:35:07 home kernel: wlp0s20f3: deauthenticating from 82:2a:a8:39:20:12 by local choice (Reason: 3=DEAUTH_LEAVING)
Mar 23 09:35:07 home dhcpcd[437]: wlp0s20f3: deleting address 2405:201:12:3dae:fef4:a3d4:1b8a:7f2e/64
Mar 23 09:35:07 home dhcpcd[437]: wlp0s20f3: deleting route to 2405:201:12:3dae::/64
Mar 23 09:35:07 home dhcpcd[437]: wlp0s20f3: deleting default route via fe80::1a82:8cff:fefc:22fd
Mar 23 09:35:07 home dhcpcd[437]: wlp0s20f3: deleting address fe80::e3d9:3eb8:fbc3:74d2
Mar 23 09:35:07 home wpa_supplicant[570]: wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=82:2a:a8:39:20:12 reason=3 locally_generated=1
Mar 23 09:35:07 home dhcpcd[437]: wlp0s20f3: deleting route to 192.168.29.0/24
Mar 23 09:35:07 home dhcpcd[437]: wlp0s20f3: deleting default route via 192.168.29.1
Mar 23 09:35:07 home wpa_supplicant[570]: wlp0s20f3: CTRL-EVENT-DSCP-POLICY clear_all
Mar 23 09:35:07 home NetworkManager[433]: <info>  [1711166707.9542] device (wlp0s20f3): supplicant interface state: completed -> disconnected
Mar 23 09:35:07 home NetworkManager[433]: <info>  [1711166707.9544] device (wlp0s20f3): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Mar 23 09:35:07 home NetworkManager[433]: <info>  [1711166707.9546] dhcp4 (wlp0s20f3): canceled DHCP transaction
Mar 23 09:35:07 home NetworkManager[433]: <info>  [1711166707.9547] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
Mar 23 09:35:07 home NetworkManager[433]: <info>  [1711166707.9547] dhcp4 (wlp0s20f3): state changed no lease
Mar 23 09:35:07 home dhcpcd[437]: wlp0s20f3: old hardware address: f0:20:ff:b9:6a:1d
Mar 23 09:35:07 home dhcpcd[437]: wlp0s20f3: new hardware address: d2:aa:4f:95:24:9f
Mar 23 09:35:07 home NetworkManager[433]: <info>  [1711166707.9861] device (wlp0s20f3): set-hw-addr: set MAC address to D2:AA:4F:95:24:9F (scanning)
Mar 23 09:35:08 home NetworkManager[433]: <info>  [1711166708.0747] device (wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Mar 23 09:35:08 home dhcpcd[437]: wlp0s20f3: old hardware address: d2:aa:4f:95:24:9f
Mar 23 09:35:08 home dhcpcd[437]: wlp0s20f3: new hardware address: f0:20:ff:b9:6a:1d
Mar 23 09:35:08 home NetworkManager[433]: <info>  [1711166708.2285] device (wlp0s20f3): set-hw-addr: reset MAC address to F0:20:FF:B9:6A:1D (unmanage)
Mar 23 09:35:08 home systemd[1]: Reached target Sleep.
Mar 23 09:35:08 home systemd[1]: Starting System Hibernate...
Mar 23 09:35:08 home systemd-sleep[11454]: Performing sleep operation 'hibernate'...
Mar 23 09:35:08 home kernel: PM: hibernation: hibernation entry
Mar 23 09:35:08 home wpa_supplicant[570]: p2p-dev-wlp0s20: CTRL-EVENT-DSCP-POLICY clear_all
Mar 23 09:35:08 home wpa_supplicant[570]: p2p-dev-wlp0s20: CTRL-EVENT-DSCP-POLICY clear_all
Mar 23 09:35:08 home wpa_supplicant[570]: nl80211: deinit ifname=p2p-dev-wlp0s20 disabled_11b_rates=0
Mar 23 09:35:08 home wpa_supplicant[570]: wlp0s20f3: CTRL-EVENT-DSCP-POLICY clear_all
Mar 23 09:35:08 home wpa_supplicant[570]: wlp0s20f3: CTRL-EVENT-DSCP-POLICY clear_all
Mar 23 09:35:08 home wpa_supplicant[570]: nl80211: deinit ifname=wlp0s20f3 disabled_11b_rates=0
Mar 23 09:35:16 home kernel: Filesystems sync: 0.002 seconds
Mar 23 09:35:16 home kernel: Freezing user space processes
Mar 23 09:35:16 home kernel: Freezing user space processes completed (elapsed 0.003 seconds)
Mar 23 09:35:16 home kernel: OOM killer disabled.
Mar 23 09:35:16 home kernel: PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
Mar 23 09:35:16 home kernel: PM: hibernation: Marking nosave pages: [mem 0x0009f000-0x000fffff]
Mar 23 09:35:16 home kernel: PM: hibernation: Marking nosave pages: [mem 0x57863000-0x57885fff]
Mar 23 09:35:16 home kernel: PM: hibernation: Marking nosave pages: [mem 0x5cd15000-0x617fefff]
Mar 23 09:35:16 home kernel: PM: hibernation: Marking nosave pages: [mem 0x61800000-0xffffffff]
Mar 23 09:35:16 home kernel: PM: hibernation: Basic memory bitmaps created
Mar 23 09:35:16 home kernel: PM: hibernation: Preallocating image memory
Mar 23 09:35:16 home kernel: PM: hibernation: Allocated 1570738 pages for snapshot
Mar 23 09:35:16 home kernel: PM: hibernation: Allocated 6282952 kbytes in 1.54 seconds (4079.83 MB/s)
Mar 23 09:35:16 home kernel: Freezing remaining freezable tasks
Mar 23 09:35:16 home kernel: Freezing remaining freezable tasks completed (elapsed 0.538 seconds)
Mar 23 09:35:16 home kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 23 09:35:16 home kernel: ACPI: EC: interrupt blocked
Mar 23 09:35:16 home kernel: ACPI: PM: Preparing to enter system sleep state S4
Mar 23 09:35:16 home kernel: ACPI: EC: event blocked
Mar 23 09:35:16 home kernel: ACPI: EC: EC stopped
Mar 23 09:35:16 home kernel: ACPI: PM: Saving platform NVS memory
Mar 23 09:35:16 home kernel: Disabling non-boot CPUs ...
Mar 23 09:35:16 home kernel: migrate_one_irq: 5 callbacks suppressed
Mar 23 09:35:16 home kernel: IRQ158: set affinity failed(-22).
Mar 23 09:35:16 home kernel: smpboot: CPU 1 is now offline
Mar 23 09:35:16 home kernel: IRQ158: set affinity failed(-22).
Mar 23 09:35:16 home kernel: smpboot: CPU 2 is now offline
Mar 23 09:35:16 home kernel: IRQ158: set affinity failed(-22).
Mar 23 09:35:16 home kernel: smpboot: CPU 3 is now offline
Mar 23 09:35:16 home kernel: IRQ158: set affinity failed(-22).
Mar 23 09:35:16 home kernel: smpboot: CPU 4 is now offline
Mar 23 09:35:16 home kernel: IRQ158: set affinity failed(-22).
Mar 23 09:35:16 home kernel: smpboot: CPU 5 is now offline
Mar 23 09:35:16 home kernel: IRQ158: set affinity failed(-22).
Mar 23 09:35:16 home kernel: smpboot: CPU 6 is now offline
Mar 23 09:35:16 home kernel: IRQ158: set affinity failed(-22).
Mar 23 09:35:16 home kernel: smpboot: CPU 7 is now offline
Mar 23 09:35:16 home kernel: IRQ158: set affinity failed(-22).
Mar 23 09:35:16 home kernel: smpboot: CPU 8 is now offline
Mar 23 09:35:16 home kernel: IRQ158: set affinity failed(-22).
Mar 23 09:35:16 home kernel: smpboot: CPU 9 is now offline
Mar 23 09:35:16 home kernel: IRQ158: set affinity failed(-22).
Mar 23 09:35:16 home kernel: smpboot: CPU 10 is now offline
Mar 23 09:35:16 home kernel: smpboot: CPU 11 is now offline
Mar 23 09:35:16 home kernel: smpboot: CPU 12 is now offline
Mar 23 09:35:16 home kernel: smpboot: CPU 13 is now offline
Mar 23 09:35:16 home kernel: smpboot: CPU 14 is now offline
Mar 23 09:35:16 home kernel: smpboot: CPU 15 is now offline
Mar 23 09:35:16 home kernel: PM: hibernation: Creating image:
Mar 23 09:35:16 home kernel: PM: hibernation: Need to copy 1505083 pages
Mar 23 09:35:16 home kernel: PM: hibernation: Normal pages needed: 1505083 + 1024, available pages: 2607587
Mar 23 09:35:16 home kernel: PM: hibernation: Image created (1252312 pages copied, 252771 zero pages)
Mar 23 09:35:16 home kernel: ACPI: PM: Restoring platform NVS memory
Mar 23 09:35:16 home kernel: ACPI: EC: EC started
Mar 23 09:35:16 home kernel: Enabling non-boot CPUs ...
Mar 23 09:35:16 home kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Mar 23 09:35:16 home kernel: CPU1 is up
Mar 23 09:35:16 home kernel: smpboot: Booting Node 0 Processor 2 APIC 0x8
Mar 23 09:35:16 home kernel: CPU2 is up
Mar 23 09:35:16 home kernel: smpboot: Booting Node 0 Processor 3 APIC 0x9
Mar 23 09:35:16 home kernel: CPU3 is up
Mar 23 09:35:16 home kernel: smpboot: Booting Node 0 Processor 4 APIC 0x10
Mar 23 09:35:16 home kernel: CPU4 is up
Mar 23 09:35:16 home kernel: smpboot: Booting Node 0 Processor 5 APIC 0x11
Mar 23 09:35:16 home kernel: CPU5 is up
Mar 23 09:35:16 home kernel: smpboot: Booting Node 0 Processor 6 APIC 0x18
Mar 23 09:35:16 home kernel: CPU6 is up
Mar 23 09:35:16 home kernel: smpboot: Booting Node 0 Processor 7 APIC 0x19
Mar 23 09:35:16 home kernel: CPU7 is up
Mar 23 09:35:16 home kernel: smpboot: Booting Node 0 Processor 8 APIC 0x20
Mar 23 09:35:16 home kernel: core: cpu_atom PMU driver: PEBS-via-PT 
Mar 23 09:35:16 home kernel: ... version:                5
Mar 23 09:35:16 home kernel: ... bit width:              48
Mar 23 09:35:16 home kernel: ... generic registers:      6
Mar 23 09:35:16 home kernel: ... value mask:             0000ffffffffffff
Mar 23 09:35:16 home kernel: ... max period:             00007fffffffffff
Mar 23 09:35:16 home kernel: ... fixed-purpose events:   3
Mar 23 09:35:16 home kernel: ... event mask:             000000070000003f
Mar 23 09:35:16 home kernel: CPU8 is up
Mar 23 09:35:16 home kernel: smpboot: Booting Node 0 Processor 9 APIC 0x22
Mar 23 09:35:16 home kernel: CPU9 is up
Mar 23 09:35:16 home kernel: smpboot: Booting Node 0 Processor 10 APIC 0x24
Mar 23 09:35:16 home kernel: CPU10 is up
Mar 23 09:35:16 home kernel: smpboot: Booting Node 0 Processor 11 APIC 0x26
Mar 23 09:35:16 home kernel: CPU11 is up
Mar 23 09:35:16 home kernel: smpboot: Booting Node 0 Processor 12 APIC 0x28
Mar 23 09:35:16 home kernel: CPU12 is up
Mar 23 09:35:16 home kernel: smpboot: Booting Node 0 Processor 13 APIC 0x2a
Mar 23 09:35:16 home kernel: CPU13 is up
Mar 23 09:35:16 home kernel: smpboot: Booting Node 0 Processor 14 APIC 0x2c
Mar 23 09:35:16 home kernel: CPU14 is up
Mar 23 09:35:16 home kernel: smpboot: Booting Node 0 Processor 15 APIC 0x2e
Mar 23 09:35:16 home kernel: CPU15 is up
Mar 23 09:35:16 home kernel: ACPI: PM: Waking up from system sleep state S4
Mar 23 09:35:16 home kernel: ACPI: EC: interrupt unblocked
Mar 23 09:35:16 home kernel: intel-hid INTC1078:00: unknown event 0xca
Mar 23 09:35:16 home kernel: ACPI: EC: event unblocked
Mar 23 09:35:16 home kernel: pcieport 10000:e0:06.0: can't derive routing for PCI INT A
Mar 23 09:35:16 home kernel: nvme 10000:e1:00.0: PCI INT A: no GSI
Mar 23 09:35:16 home kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.20.0
Mar 23 09:35:16 home kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
Mar 23 09:35:16 home kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
Mar 23 09:35:16 home kernel: nvme nvme0: 16/0/0 default/read/poll queues
Mar 23 09:35:16 home kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
Mar 23 09:35:16 home kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
Mar 23 09:35:16 home kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
Mar 23 09:35:16 home kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
Mar 23 09:35:16 home kernel: iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
Mar 23 09:35:16 home kernel: iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Mar 23 09:35:16 home kernel: iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
Mar 23 09:35:16 home kernel: iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
Mar 23 09:35:16 home kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
Mar 23 09:35:16 home kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Mar 23 09:35:16 home kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
Mar 23 09:35:16 home kernel: PM: Using 3 thread(s) for compression
Mar 23 09:35:16 home kernel: PM: Compressing and saving image data (1255252 pages)...
Mar 23 09:35:16 home kernel: PM: Image saving progress:   0%
Mar 23 09:35:16 home kernel: PM: Image saving progress:  10%
Mar 23 09:35:16 home kernel: PM: Image saving progress:  20%
Mar 23 09:35:16 home kernel: PM: Image saving progress:  30%
Mar 23 09:35:16 home kernel: PM: Image saving progress:  40%
Mar 23 09:35:16 home kernel: PM: Image saving progress:  50%
Mar 23 09:35:16 home kernel: PM: Image saving progress:  60%
Mar 23 09:35:16 home kernel: PM: Image saving progress:  70%
Mar 23 09:35:16 home kernel: PM: Image saving progress:  80%
Mar 23 09:35:16 home kernel: PM: Image saving progress:  90%
Mar 23 09:35:16 home kernel: PM: Image saving progress: 100%
Mar 23 09:35:16 home kernel: PM: Image saving done
Mar 23 09:35:16 home kernel: PM: hibernation: Wrote 5021008 kbytes in 3.58 seconds (1402.51 MB/s)
Mar 23 09:35:16 home kernel: PM: S|
Mar 23 09:35:16 home kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 23 09:35:16 home kernel: PM: hibernation: Wakeup event detected during hibernation, rolling back.
Mar 23 09:35:16 home kernel: PM: hibernation: Basic memory bitmaps freed
Mar 23 09:35:16 home kernel: OOM killer enabled.
Mar 23 09:35:16 home kernel: Restarting tasks ... done.
Mar 23 09:35:16 home rtkit-daemon[784]: The canary thread is apparently starving. Taking action.
Mar 23 09:35:16 home rtkit-daemon[784]: Demoting known real-time threads.
Mar 23 09:35:16 home rtkit-daemon[784]: Successfully demoted thread 1276 of process 1162.
Mar 23 09:35:16 home rtkit-daemon[784]: Successfully demoted thread 1268 of process 1162.
Mar 23 09:35:16 home rtkit-daemon[784]: Successfully demoted thread 1264 of process 1162.
Mar 23 09:35:16 home rtkit-daemon[784]: Successfully demoted thread 1262 of process 1162.
Mar 23 09:35:16 home rtkit-daemon[784]: Successfully demoted thread 1260 of process 1162.
Mar 23 09:35:16 home rtkit-daemon[784]: Successfully demoted thread 1258 of process 1162.
Mar 23 09:35:16 home rtkit-daemon[784]: Successfully demoted thread 1162 of process 1162.
Mar 23 09:35:16 home rtkit-daemon[784]: Successfully demoted thread 819 of process 819.
Mar 23 09:35:16 home rtkit-daemon[784]: Successfully demoted thread 822 of process 810.
Mar 23 09:35:16 home rtkit-daemon[784]: Successfully demoted thread 810 of process 810.
Mar 23 09:35:16 home rtkit-daemon[784]: Demoted 10 threads.
Mar 23 09:35:16 home kernel: PM: hibernation: hibernation exit
Mar 23 09:35:16 home systemd-sleep[11454]: System returned from sleep operation 'hibernate'.
Mar 23 09:35:16 home systemd[1]: systemd-hibernate.service: Deactivated successfully.
Mar 23 09:35:16 home systemd[1]: Finished System Hibernate.
Mar 23 09:35:16 home systemd[1]: systemd-hibernate.service: Consumed 2.982s CPU time.
Mar 23 09:35:16 home systemd[1]: Reached target System Hibernation.
Mar 23 09:35:16 home systemd[1]: Stopped target Sleep.
Mar 23 09:35:16 home systemd-logind[435]: Operation 'hibernate' finished.
Mar 23 09:35:16 home systemd[1]: Stopped target System Hibernation.
Mar 23 09:35:16 home NetworkManager[433]: <info>  [1711166716.5923] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Mar 23 09:35:16 home NetworkManager[433]: <info>  [1711166716.5925] device (wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Mar 23 09:35:16 home kdeconnectd[1105]: 2024-03-23T09:35:16 default: Error sending UDP packet: QAbstractSocket::NetworkError
Mar 23 09:35:16 home kdeconnectd[1105]: 2024-03-23T09:35:16 kdeconnect.core: Failed to open any MDNS client sockets
Mar 23 09:35:16 home kdeconnectd[1105]: 2024-03-23T09:35:16 kdeconnect.core: Failed to open any MDNS server sockets
Mar 23 09:35:16 home NetworkManager[433]: <info>  [1711166716.5940] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Mar 23 09:35:16 home NetworkManager[433]: <info>  [1711166716.5942] manager: NetworkManager state is now DISCONNECTED
Mar 23 09:35:16 home NetworkManager[433]: <info>  [1711166716.6456] device (wlp0s20f3): supplicant interface state: internal-starting -> disconnected
Mar 23 09:35:16 home NetworkManager[433]: <info>  [1711166716.6457] device (p2p-dev-wlp0s20f3): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Mar 23 09:35:16 home NetworkManager[433]: <info>  [1711166716.6461] Wi-Fi P2P device controlled by interface wlp0s20f3 created
Mar 23 09:35:16 home NetworkManager[433]: <info>  [1711166716.6463] manager: (p2p-dev-wlp0s20f3): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/7)
Mar 23 09:35:16 home NetworkManager[433]: <info>  [1711166716.6464] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Mar 23 09:35:16 home NetworkManager[433]: <info>  [1711166716.6467] device (wlp0s20f3): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Mar 23 09:35:16 home NetworkManager[433]: <info>  [1711166716.6471] device (p2p-dev-wlp0s20f3): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Mar 23 09:35:18 home systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 23 09:35:20 home wpa_supplicant[570]: wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4603] policy: auto-activating connection 'Jio_1' (442da66b-c354-4cfa-bbf8-cc7dfedb7470)
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4609] device (wlp0s20f3): Activation: starting connection 'Jio_1' (442da66b-c354-4cfa-bbf8-cc7dfedb7470)
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4610] device (wlp0s20f3): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4613] manager: NetworkManager state is now CONNECTING
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4615] device (wlp0s20f3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4620] device (wlp0s20f3): Activation: (wifi) access point 'Jio_1' has security, but secrets are required.
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4620] device (wlp0s20f3): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4635] device (wlp0s20f3): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4637] device (wlp0s20f3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4640] device (wlp0s20f3): Activation: (wifi) connection 'Jio_1' has security, and secrets exist.  No new secrets needed.
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4640] Config: added 'ssid' value 'Jio_1'
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4640] Config: added 'scan_ssid' value '1'
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4640] Config: added 'bgscan' value 'simple:30:-65:300'
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4640] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4640] Config: added 'auth_alg' value 'OPEN'
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4641] Config: added 'psk' value '<hidden>'
Mar 23 09:35:20 home wpa_supplicant[570]: wlp0s20f3: SME: Trying to authenticate with 82:2a:a8:39:20:12 (SSID='Jio_1' freq=2462 MHz)
Mar 23 09:35:20 home kernel: wlp0s20f3: 80 MHz not supported, disabling VHT
Mar 23 09:35:20 home kded6[883]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId"
Mar 23 09:35:20 home plasmashell[930]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId"
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4808] device (wlp0s20f3): supplicant interface state: disconnected -> authenticating
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.4808] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> authenticating
Mar 23 09:35:20 home kernel: wlp0s20f3: authenticate with 82:2a:a8:39:20:12 (local address=f0:20:ff:b9:6a:1d)
Mar 23 09:35:20 home kernel: wlp0s20f3: send auth to 82:2a:a8:39:20:12 (try 1/3)
Mar 23 09:35:20 home wpa_supplicant[570]: wlp0s20f3: Trying to associate with 82:2a:a8:39:20:12 (SSID='Jio_1' freq=2462 MHz)
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.5237] device (wlp0s20f3): supplicant interface state: authenticating -> associating
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.5238] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating
Mar 23 09:35:20 home kernel: wlp0s20f3: authenticated
Mar 23 09:35:20 home kernel: wlp0s20f3: associate with 82:2a:a8:39:20:12 (try 1/3)
Mar 23 09:35:20 home kernel: wlp0s20f3: RX AssocResp from 82:2a:a8:39:20:12 (capab=0x431 status=0 aid=1)
Mar 23 09:35:20 home wpa_supplicant[570]: wlp0s20f3: Associated with 82:2a:a8:39:20:12
Mar 23 09:35:20 home kernel: wlp0s20f3: associated
Mar 23 09:35:20 home wpa_supplicant[570]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.5498] device (wlp0s20f3): supplicant interface state: associating -> 4way_handshake
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.5499] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> 4way_handshake
Mar 23 09:35:20 home wpa_supplicant[570]: wlp0s20f3: WPA: Key negotiation completed with 82:2a:a8:39:20:12 [PTK=CCMP GTK=CCMP]
Mar 23 09:35:20 home wpa_supplicant[570]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to 82:2a:a8:39:20:12 completed [id=0 id_str=]
Mar 23 09:35:20 home dhcpcd[437]: wlp0s20f3: carrier acquired
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.6299] device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.6300] device (wlp0s20f3): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Jio_1"
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.6300] device (p2p-dev-wlp0s20f3): supplicant management interface state: 4way_handshake -> completed
Mar 23 09:35:20 home wpa_supplicant[570]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-43 noise=9999 txrate=52000
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.6303] device (wlp0s20f3): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.6308] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
Mar 23 09:35:20 home dhcpcd[437]: wlp0s20f3: IAID ff:b9:6a:1d
Mar 23 09:35:20 home dhcpcd[437]: wlp0s20f3: adding address fe80::e3d9:3eb8:fbc3:74d2
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.6407] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.29.135, acd pending
Mar 23 09:35:20 home dhcpcd[437]: wlp0s20f3: soliciting an IPv6 router
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.8214] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.29.135
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.8226] policy: set 'Jio_1' (wlp0s20f3) as default for IPv4 routing and DNS
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.8395] device (wlp0s20f3): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 23 09:35:20 home systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 23 09:35:20 home systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.9068] device (wlp0s20f3): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.9070] device (wlp0s20f3): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.9074] manager: NetworkManager state is now CONNECTED_SITE
Mar 23 09:35:20 home NetworkManager[433]: <info>  [1711166720.9103] device (wlp0s20f3): Activation: successful, device activated.
Mar 23 09:35:21 home NetworkManager[433]: <info>  [1711166721.2389] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 23 09:35:21 home kdeconnectd[1105]: 2024-03-23T09:35:21 kdeconnect.core: Failed to send mDNS query: Cannot assign requested address
Mar 23 09:35:21 home kdeconnectd[1105]: 2024-03-23T09:35:21 kdeconnect.core: Failed to send mDNS query: Cannot assign requested address
Mar 23 09:35:21 home dhcpcd[437]: wlp0s20f3: rebinding lease of 192.168.29.134
Mar 23 09:35:21 home dhcpcd[437]: wlp0s20f3: probing address 192.168.29.134/24
Mar 23 09:35:21 home dhcpcd[437]: wlp0s20f3: Router Advertisement from fe80::1a82:8cff:fefc:22fd
Mar 23 09:35:21 home dhcpcd[437]: wlp0s20f3: adding address 2405:201:12:3dae:fef4:a3d4:1b8a:7f2e/64
Mar 23 09:35:21 home dhcpcd[437]: wlp0s20f3: adding route to 2405:201:12:3dae::/64
Mar 23 09:35:21 home dhcpcd[437]: wlp0s20f3: requesting DHCPv6 information
Mar 23 09:35:21 home dhcpcd[437]: wlp0s20f3: adding default route via fe80::1a82:8cff:fefc:22fd
Mar 23 09:35:22 home dhcpcd[437]: wlp0s20f3: REPLY6 received from fe80::1a82:8cff:fefc:22fd
Mar 23 09:35:22 home dhcpcd[437]: wlp0s20f3: refresh in 86400 seconds
Mar 23 09:35:24 home kscreenlocker_greet[11358]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000)
Mar 23 09:35:24 home kscreenlocker_greet[11358]: Failed to write to the pipe: Bad file descriptor.
Mar 23 09:35:25 home kernel: IPv6: MLD: clamping QRV from 1 to 2!
Mar 23 09:35:26 home dhcpcd[437]: wlp0s20f3: leased 192.168.29.134 for 86400 seconds
Mar 23 09:35:26 home dhcpcd[437]: wlp0s20f3: adding route to 192.168.29.0/24
Mar 23 09:35:26 home dhcpcd[437]: wlp0s20f3: adding default route via 192.168.29.1
Mar 23 09:35:28 home NetworkManager[433]: <info>  [1711166728.5746] dhcp6 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
Mar 23 09:35:28 home NetworkManager[433]: <info>  [1711166728.5749] dhcp6 (wlp0s20f3): canceled DHCP transaction
Mar 23 09:35:28 home NetworkManager[433]: <info>  [1711166728.5749] dhcp6 (wlp0s20f3): state changed no lease
Mar 23 09:35:28 home NetworkManager[433]: <info>  [1711166728.5752] policy: set 'Jio_1' (wlp0s20f3) as default for IPv6 routing and DNS
Mar 23 09:35:30 home systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

Last edited by aaditmshah (2024-03-23 04:19:12)

seth · 2024-03-23 07:55:24

Yes, I am dual booting Arch Linux and Windows.

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

TXHC      S4    *enabled   pci:0000:00:0d.0
TDM0      S4    *enabled   pci:0000:00:0d.2
TRP0      S4    *enabled   pci:0000:00:07.0
AWAC      S4    *enabled   platform:ACPI000E:00

lspci -tvnn

to see what is on those būs and certainly (try to) disable AWAC

Are you using dhpcd as NM backend?
Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

aaditmshah · 2024-03-24 04:55:45

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

I disabled fast startup and hibernation on Windows.

TXHC      S4    *enabled   pci:0000:00:0d.0
TDM0      S4    *enabled   pci:0000:00:0d.2
TRP0      S4    *enabled   pci:0000:00:07.0
AWAC      S4    *enabled   platform:ACPI000E:00

lspci -tvnn

to see what is on those būs and certainly (try to) disable AWAC

Here's the output of lspci. I temporarily disabled AWAC after disabling fast startup on Windows and tried hibernating, but it still wakes up.

-[0000:00]-+-00.0  Intel Corporation Raptor Lake-P/U 4p+8e cores Host Bridge/DRAM Controller [8086:a707]
           +-02.0  Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a0]
           +-04.0  Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant [8086:a71d]
           +-06.0  Intel Corporation RST VMD Managed Controller [8086:09ab]
           +-07.0-[01-38]--
           +-08.0  Intel Corporation GNA Scoring Accelerator module [8086:a74f]
           +-0d.0  Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller [8086:a71e]
           +-0d.2  Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #0 [8086:a73e]
           +-0e.0  Intel Corporation Volume Management Device NVMe RAID Controller Intel Corporation [8086:a77f]
           +-12.0  Intel Corporation Alder Lake-P Integrated Sensor Hub [8086:51fc]
           +-14.0  Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller [8086:51ed]
           +-14.2  Intel Corporation Alder Lake PCH Shared SRAM [8086:51ef]
           +-14.3  Intel Corporation Raptor Lake PCH CNVi WiFi [8086:51f1]
           +-15.0  Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 [8086:51e8]
           +-15.1  Intel Corporation Alder Lake PCH Serial IO I2C Controller #1 [8086:51e9]
           +-16.0  Intel Corporation Alder Lake PCH HECI Controller [8086:51e0]
           +-1f.0  Intel Corporation Raptor Lake LPC/eSPI Controller [8086:519d]
           +-1f.3  Intel Corporation Raptor Lake-P/U/H cAVS [8086:51ca]
           +-1f.4  Intel Corporation Alder Lake PCH-P SMBus Host Controller [8086:51a3]
           \-1f.5  Intel Corporation Alder Lake-P PCH SPI Controller [8086:51a4]
-[10000:e0]---06.0-[e1]----00.0  KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) [1e0f:000c]

Are you using dhpcd as NM backend?
Please post the output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Here's the output of the command.

bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
dhcpcd.service                           | multi-user.target.wants
display-manager.service                  | system
getty@tty1.service                       | getty.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

By the way, if Windows is causing an issue then I don't mind formatting it. I never use Windows anyway.

seth · 2024-03-24 08:22:56

A hibernating windows (the voodoo dance there is btw. not a joke, it has multiple times be suggested to be a necessary step and there's at least one report of 3 required reboots…) is a general issue and in proximity to your problem, just having windows on a disk only wastes disk space

* Disable dhcpcd, it'sll collide w/ NM
* TXHC & TDM0 are thunderbolt (data and display) - just disable them for wakeup
* TRP0 is "+-07.0-[01-38]--" looks weird, the "device" is a trap monitor (is this a macbook?)
=> Disable them along AWAC

Last edited by seth (2024-03-24 08:23:05)

nihil21 · 2024-03-24 11:02:19

This issue is not related to dual-booting Windows: I have it installed, but hibernation worked fine until recently. I did some testing, and it may be a kernel bug:
- with 6.6.22-1-lts everything works fine;
- with 6.8.1.arch1-1, hibernation fails with "Wakeup event detected during hibernation, rolling back" error.

aaditmshah · 2024-03-24 11:28:08

I disabled all the four wakeup triggers, i.e. TXHC, TDM0, TRP0, and AWAC, I disabled dhcpcd, and I also disabled Windows fast startup and hibernation. However, the problem still persists.

aaditmshah · 2024-03-24 11:31:08

nihil21 wrote:

This issue is not related to dual-booting Windows: I have it installed, but hibernation worked fine until recently. I did some testing, and it may be a kernel bug:
- with 6.6.22-1-lts everything works fine;
- with 6.8.1.arch1-1, hibernation fails with "Wakeup event detected during hibernation, rolling back" error.

That's good to know. I am indeed using kernel version 6.8.1-arch1-1.

nihil21 · 2024-03-24 11:51:00

I opened a bug report here: https://bugzilla.kernel.org/show_bug.cgi?id=218634

seth · 2024-03-24 14:03:43

Shot in the dark since S3 isn't affected: https://wiki.archlinux.org/title/Solid_ … leshooting
"nvme_core.default_ps_max_latency_us=0 iommu=soft"

shuruper · 2024-04-15 21:09:17

I have the same exact problem with a small addition: after a failed hibernation, any attempt to reboot or shutdown freezes the system (journalctl tells that system is shut down while it's hanging).

There is some activity here: https://bugzilla.kernel.org/show_bug.cgi?id=218634 . Can anyone make sense of it? They claim to have solve the issue, but I have no idea what are they talking about.

seth · 2024-04-15 21:14:54

Closer to the root cause seems to be a kind of spurious 0xCF (power button up) event from the Intel 5 button device that seems to be generated / handled / whatever when the actual hibernation state is entered through platform / ACPI methods.

https://bugzilla.kernel.org/attachment. … ction=diff

I compiled intel-hid.ko for both 6.8.4 and 6.8.5 with this patch applied on OpenSuSE Tumbleweed and it seems to work. I can hibernate.

shuruper · 2024-04-19 16:40:41

It seems like the problem is fixed in the latest kernel update (6.8.7). I can hibernate again.

Arch Linux

#1 2024-03-22 17:29:27

My system wakes up immediately from hibernation

#2 2024-03-22 19:54:12

Re: My system wakes up immediately from hibernation

#3 2024-03-23 04:08:37

Re: My system wakes up immediately from hibernation

#4 2024-03-23 07:55:24

Re: My system wakes up immediately from hibernation

#5 2024-03-24 04:55:45

Re: My system wakes up immediately from hibernation

#6 2024-03-24 08:22:56

Re: My system wakes up immediately from hibernation

#7 2024-03-24 11:02:19

Re: My system wakes up immediately from hibernation

#8 2024-03-24 11:28:08

Re: My system wakes up immediately from hibernation

#9 2024-03-24 11:31:08

Re: My system wakes up immediately from hibernation

#10 2024-03-24 11:51:00

Re: My system wakes up immediately from hibernation

#11 2024-03-24 14:03:43

Re: My system wakes up immediately from hibernation

#12 2024-04-15 21:09:17

Re: My system wakes up immediately from hibernation

#13 2024-04-15 21:14:54

Re: My system wakes up immediately from hibernation

#14 2024-04-19 16:40:41

Re: My system wakes up immediately from hibernation

Board footer