You are not logged in.
Pages: 1
Hi. I have a Thinkpad X! Carbon Generation 8 that sometimes wakes immediately after suspend. It seems like Bluetooth is somehow cancelling the suspend process from the dmesg[ logs:
[ 96.134235] wlp0s20f3: deauthenticating from 58:19:f8:f2:0a:c4 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 101.198038] PM: suspend entry (s2idle)
[ 101.210269] Filesystems sync: 0.012 seconds
[ 101.585267] Bluetooth: hci0: Suspend notifier action (3) failed: 2
[ 101.585281] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 101.587656] OOM killer disabled.
[ 101.587658] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 101.588933] printk: Suspending console(s) (use no_console_suspend to debug)
[ 101.641627] e1000e: EEE TX LPI TIMER: 00000011
[ 101.642314] intel_pch_thermal 0000:00:12.0: CPU-PCH is cool [47C], continue to suspend
[ 103.226467] ACPI: EC: interrupt blocked
[ 104.490760] ACPI: EC: interrupt unblocked
[ 106.162629] OOM killer enabled.
[ 106.162633] Restarting tasks ... done.
[ 106.207452] PM: suspend exitThe only thing remotely similar to this issue I can find on the web is this old kernel patch: https://patchwork.kernel.org/project/li … @changeid/
I assume this patch has been applied, in the 5.17.5-arch1 kernel I'm running, so I'm pretty stumped.
Does anyone know how to fix this to allow the machine to suspend successfully?
Last edited by zonotope (2022-05-01 19:53:09)
Offline
I've been having a similar problem lately on my Razer Blade Advanced. I cannot enter s3 sleep. As soon as the computer goes to sleep, it wakes back up. I think this is related to a recent kernel update. I have very similar journald messages as you but I'm not sure this is related to Bluetooth:
[Wed May 4 21:55:43 2022] PM: suspend entry (deep)
[Wed May 4 21:55:43 2022] Filesystems sync: 0.009 seconds
[Wed May 4 21:55:44 2022] Freezing user space processes ... (elapsed 0.001 seconds) done.
[Wed May 4 21:55:44 2022] OOM killer disabled.
[Wed May 4 21:55:44 2022] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[Wed May 4 21:55:44 2022] printk: Suspending console(s) (use no_console_suspend to debug)
[Wed May 4 21:55:45 2022] ACPI: EC: interrupt blocked
[Wed May 4 21:55:46 2022] ACPI: PM: Preparing to enter system sleep state S3
[Wed May 4 21:55:46 2022] ACPI: EC: event blocked
[Wed May 4 21:55:46 2022] ACPI: EC: EC stopped
[Wed May 4 21:55:46 2022] ACPI: PM: Saving platform NVS memory
[Wed May 4 21:55:46 2022] Disabling non-boot CPUs ...
[Wed May 4 21:55:46 2022] smpboot: CPU 1 is now offline
[Wed May 4 21:55:46 2022] smpboot: CPU 2 is now offline
[Wed May 4 21:55:46 2022] smpboot: CPU 3 is now offline
[Wed May 4 21:55:46 2022] smpboot: CPU 4 is now offline
[Wed May 4 21:55:46 2022] smpboot: CPU 5 is now offline
[Wed May 4 21:55:46 2022] smpboot: CPU 6 is now offline
[Wed May 4 21:55:46 2022] smpboot: CPU 7 is now offline
[Wed May 4 21:55:46 2022] smpboot: CPU 8 is now offline
[Wed May 4 21:55:46 2022] smpboot: CPU 9 is now offline
[Wed May 4 21:55:46 2022] smpboot: CPU 10 is now offline
[Wed May 4 21:55:46 2022] smpboot: CPU 11 is now offline
[Wed May 4 21:55:46 2022] smpboot: CPU 12 is now offline
[Wed May 4 21:55:46 2022] smpboot: CPU 13 is now offline
[Wed May 4 21:55:46 2022] smpboot: CPU 14 is now offline
[Wed May 4 21:55:46 2022] smpboot: CPU 15 is now offline
[Wed May 4 21:55:46 2022] ACPI: PM: Low-level resume complete
[Wed May 4 21:55:46 2022] ACPI: EC: EC started
[Wed May 4 21:55:46 2022] ACPI: PM: Restoring platform NVS memory
[Wed May 4 21:55:46 2022] Enabling non-boot CPUs ...
[Wed May 4 21:55:46 2022] x86: Booting SMP configuration:
[Wed May 4 21:55:46 2022] smpboot: Booting Node 0 Processor 1 APIC 0x2
[Wed May 4 21:55:46 2022] CPU1 is up
[Wed May 4 21:55:46 2022] smpboot: Booting Node 0 Processor 2 APIC 0x4
[Wed May 4 21:55:46 2022] CPU2 is up
[Wed May 4 21:55:46 2022] smpboot: Booting Node 0 Processor 3 APIC 0x6
[Wed May 4 21:55:46 2022] CPU3 is up
[Wed May 4 21:55:46 2022] smpboot: Booting Node 0 Processor 4 APIC 0x8
[Wed May 4 21:55:46 2022] CPU4 is up
[Wed May 4 21:55:46 2022] smpboot: Booting Node 0 Processor 5 APIC 0xa
[Wed May 4 21:55:46 2022] CPU5 is up
[Wed May 4 21:55:46 2022] smpboot: Booting Node 0 Processor 6 APIC 0xc
[Wed May 4 21:55:46 2022] CPU6 is up
[Wed May 4 21:55:46 2022] smpboot: Booting Node 0 Processor 7 APIC 0xe
[Wed May 4 21:55:46 2022] CPU7 is up
[Wed May 4 21:55:46 2022] smpboot: Booting Node 0 Processor 8 APIC 0x1
[Wed May 4 21:55:46 2022] CPU8 is up
[Wed May 4 21:55:46 2022] smpboot: Booting Node 0 Processor 9 APIC 0x3
[Wed May 4 21:55:46 2022] CPU9 is up
[Wed May 4 21:55:46 2022] smpboot: Booting Node 0 Processor 10 APIC 0x5
[Wed May 4 21:55:46 2022] CPU10 is up
[Wed May 4 21:55:46 2022] smpboot: Booting Node 0 Processor 11 APIC 0x7
[Wed May 4 21:55:46 2022] CPU11 is up
[Wed May 4 21:55:46 2022] smpboot: Booting Node 0 Processor 12 APIC 0x9
[Wed May 4 21:55:46 2022] CPU12 is up
[Wed May 4 21:55:46 2022] smpboot: Booting Node 0 Processor 13 APIC 0xb
[Wed May 4 21:55:46 2022] CPU13 is up
[Wed May 4 21:55:46 2022] smpboot: Booting Node 0 Processor 14 APIC 0xd
[Wed May 4 21:55:46 2022] CPU14 is up
[Wed May 4 21:55:46 2022] smpboot: Booting Node 0 Processor 15 APIC 0xf
[Wed May 4 21:55:46 2022] CPU15 is up
[Wed May 4 21:55:46 2022] ACPI: PM: Waking up from system sleep state S3
[Wed May 4 21:55:46 2022] ACPI Error: No handler for Region [VRTC] (00000000c6830abc) [SystemCMOS] (20211217/evregion-130)
[Wed May 4 21:55:46 2022] ACPI Error: Region SystemCMOS (ID=5) has no handler (20211217/exfldio-261)
[Wed May 4 21:55:46 2022] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC0.RTEC due to previous error (AE_NOT_EXIST) (20211217/psparse-529)
[Wed May 4 21:55:46 2022] ACPI Error: Aborting method \RWAK due to previous error (AE_NOT_EXIST) (20211217/psparse-529)
[Wed May 4 21:55:46 2022] ACPI Error: Aborting method \_WAK due to previous error (AE_NOT_EXIST) (20211217/psparse-529)
[Wed May 4 21:55:46 2022] ACPI Error: AE_NOT_EXIST, While executing method \_WAK (20211217/hwesleep-47)
[Wed May 4 21:55:46 2022] ACPI: EC: interrupt unblocked
[Wed May 4 21:55:47 2022] ACPI: EC: event unblocked
[Wed May 4 21:55:47 2022] i915 0000:00:02.0: [drm] [ENCODER:94:DDI A/PHY A] is disabled/in DSI mode with an ungated DDI clock, gate it
[Wed May 4 21:55:47 2022] nvme nvme0: Shutdown timeout set to 10 seconds
[Wed May 4 21:55:47 2022] nvme nvme0: 16/0/0 default/read/poll queues
[Wed May 4 21:55:47 2022] usb 1-7: reset high-speed USB device number 2 using xhci_hcd
[Wed May 4 21:55:47 2022] xhci_hcd 0000:01:00.2: xHC error in resume, USBSTS 0x401, Reinit
[Wed May 4 21:55:47 2022] usb usb3: root hub lost power or was reset
[Wed May 4 21:55:47 2022] usb usb4: root hub lost power or was reset
[Wed May 4 21:55:48 2022] OOM killer enabled.
[Wed May 4 21:55:48 2022] Restarting tasks ...
[Wed May 4 21:55:48 2022] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[Wed May 4 21:55:48 2022] done.
[Wed May 4 21:55:48 2022] ACPI: battery: [Firmware Bug]: (dis)charge rate invalid.
[Wed May 4 21:55:48 2022] PM: suspend exitOffline
Looks like it is kernel related. I was on kernel 5.17.5. I reinstalled linux 5.16.16 and the problem has gone away. I can now enter s3 sleep without it waking back up right away.
Oddly enough, my dmesg entries are nearly identical between suspending and resuming on both kernel versions so I can't really see what the culprit is here.
PS: To install an older version of the kernel, you can do so from the pacman cache:
pacman -U /var/cache/pacman/pkg/{linux-5.16.16.arch1-1-x86_64.pkg.tar.zst,linux-headers-5.16.16.arch1-1-x86_64.pkg.tar.zst}Last edited by Mike616 (2022-05-05 05:48:17)
Offline
I'm still seeing this problem with 5.17.9 and 5.18.0. I'm currently pinning linux and linux-headers to 5.16.16. Anyone have any suggestions?
Last edited by Mike616 (2022-06-11 08:05:21)
Offline
Pages: 1