Computer wakes up right after suspending

Ex0Matter · 2021-11-02 07:17:19

I've been having a problem where anytime I try to suspend the computer (mainly from GNOME's power options), it'll turn off then immediately wake back up. This problem occurred even before I switched from Fedora 34. I followed the wiki entry here to no avail; it doesn't seem like any USB devices (or really any devices) are sending a wakeup signal, so I'm confused to why this is happening. One thing to note is that I do have an NVIDIA graphics card (running 495.44) and have been having problems related to screen blanking and GNOME, which I suspect could be a possible culprit, but am not sure how to trace down. Something happens when my primary screen turns back on - from suspend or automatic blanking - where a bunch of artifacting and vertical lines appear on my primary monitor. So far my solution has just been to unplug my monitor and reconnect and hope it doesn't happen again.

Here is the output of "cat /proc/acpi/wakeup":

Device	S-state	  Status   Sysfs node
GPP0	  S4	*enabled   pci:0000:00:01.1
GPP1	  S4	*disabled
GPP3	  S4	*disabled
GPP4	  S4	*disabled
GPP5	  S4	*disabled
GPP6	  S4	*disabled
GPP7	  S4	*disabled
X161	  S4	*disabled  pci:0000:0b:00.0
X162	  S4	*disabled
GPPA	  S4	*disabled
GPPB	  S4	*disabled
GPPC	  S4	*disabled
GPPD	  S4	*disabled
GPPE	  S4	*disabled
GPPF	  S4	*disabled
GP10	  S4	*disabled
GP11	  S4	*disabled
GP12	  S4	*enabled   pci:0000:00:07.1
GP13	  S4	*enabled   pci:0000:00:08.1
XHC0	  S4	*enabled   pci:0000:0d:00.3
GP30	  S4	*disabled
GP31	  S4	*disabled
PS2K	  S3	*disabled
PS2M	  S3	*disabled
UAR1	  S4	*disabled  pnp:00:04
GPP2	  S4	*enabled   pci:0000:00:01.3
X4_0	  S4	*disabled
X4_1	  S4	*disabled
X411	  S4	*disabled
X413	  S4	*disabled  pci:0000:06:00.0
AS42	  S4	*enabled   pci:0000:07:00.0
X412	  S4	*disabled
I211	  S4	*enabled   pci:0000:09:00.0
PTXH	  S4	*enabled   pci:0000:02:00.0

Here is a screenshot of "dmesg -w" when I suspended:

