You are not logged in.

Pages: 1

#1 2022-12-27 04:09:31

megaminxwin
Member
Registered: 2017-07-30
Posts: 16

AMD Desktop immediately wakes up from sleep

Hi,

A while ago I installed a new motherboard, a Gigabyte B450 Aorus Elite, and since then I've been unable to put my computer to sleep without it immediately starting up again. I had this problem with my last motherboard as well, an Asus Prime B450-Plus, but I was able to solve it last time by disabling certain devices in /proc/acpi/wakeup. This time, however, even if every single device is disabled, it still immediately wakes up. I had been having this issue with Kubuntu as well, which was one of the reasons I switched, but unfortunately the same problem is still occurring.

I attempted to disable all devices in /sys/bus/usb/devices/*/power/wakeup, but that didn't help. At first I thought it was because of the couple of external drives I have, but even when all devices are unplugged, except for a display, keyboard, and mouse, the system still immediately wakes up.

This is the relevant section of journalctl:

Dec 27 14:47:42 tamara-arch systemd-logind[618]: The system will suspend now!
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.6236] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.6237] device (eno1): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.6326] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.6327] manager: NetworkManager state is now ASLEEP
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.6328] device (wlan0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Dec 27 14:47:42 tamara-arch dbus-daemon[616]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=636 comm="/usr/bin/NetworkManager --no-daemon")
Dec 27 14:47:42 tamara-arch systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 27 14:47:42 tamara-arch dbus-daemon[616]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 27 14:47:42 tamara-arch systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 27 14:47:42 tamara-arch audit[1]: SERVICE_START 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 27 14:47:42 tamara-arch kernel: audit: type=1130 audit(1672112862.666:828): 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 27 14:47:42 tamara-arch kernel: wlan0: deauthenticating from 98:da:c4:9b:30:eb by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 27 14:47:42 tamara-arch kscreenlocker_greet[118987]: Qt: Session management error: networkIdsList argument is NULL
Dec 27 14:47:42 tamara-arch wpa_supplicant[728]: wlan0: CTRL-EVENT-DISCONNECTED bssid=98:da:c4:9b:30:eb reason=3 locally_generated=1
Dec 27 14:47:42 tamara-arch wpa_supplicant[728]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.8126] device (wlan0): supplicant interface state: completed -> disconnected
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.8127] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Dec 27 14:47:42 tamara-arch kded5[118718]: org.kde.plasma.nm.kded: Unhandled active connection state change:  3
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.8622] dhcp4 (wlan0): canceled DHCP transaction
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.8622] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.8622] dhcp4 (wlan0): state changed no lease
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.8623] dhcp6 (wlan0): canceled DHCP transaction
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.8623] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.8623] dhcp6 (wlan0): state changed no lease
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.9132] device (wlan0): set-hw-addr: set MAC address to C2:A6:04:5A:5E:20 (scanning)
Dec 27 14:47:42 tamara-arch systemd-resolved[612]: wlan0: Bus client set default route setting: no
Dec 27 14:47:42 tamara-arch systemd-resolved[612]: wlan0: Bus client reset DNS server list.
Dec 27 14:47:42 tamara-arch iwd[617]: Could not register frame watch type 00d0: -114
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.9496] device (wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Dec 27 14:47:42 tamara-arch NetworkManager[636]: <info>  [1672112862.9995] device (wlan0): set-hw-addr: reset MAC address to AC:12:03:FB:02:D9 (unmanage)
Dec 27 14:47:43 tamara-arch iwd[617]: Could not register frame watch type 00d0: -114
Dec 27 14:47:43 tamara-arch wpa_supplicant[728]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 27 14:47:43 tamara-arch wpa_supplicant[728]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 27 14:47:43 tamara-arch wpa_supplicant[728]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
Dec 27 14:47:43 tamara-arch wpa_supplicant[728]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 27 14:47:43 tamara-arch kscreenlocker_greet[118987]: kf.kirigami: Failed to find a Kirigami platform plugin
Dec 27 14:47:43 tamara-arch kscreenlocker_greet[118987]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed
Dec 27 14:47:43 tamara-arch systemd[1]: Reached target Sleep.
Dec 27 14:47:43 tamara-arch wpa_supplicant[728]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 27 14:47:43 tamara-arch wpa_supplicant[728]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Dec 27 14:47:43 tamara-arch systemd[1]: Starting System Suspend...
Dec 27 14:47:43 tamara-arch systemd-sleep[119041]: Entering sleep state 'suspend'...
Dec 27 14:47:43 tamara-arch kernel: PM: suspend entry (deep)
Dec 27 14:47:43 tamara-arch kernel: Filesystems sync: 0.091 seconds
Dec 27 14:47:50 tamara-arch kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Dec 27 14:47:50 tamara-arch kernel: OOM killer disabled.
Dec 27 14:47:50 tamara-arch kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Dec 27 14:47:50 tamara-arch kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dec 27 14:47:50 tamara-arch kernel: serial 00:04: disabled
Dec 27 14:47:50 tamara-arch kernel: queueing ieee80211 work while going to suspend
Dec 27 14:47:50 tamara-arch kernel: sd 14:0:0:0: [sdc] Synchronizing SCSI cache
Dec 27 14:47:50 tamara-arch kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Dec 27 14:47:50 tamara-arch kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Dec 27 14:47:50 tamara-arch kernel: sd 15:0:0:0: [sdd] Synchronizing SCSI cache
Dec 27 14:47:50 tamara-arch kernel: sd 1:0:0:0: [sdb] Stopping disk
Dec 27 14:47:50 tamara-arch kernel: sd 0:0:0:0: [sda] Stopping disk
Dec 27 14:47:50 tamara-arch kernel: amdgpu 0000:06:00.0: amdgpu: PCI CONFIG reset
Dec 27 14:47:50 tamara-arch kernel: ACPI: PM: Preparing to enter system sleep state S3
Dec 27 14:47:50 tamara-arch kernel: ACPI: PM: Saving platform NVS memory
Dec 27 14:47:50 tamara-arch kernel: Disabling non-boot CPUs ...
Dec 27 14:47:50 tamara-arch kernel: smpboot: CPU 1 is now offline
Dec 27 14:47:50 tamara-arch kernel: smpboot: CPU 2 is now offline
Dec 27 14:47:50 tamara-arch kernel: smpboot: CPU 3 is now offline
Dec 27 14:47:50 tamara-arch kernel: smpboot: CPU 4 is now offline
Dec 27 14:47:50 tamara-arch kernel: smpboot: CPU 5 is now offline
Dec 27 14:47:50 tamara-arch kernel: smpboot: CPU 6 is now offline
Dec 27 14:47:50 tamara-arch kernel: smpboot: CPU 7 is now offline
Dec 27 14:47:50 tamara-arch kernel: smpboot: CPU 8 is now offline
Dec 27 14:47:50 tamara-arch kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
Dec 27 14:47:50 tamara-arch kernel: smpboot: CPU 9 is now offline
Dec 27 14:47:50 tamara-arch kernel: smpboot: CPU 10 is now offline
Dec 27 14:47:50 tamara-arch kernel: smpboot: CPU 11 is now offline
Dec 27 14:47:50 tamara-arch kernel: smpboot: CPU 12 is now offline
Dec 27 14:47:50 tamara-arch kernel: smpboot: CPU 13 is now offline
Dec 27 14:47:50 tamara-arch kernel: smpboot: CPU 14 is now offline
Dec 27 14:47:50 tamara-arch kernel: smpboot: CPU 15 is now offline
Dec 27 14:47:50 tamara-arch kernel: ACPI: PM: Low-level resume complete
Dec 27 14:47:50 tamara-arch kernel: ACPI: PM: Restoring platform NVS memory
Dec 27 14:47:50 tamara-arch kernel: LVT offset 0 assigned for vector 0x400
Dec 27 14:47:50 tamara-arch kernel: Enabling non-boot CPUs ...
Dec 27 14:47:50 tamara-arch kernel: x86: Booting SMP configuration:
Dec 27 14:47:50 tamara-arch kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Dec 27 14:47:50 tamara-arch kernel: microcode: CPU1: patch_level=0x0a20120a
Dec 27 14:47:50 tamara-arch kernel: ACPI: \_PR_.C002: Found 2 idle states
Dec 27 14:47:50 tamara-arch kernel: CPU1 is up
Dec 27 14:47:50 tamara-arch kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Dec 27 14:47:50 tamara-arch kernel: microcode: CPU2: patch_level=0x0a20120a
Dec 27 14:47:50 tamara-arch kernel: ACPI: \_PR_.C004: Found 2 idle states
Dec 27 14:47:50 tamara-arch kernel: CPU2 is up
Dec 27 14:47:50 tamara-arch kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Dec 27 14:47:50 tamara-arch kernel: microcode: CPU3: patch_level=0x0a20120a
Dec 27 14:47:50 tamara-arch kernel: ACPI: \_PR_.C006: Found 2 idle states
Dec 27 14:47:50 tamara-arch kernel: CPU3 is up
Dec 27 14:47:50 tamara-arch kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Dec 27 14:47:50 tamara-arch kernel: microcode: CPU4: patch_level=0x0a20120a
Dec 27 14:47:50 tamara-arch kernel: ACPI: \_PR_.C008: Found 2 idle states
Dec 27 14:47:50 tamara-arch kernel: CPU4 is up
Dec 27 14:47:50 tamara-arch kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Dec 27 14:47:50 tamara-arch kernel: microcode: CPU5: patch_level=0x0a20120a
Dec 27 14:47:50 tamara-arch kernel: ACPI: \_PR_.C00A: Found 2 idle states
Dec 27 14:47:50 tamara-arch kernel: CPU5 is up
Dec 27 14:47:50 tamara-arch kernel: smpboot: Booting Node 0 Processor 6 APIC 0xc
Dec 27 14:47:50 tamara-arch kernel: microcode: CPU6: patch_level=0x0a20120a
Dec 27 14:47:50 tamara-arch kernel: ACPI: \_PR_.C00C: Found 2 idle states
Dec 27 14:47:50 tamara-arch kernel: CPU6 is up
Dec 27 14:47:50 tamara-arch kernel: smpboot: Booting Node 0 Processor 7 APIC 0xe
Dec 27 14:47:50 tamara-arch kernel: microcode: CPU7: patch_level=0x0a20120a
Dec 27 14:47:50 tamara-arch kernel: ACPI: \_PR_.C00E: Found 2 idle states
Dec 27 14:47:50 tamara-arch kernel: CPU7 is up
Dec 27 14:47:50 tamara-arch kernel: smpboot: Booting Node 0 Processor 8 APIC 0x1
Dec 27 14:47:50 tamara-arch kernel: microcode: CPU8: patch_level=0x0a20120a
Dec 27 14:47:50 tamara-arch kernel: ACPI: \_PR_.C001: Found 2 idle states
Dec 27 14:47:50 tamara-arch kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Dec 27 14:47:50 tamara-arch kernel: CPU8 is up
Dec 27 14:47:50 tamara-arch kernel: smpboot: Booting Node 0 Processor 9 APIC 0x3
Dec 27 14:47:50 tamara-arch kernel: microcode: CPU9: patch_level=0x0a20120a
Dec 27 14:47:50 tamara-arch kernel: ACPI: \_PR_.C003: Found 2 idle states
Dec 27 14:47:50 tamara-arch kernel: CPU9 is up
Dec 27 14:47:50 tamara-arch kernel: smpboot: Booting Node 0 Processor 10 APIC 0x5
Dec 27 14:47:50 tamara-arch kernel: microcode: CPU10: patch_level=0x0a20120a
Dec 27 14:47:50 tamara-arch kernel: ACPI: \_PR_.C005: Found 2 idle states
Dec 27 14:47:50 tamara-arch kernel: CPU10 is up
Dec 27 14:47:50 tamara-arch kernel: smpboot: Booting Node 0 Processor 11 APIC 0x7
Dec 27 14:47:50 tamara-arch kernel: microcode: CPU11: patch_level=0x0a20120a
Dec 27 14:47:50 tamara-arch kernel: ACPI: \_PR_.C007: Found 2 idle states
Dec 27 14:47:50 tamara-arch kernel: CPU11 is up
Dec 27 14:47:50 tamara-arch kernel: smpboot: Booting Node 0 Processor 12 APIC 0x9
Dec 27 14:47:50 tamara-arch kernel: microcode: CPU12: patch_level=0x0a20120a
Dec 27 14:47:50 tamara-arch kernel: ACPI: \_PR_.C009: Found 2 idle states
Dec 27 14:47:50 tamara-arch kernel: CPU12 is up
Dec 27 14:47:50 tamara-arch kernel: smpboot: Booting Node 0 Processor 13 APIC 0xb
Dec 27 14:47:50 tamara-arch kernel: microcode: CPU13: patch_level=0x0a20120a
Dec 27 14:47:50 tamara-arch kernel: ACPI: \_PR_.C00B: Found 2 idle states
Dec 27 14:47:50 tamara-arch kernel: CPU13 is up
Dec 27 14:47:50 tamara-arch kernel: smpboot: Booting Node 0 Processor 14 APIC 0xd
Dec 27 14:47:50 tamara-arch kernel: microcode: CPU14: patch_level=0x0a20120a
Dec 27 14:47:50 tamara-arch kernel: ACPI: \_PR_.C00D: Found 2 idle states
Dec 27 14:47:50 tamara-arch kernel: CPU14 is up
Dec 27 14:47:50 tamara-arch kernel: smpboot: Booting Node 0 Processor 15 APIC 0xf
Dec 27 14:47:50 tamara-arch kernel: microcode: CPU15: patch_level=0x0a20120a
Dec 27 14:47:50 tamara-arch kernel: ACPI: \_PR_.C00F: Found 2 idle states
Dec 27 14:47:50 tamara-arch kernel: CPU15 is up
Dec 27 14:47:50 tamara-arch kernel: ACPI: PM: Waking up from system sleep state S3
Dec 27 14:47:50 tamara-arch kernel: xhci_hcd 0000:01:00.0: xHC error in resume, USBSTS 0x401, Reinit
Dec 27 14:47:50 tamara-arch kernel: usb usb1: root hub lost power or was reset
Dec 27 14:47:50 tamara-arch kernel: usb usb2: root hub lost power or was reset
Dec 27 14:47:50 tamara-arch kernel: usb usb3: root hub lost power or was reset
Dec 27 14:47:50 tamara-arch kernel: usb usb4: root hub lost power or was reset
Dec 27 14:47:50 tamara-arch kernel: serial 00:04: activated
Dec 27 14:47:50 tamara-arch kernel: sd 0:0:0:0: [sda] Starting disk
Dec 27 14:47:50 tamara-arch kernel: sd 1:0:0:0: [sdb] Starting disk
Dec 27 14:47:50 tamara-arch kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400300000).
Dec 27 14:47:50 tamara-arch kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Dec 27 14:47:50 tamara-arch kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Dec 27 14:47:50 tamara-arch kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Dec 27 14:47:50 tamara-arch kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Dec 27 14:47:50 tamara-arch kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Dec 27 14:47:50 tamara-arch kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Dec 27 14:47:50 tamara-arch kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
Dec 27 14:47:50 tamara-arch kernel: usb 3-1: reset high-speed USB device number 2 using xhci_hcd
Dec 27 14:47:50 tamara-arch kernel: ata6: SATA link down (SStatus 0 SControl 330)
Dec 27 14:47:50 tamara-arch kernel: ata5: SATA link down (SStatus 0 SControl 330)
Dec 27 14:47:50 tamara-arch kernel: usb 1-6: reset full-speed USB device number 4 using xhci_hcd
Dec 27 14:47:50 tamara-arch kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 27 14:47:50 tamara-arch kernel: ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Dec 27 14:47:50 tamara-arch kernel: ata2.00: supports DRM functions and may not be fully accessible
Dec 27 14:47:50 tamara-arch kernel: ata2.00: supports DRM functions and may not be fully accessible
Dec 27 14:47:50 tamara-arch kernel: ata2.00: configured for UDMA/133
Dec 27 14:47:50 tamara-arch kernel: ata14.00: configured for PIO3
Dec 27 14:47:50 tamara-arch kernel: usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd
Dec 27 14:47:50 tamara-arch kernel: usb 1-2: reset full-speed USB device number 2 using xhci_hcd
Dec 27 14:47:50 tamara-arch kernel: usb 3-1.2: reset high-speed USB device number 3 using xhci_hcd
Dec 27 14:47:50 tamara-arch kernel: [drm] Fence fallback timer expired on ring sdma0
Dec 27 14:47:50 tamara-arch kernel: usb 1-5: reset low-speed USB device number 3 using xhci_hcd
Dec 27 14:47:50 tamara-arch kernel: [drm] Fence fallback timer expired on ring sdma0
Dec 27 14:47:50 tamara-arch kernel: usb 1-9: reset full-speed USB device number 5 using xhci_hcd
Dec 27 14:47:50 tamara-arch kernel: [drm] Fence fallback timer expired on ring sdma0
Dec 27 14:47:50 tamara-arch kernel: [drm] Fence fallback timer expired on ring sdma0
Dec 27 14:47:50 tamara-arch kernel: [drm] Fence fallback timer expired on ring sdma0
Dec 27 14:47:50 tamara-arch kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 27 14:47:50 tamara-arch kernel: [drm] Fence fallback timer expired on ring sdma0
Dec 27 14:47:50 tamara-arch kernel: ata1.00: configured for UDMA/133
Dec 27 14:47:50 tamara-arch kernel: [drm] UVD and UVD ENC initialized successfully.
Dec 27 14:47:50 tamara-arch kernel: [drm] VCE initialized successfully.
Dec 27 14:47:50 tamara-arch kernel: OOM killer enabled.
Dec 27 14:47:50 tamara-arch kernel: Restarting tasks ... done.
Dec 27 14:47:50 tamara-arch kernel: random: crng reseeded on system resumption
Dec 27 14:47:50 tamara-arch kernel: PM: suspend exit

And my /proc/acpi/wakeup, although it's not exactly that helpful since I have disabled everything:

Device  S-state   Status   Sysfs node
GPP0      S4    *disabled
GPP1      S4    *disabled
GPP3      S4    *disabled
GPP4      S4    *disabled
GPP5      S4    *disabled
GPP6      S4    *disabled
GPP7      S4    *disabled
GPP8      S4    *disabled  pci:0000:00:03.1
GPP9      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    *disabled  pci:0000:00:07.1
GP13      S4    *disabled  pci:0000:00:08.1
XHC0      S4    *disabled  pci:0000:08:00.3
GP30      S4    *disabled
GP31      S4    *disabled  pci:0000:00:08.3
PS2K      S3    *disabled
PS2M      S3    *disabled
GPP2      S4    *disabled  pci:0000:00:01.3
PTXH      S4    *disabled  pci:0000:01:00.0

My "dmidecode | grep Wake-up" gives me "Wake-up Type: Power Switch", which isn't helpful either. Part of me now thinks it's a kernel issue, but considering this has been happening to me for many months across several different kernels, I think I might just be missing something here. I checked the BIOS but there doesn't appear to be anything there that would prevent this.

Any help would be greatly appreciated, as it's beginning to drive me slightly mad. Thanks!

Offline

#2 2022-12-27 07:46:51

d.ALT
Member
Registered: 2019-05-10
Posts: 920

Re: AMD Desktop immediately wakes up from sleep

Do you have some weir Oprions enabled in your UEFI Firmware Settings?
I recall once I had a computer it was waking-up immediately after suspend because of Wake-On-PCI events enabled in UEFI.

<49,17,III,I>    Fama di loro il mondo esser non lassa;
<50,17,III,I>    misericordia e giustizia li sdegna:
<51,17,III,I>    non ragioniam di lor, ma guarda e passa.

Offline

#3 2022-12-27 08:26:07

megaminxwin
Member
Registered: 2017-07-30
Posts: 16

Re: AMD Desktop immediately wakes up from sleep

I've checked all the BIOS settings, but as far as I can tell, everything to do with waking up is disabled. Resume by alarm is disabled, wake on LAN is disabled, power on by keyboard/mouse is disabled, and so on.

Offline

#4 2023-01-04 08:39:56

botsunny
Member
Registered: 2022-03-14
Posts: 9

Re: AMD Desktop immediately wakes up from sleep

Hi there, have you been able to fix this issue? I have the exact same problem as yours, except I am using an AMD laptop. My `/proc/acpi/wakeup` shows

Device  S-state   Status   Sysfs node
GP17      S3    *disabled  pci:0000:00:08.1
XHC0      S3    *disabled  pci:0000:03:00.3
XHC1      S3    *disabled  pci:0000:03:00.4

`sudo dmidecode | grep Wake-up` also shows 

Wake-up Type: Power Switch

My journalctl messages are also similar. Kernel is 6.1.2-arch1-1. This problem is driving me crazy.

Offline

#5 2023-01-06 07:04:11

megaminxwin
Member
Registered: 2017-07-30
Posts: 16

Re: AMD Desktop immediately wakes up from sleep

No, I'm still working on this. Could it be a kernel bug, maybe? I'm not sure how I could confirm that.

Offline

#6 2024-01-30 07:14:48

meetvora
Member
Registered: 2019-06-10
Posts: 4

Re: AMD Desktop immediately wakes up from sleep

I'm having the same problem
so far I've tried
- Disabling bluetooth before sleep
- Disabling NetworkManager before sleep

still no luck

I am using a treadripper and an amdgpu

Offline

#7 2024-01-30 09:52:01

seth
Member
Registered: 2012-09-03
Posts: 52,199

Re: AMD Desktop immediately wakes up from sleep

Wild guess would be the CPU power state, https://wiki.archlinux.org/title/Ryzen# … nd_suspend
Does any of you have a parallel windows installation (3rd link below…)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#8 2024-03-19 22:56:49

1sliq
Member
Registered: 2024-02-13
Posts: 6

Re: AMD Desktop immediately wakes up from sleep

This looks exactly like the issue I have, journalctl looks the same as well. Here's the post I made for reference: https://bbs.archlinux.org/viewtopic.php … 1#p2150752

Unfortunately I don't have a solution either, but I've tried a lot of the same things. Seth - I just tried your CPU power state change, but the issue persists.

I have a Gigabyte Aorus B650i, interesting that the motherboards are so similar.

Offline

#9 2024-05-03 12:04:41

NicoDelle
Member
Registered: 2024-01-27
Posts: 2

Re: AMD Desktop immediately wakes up from sleep

I'm having the same exact problem on an AMD laptop (with integrated graphics) . I've found that booting with the "nomodeset=0" kernel parameter solves the issue related to suspension, but that isn't a suitable solution because then i'm not able to adjust the brightness and experience poor performances overall. Does this point to anything? Have you had any luck in the meantime?

Offline

Pages: 1

Board footer

Powered by FluxBB