[ 8135.676524] wlp6s0: deauthenticating from 18:31:bf:ad:4c:9c by local choice (Reason: 3=DEAUTH_LEAVING)
[ 8138.905504] PM: suspend entry (deep)
[ 8138.934037] Filesystems sync: 0.028 seconds
[ 8139.467758] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 8139.470116] OOM killer disabled.
[ 8139.470117] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 8139.471285] printk: Suspending console(s) (use no_console_suspend to debug)
[ 8139.475603] serial 00:04: disabled
[ 8139.513131] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 8139.513142] sd 4:0:0:0: [sdb] Synchronizing SCSI cache
[ 8139.516932] sd 0:0:0:0: [sda] Stopping disk
[ 8139.516956] sd 4:0:0:0: [sdb] Stopping disk
[ 8139.528427] sd 8:0:0:0: [sdc] Synchronizing SCSI cache
[ 8139.871614] ACPI: EC: interrupt blocked
[ 8139.938816] ACPI: PM: Preparing to enter system sleep state S3
[ 8140.249240] ACPI: EC: event blocked
[ 8140.249242] ACPI: EC: EC stopped
[ 8140.249243] ACPI: PM: Saving platform NVS memory
[ 8140.249293] Disabling non-boot CPUs ...
[ 8140.250932] IRQ 88: no longer affine to CPU1
[ 8140.251964] smpboot: CPU 1 is now offline
[ 8140.254414] IRQ 89: no longer affine to CPU2
[ 8140.255434] smpboot: CPU 2 is now offline
[ 8140.257138] IRQ 90: no longer affine to CPU3
[ 8140.258239] smpboot: CPU 3 is now offline
[ 8140.260313] IRQ 91: no longer affine to CPU4
[ 8140.261327] smpboot: CPU 4 is now offline
[ 8140.263144] IRQ 92: no longer affine to CPU5
[ 8140.264163] smpboot: CPU 5 is now offline
[ 8140.266128] IRQ 93: no longer affine to CPU6
[ 8140.267143] smpboot: CPU 6 is now offline
[ 8140.269097] IRQ 94: no longer affine to CPU7
[ 8140.270117] smpboot: CPU 7 is now offline
[ 8140.271267] IRQ 95: no longer affine to CPU8
[ 8140.272412] smpboot: CPU 8 is now offline
[ 8140.274179] IRQ 96: no longer affine to CPU9
[ 8140.275277] smpboot: CPU 9 is now offline
[ 8140.277489] IRQ 97: no longer affine to CPU10
[ 8140.278511] smpboot: CPU 10 is now offline
[ 8140.280934] smpboot: CPU 11 is now offline
[ 8140.283321] smpboot: CPU 12 is now offline
[ 8140.286086] smpboot: CPU 13 is now offline
[ 8140.288884] smpboot: CPU 14 is now offline
[ 8140.291537] smpboot: CPU 15 is now offline
[ 8140.293002] ACPI: PM: Low-level resume complete
[ 8140.293038] ACPI: EC: EC started
[ 8140.293038] ACPI: PM: Restoring platform NVS memory
[ 8140.293184] LVT offset 0 assigned for vector 0x400
[ 8140.293669] Enabling non-boot CPUs ...
[ 8140.293719] x86: Booting SMP configuration:
[ 8140.293719] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 8140.293856] microcode: CPU1: patch_level=0x08701021
[ 8140.296538] ACPI: \_PR_.C002: Found 2 idle states
[ 8140.299266] CPU1 is up
[ 8140.299305] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ 8140.299445] microcode: CPU2: patch_level=0x08701021
[ 8140.301698] ACPI: \_PR_.C004: Found 2 idle states
[ 8140.302627] CPU2 is up
[ 8140.302660] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ 8140.302788] microcode: CPU3: patch_level=0x08701021
[ 8140.305032] ACPI: \_PR_.C006: Found 2 idle states
[ 8140.305963] CPU3 is up
[ 8140.305982] smpboot: Booting Node 0 Processor 4 APIC 0x8
[ 8140.306132] microcode: CPU4: patch_level=0x08701021
[ 8140.308405] ACPI: \_PR_.C008: Found 2 idle states
[ 8140.309387] CPU4 is up
[ 8140.309409] smpboot: Booting Node 0 Processor 5 APIC 0xa
[ 8140.309571] microcode: CPU5: patch_level=0x08701021
[ 8140.311821] ACPI: \_PR_.C00A: Found 2 idle states
[ 8140.312744] CPU5 is up
[ 8140.312768] smpboot: Booting Node 0 Processor 6 APIC 0xc
[ 8140.312932] microcode: CPU6: patch_level=0x08701021
[ 8140.315196] ACPI: \_PR_.C00C: Found 2 idle states
[ 8140.316130] CPU6 is up
[ 8140.316154] smpboot: Booting Node 0 Processor 7 APIC 0xe
[ 8140.316321] microcode: CPU7: patch_level=0x08701021
[ 8140.318574] ACPI: \_PR_.C00E: Found 2 idle states
[ 8140.319497] CPU7 is up
[ 8140.319520] smpboot: Booting Node 0 Processor 8 APIC 0x1
[ 8140.319692] microcode: CPU8: patch_level=0x08701021
[ 8140.321955] ACPI: \_PR_.C001: Found 2 idle states
[ 8140.323024] CPU8 is up
[ 8140.323058] smpboot: Booting Node 0 Processor 9 APIC 0x3
[ 8140.323207] microcode: CPU9: patch_level=0x08701021
[ 8140.325457] ACPI: \_PR_.C003: Found 2 idle states
[ 8140.326305] CPU9 is up
[ 8140.326328] smpboot: Booting Node 0 Processor 10 APIC 0x5
[ 8140.326474] microcode: CPU10: patch_level=0x08701021
[ 8140.328718] ACPI: \_PR_.C005: Found 2 idle states
[ 8140.329828] CPU10 is up
[ 8140.329849] smpboot: Booting Node 0 Processor 11 APIC 0x7
[ 8140.329991] microcode: CPU11: patch_level=0x08701021
[ 8140.332230] ACPI: \_PR_.C007: Found 2 idle states
[ 8140.333149] CPU11 is up
[ 8140.333169] smpboot: Booting Node 0 Processor 12 APIC 0x9
[ 8140.333334] microcode: CPU12: patch_level=0x08701021
[ 8140.335588] ACPI: \_PR_.C009: Found 2 idle states
[ 8140.336850] CPU12 is up
[ 8140.336870] smpboot: Booting Node 0 Processor 13 APIC 0xb
[ 8140.337055] microcode: CPU13: patch_level=0x08701021
[ 8140.339322] ACPI: \_PR_.C00B: Found 2 idle states
[ 8140.340363] CPU13 is up
[ 8140.340385] smpboot: Booting Node 0 Processor 14 APIC 0xd
[ 8140.340571] microcode: CPU14: patch_level=0x08701021
[ 8140.342825] ACPI: \_PR_.C00D: Found 2 idle states
[ 8140.346611] CPU14 is up
[ 8140.346635] smpboot: Booting Node 0 Processor 15 APIC 0xf
[ 8140.346823] microcode: CPU15: patch_level=0x08701021
[ 8140.349075] ACPI: \_PR_.C00F: Found 2 idle states
[ 8140.350299] CPU15 is up
[ 8140.351321] ACPI: PM: Waking up from system sleep state S3
[ 8140.352048] ACPI: EC: interrupt unblocked
[ 8140.416814] ACPI: EC: event unblocked
[ 8140.416904] usb usb1: root hub lost power or was reset
[ 8140.416907] usb usb2: root hub lost power or was reset
[ 8140.417068] usb usb3: root hub lost power or was reset
[ 8140.417070] usb usb4: root hub lost power or was reset
[ 8140.417512] sd 4:0:0:0: [sdb] Starting disk
[ 8140.417512] sd 0:0:0:0: [sda] Starting disk
[ 8140.417779] serial 00:04: activated
[ 8140.486949] nvme nvme0: 8/0/0 default/read/poll queues
[ 8140.640050] usb 2-4: reset SuperSpeed USB device number 2 using xhci_hcd
[ 8140.728699] ata3: SATA link down (SStatus 0 SControl 330)
[ 8140.728721] ata6: SATA link down (SStatus 0 SControl 330)
[ 8140.728743] ata4: SATA link down (SStatus 0 SControl 330)
[ 8140.728766] ata8: SATA link down (SStatus 0 SControl 330)
[ 8140.728786] ata7: SATA link down (SStatus 0 SControl 330)
[ 8140.731996] ata2: SATA link down (SStatus 0 SControl 300)
[ 8140.826344] usb 3-1: reset full-speed USB device number 2 using xhci_hcd
[ 8140.849309] usb 1-13: reset full-speed USB device number 6 using xhci_hcd
[ 8140.886220] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 8140.886238] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 8140.886460] ata5.00: supports DRM functions and may not be fully accessible
[ 8140.886476] ata1.00: supports DRM functions and may not be fully accessible
[ 8140.886872] ata5.00: disabling queued TRIM support
[ 8140.886898] ata1.00: disabling queued TRIM support
[ 8140.888773] ata5.00: supports DRM functions and may not be fully accessible
[ 8140.888796] ata1.00: supports DRM functions and may not be fully accessible
[ 8140.889177] ata5.00: disabling queued TRIM support
[ 8140.889227] ata1.00: disabling queued TRIM support
[ 8140.890813] ata5.00: configured for UDMA/133
[ 8140.890863] ata1.00: configured for UDMA/133
[ 8140.891205] ata5.00: Enabling discard_zeroes_data
[ 8140.891245] ata1.00: Enabling discard_zeroes_data
[ 8141.155092] usb usb5: root hub lost power or was reset
[ 8141.155093] usb usb6: root hub lost power or was reset
[ 8141.335927] usb 1-9: reset full-speed USB device number 5 using xhci_hcd
[ 8141.813231] usb 1-7: reset full-speed USB device number 4 using xhci_hcd
[ 8142.289785] usb 1-5: reset full-speed USB device number 3 using xhci_hcd
[ 8142.769744] usb 1-3: reset full-speed USB device number 2 using xhci_hcd
[ 8143.534714] OOM killer enabled.
[ 8143.534716] Restarting tasks ... done.
[ 8143.538145] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[ 8143.541873] PM: suspend exit
[ 8143.545819] rfkill: input handler enabled
[ 8143.546148] Bluetooth: hci0: Device revision is 1
[ 8143.546153] Bluetooth: hci0: Secure boot is enabled
[ 8143.546154] Bluetooth: hci0: OTP lock is enabled
[ 8143.546155] Bluetooth: hci0: API lock is enabled
[ 8143.546155] Bluetooth: hci0: Debug lock is disabled
[ 8143.546156] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 8143.546160] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi

seth · 2021-11-02 08:05:30

You've set and confirmed *all* devices in /proc/acpi/wakeup to be disabled and this still happens?
What's "cat /sys/power/mem_sleep"?
Do you have a parallel OS (windows…) installation?

Ex0Matter · 2021-11-02 08:16:03

seth wrote:

You've set and confirmed *all* devices in /proc/acpi/wakeup to be disabled and this still happens?

I haven't done this yet, but I will test this next. Just a question: in my wakeup devices, the only ones still enabled are in the S4 state, would this have an impact on the suspend? As far as I understand, S4 is the hibernation state, so I wouldn't expect it to impact.

seth wrote:

What's "cat /sys/power/mem_sleep"?

s2idle [deep]

seth wrote:

Do you have a parallel OS (windows…) installation?

I do have a Windows dual-boot, and I've ensured fast boot is disabled. I doubt it had an impact, but one odd thing I noted in the dmesg log was that the Bluetooth module said that Secure Boot was enabled, but I made sure to disable it in my motherboard's UEFI settings before I installed Arch.

seth · 2021-11-02 08:18:41

S4 implies S3, if the device can wake from S4 it will wake from S3 as well.
The problem is *not* that deep sleep isn't available and the shallow one fails (an issue w/ some notebooks)

Windows is also not actively hibernating?

Ex0Matter · 2021-11-02 08:23:01

seth wrote:

S4 implies S3, if the device can wake from S4 it will wake from S3 as well.
The problem is *not* that deep sleep isn't available and the shallow one fails (an issue w/ some notebooks)

Ahh gotcha, thanks for clearing that up!

seth wrote:

Windows is also not actively hibernating?

I don't believe so, but often I'll hit "Restart" from Windows when I want to switch back to Arch. Just to make absolutely sure, I'll boot back into Windows and do a hard restart.

Ex0Matter · 2021-11-04 01:21:47

Ok, I went through and manually disabled all wake-up items and suspend is now working properly . This also miraculously solved (I hope at least) my weird screen artifacting problem. My question now is, how can I make this a permanent change?

seth · 2021-11-04 06:52:03

First and foremost you want to isolate the offender - you cannot really bisect them, because there could be more than one, but you can trim them down in bulk (keep several enabled on each try - either S3 works and you can subsequently ignore those devices or you found a group w/ at least one offender)

The values are transient, so you have to update them w/ every boot, eg. using a tempfile.
https://wiki.archlinux.org/title/Power_ … om_suspend lists an example.

Arch Linux

#1 2021-11-02 07:17:19

Computer wakes up right after suspending

#2 2021-11-02 08:05:30

Re: Computer wakes up right after suspending

#3 2021-11-02 08:16:03

Re: Computer wakes up right after suspending

#4 2021-11-02 08:18:41

Re: Computer wakes up right after suspending

#5 2021-11-02 08:23:01

Re: Computer wakes up right after suspending

#6 2021-11-04 01:21:47

Re: Computer wakes up right after suspending

#7 2021-11-04 06:52:03

Re: Computer wakes up right after suspending

Board footer