Sample Header Ad - 728x90

Asus TUF A16 AMD Laptop wakes up immediately after sleep when External Monitor is plugged in

1 vote
0 answers
117 views
I'm using the ASUS TUF A16 which comes with AMD Radeon RX 7700S dedicated GPU, and an integrated Radeon 680M. It manages them through a MUX switcher in the laptop, with the only option to run dedicated-gpu only on boot menu. I'm on KDE-fedora, but I have replicated the problem on multiple distros and desktop environments. The problem I'm having is that the laptop goes to sleep and immediately wakes up when my external monitor is plugged in. I've done some research and troubleshooting, and I've come to think the cause is that the external GPU restarts whenever it goes to sleep with the external monitor on, possibly related to AMD's MUX switch, but that's just speculation. I assume this is because the hdmi is run by the dgpu, and doesn't work with the igpu, but how to fix it has proven so far to be out of my league. This is the last minute of journalctl log after suspension: Dec 31 12:13:29 LaptopHostName systemd-logind: The system will suspend now! Dec 31 12:13:29 LaptopHostName ModemManager: [sleep-monitor-systemd] system is about to suspend Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.7223] manager: sleep: sleep requested (sleeping: no enabled: yes) Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.7229] device (eno1): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full') Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.7347] device (p2p-dev-wlp6s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full') Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.7350] manager: NetworkManager state is now ASLEEP Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.7352] device (wlp6s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full') Dec 31 12:13:29 LaptopHostName kded6: org.kde.plasma.nm.kded: Unhandled active connection state change: 3 Dec 31 12:13:29 LaptopHostName systemd: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... ░░ Subject: A start job for unit NetworkManager-dispatcher.service has begun execution ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit NetworkManager-dispatcher.service has begun execution. ░░ ░░ The job identifier is 13845. Dec 31 12:13:29 LaptopHostName systemd: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. ░░ Subject: A start job for unit NetworkManager-dispatcher.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit NetworkManager-dispatcher.service has finished successfully. ░░ ░░ The job identifier is 13845. Dec 31 12:13:29 LaptopHostName audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 31 12:13:29 LaptopHostName kernel: wlp6s0: deauthenticating from 58:ae:f1:59:cf:cc by local choice (Reason: 3=DEAUTH_LEAVING) Dec 31 12:13:29 LaptopHostName wpa_supplicant: nl80211: send_event_marker failed: Source based routing not supported Dec 31 12:13:29 LaptopHostName wpa_supplicant: wlp6s0: CTRL-EVENT-DISCONNECTED bssid=58:ae:f1:59:cf:cc reason=3 locally_generated=1 Dec 31 12:13:29 LaptopHostName wpa_supplicant: wlp6s0: CTRL-EVENT-DSCP-POLICY clear_all Dec 31 12:13:29 LaptopHostName wpa_supplicant: wlp6s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.9105] device (wlp6s0): supplicant interface state: completed -> disconnected Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.9107] device (wlp6s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full') Dec 31 12:13:29 LaptopHostName avahi-daemon: Withdrawing address record for fe80::55c1:d249:2295:4446 on wlp6s0. Dec 31 12:13:29 LaptopHostName avahi-daemon: Leaving mDNS multicast group on interface wlp6s0.IPv6 with address fe80::55c1:d249:2295:4446. Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.9114] dhcp4 (wlp6s0): canceled DHCP transaction Dec 31 12:13:29 LaptopHostName avahi-daemon: Interface wlp6s0.IPv6 no longer relevant for mDNS. Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.9114] dhcp4 (wlp6s0): activation: beginning transaction (timeout in 45 seconds) Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.9114] dhcp4 (wlp6s0): state changed no lease Dec 31 12:13:29 LaptopHostName audit: NETFILTER_CFG table=firewalld:51 family=1 entries=34 op=nft_unregister_rule pid=2027 subj=system_u:system_r:firewalld_t:s0 comm="firewalld" Dec 31 12:13:29 LaptopHostName audit: SYSCALL arch=c000003e syscall=46 success=yes exit=2680 a0=6 a1=7fffc43f33f0 a2=0 a3=7fffc43f3560 items=0 ppid=1 pid=2027 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="firewalld" exe="/usr/bin/python3.13" subj=system_u:system_r:firewalld_t:s0 key=(null) Dec 31 12:13:29 LaptopHostName audit: PROCTITLE proctitle=2F7573722F62696E2F707974686F6E33002D7350002F7573722F7362696E2F6669726577616C6C64002D2D6E6F666F726B002D2D6E6F706964 Dec 31 12:13:29 LaptopHostName avahi-daemon: Interface wlp6s0.IPv4 no longer relevant for mDNS. Dec 31 12:13:29 LaptopHostName avahi-daemon: Leaving mDNS multicast group on interface wlp6s0.IPv4 with address 192.168.1.9. Dec 31 12:13:29 LaptopHostName avahi-daemon: Withdrawing address record for 192.168.1.9 on wlp6s0. Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.9423] device (wlp6s0): set-hw-addr: set MAC address to 1A:DF:02:F4:56:54 (scanning) Dec 31 12:13:29 LaptopHostName avahi-daemon: Joining mDNS multicast group on interface wlp6s0.IPv4 with address 192.168.1.9. Dec 31 12:13:29 LaptopHostName avahi-daemon: New relevant interface wlp6s0.IPv4 for mDNS. Dec 31 12:13:29 LaptopHostName avahi-daemon: Registering new address record for 192.168.1.9 on wlp6s0.IPv4. Dec 31 12:13:29 LaptopHostName avahi-daemon: Withdrawing address record for 192.168.1.9 on wlp6s0. Dec 31 12:13:29 LaptopHostName avahi-daemon: Leaving mDNS multicast group on interface wlp6s0.IPv4 with address 192.168.1.9. Dec 31 12:13:29 LaptopHostName avahi-daemon: Interface wlp6s0.IPv4 no longer relevant for mDNS. Dec 31 12:13:29 LaptopHostName systemd-resolved: wlp6s0: Bus client set default route setting: no Dec 31 12:13:29 LaptopHostName systemd-resolved: wlp6s0: Bus client reset DNS server list. Dec 31 12:13:30 LaptopHostName NetworkManager: [1735658010.0132] device (wlp6s0): supplicant interface state: disconnected -> interface_disabled Dec 31 12:13:30 LaptopHostName NetworkManager: [1735658010.0134] device (wlp6s0): supplicant interface state: interface_disabled -> disconnected Dec 31 12:13:30 LaptopHostName NetworkManager: [1735658010.0136] device (wlp6s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full') Dec 31 12:13:30 LaptopHostName chronyd: Source 216.238.106.159 offline Dec 31 12:13:30 LaptopHostName chronyd: Source 143.107.229.210 offline Dec 31 12:13:30 LaptopHostName chronyd: Source 200.160.7.197 offline Dec 31 12:13:30 LaptopHostName chronyd: Can't synchronise: no selectable sources Dec 31 12:13:30 LaptopHostName chronyd: Source 200.160.7.193 offline Dec 31 12:13:30 LaptopHostName NetworkManager: [1735658010.0599] device (wlp6s0): set-hw-addr: reset MAC address to 94:BB:43:74:7D:0D (unmanage) Dec 31 12:13:30 LaptopHostName wpa_supplicant: wlp6s0: CTRL-EVENT-DSCP-POLICY clear_all Dec 31 12:13:30 LaptopHostName systemd: Reached target sleep.target - Sleep. ░░ Subject: A start job for unit sleep.target has finished successfully ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit sleep.target has finished successfully. ░░ ░░ The job identifier is 14007. Dec 31 12:13:30 LaptopHostName systemd: Starting systemd-suspend.service - System Suspend... ░░ Subject: A start job for unit systemd-suspend.service has begun execution ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit systemd-suspend.service has begun execution. ░░ ░░ The job identifier is 14004. Dec 31 12:13:30 LaptopHostName wpa_supplicant: wlp6s0: CTRL-EVENT-DSCP-POLICY clear_all Dec 31 12:13:30 LaptopHostName wpa_supplicant: nl80211: deinit ifname=wlp6s0 disabled_11b_rates=0 Dec 31 12:13:30 LaptopHostName systemd-sleep: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0). Dec 31 12:13:30 LaptopHostName systemd-sleep: This is not recommended, and might result in unexpected behavior, particularly Dec 31 12:13:30 LaptopHostName systemd-sleep: in suspend-then-hibernate operations or setups with encrypted home directories. Dec 31 12:13:30 LaptopHostName systemd-sleep: Performing sleep operation 'suspend'... ░░ Subject: System sleep state suspend entered ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ The system has now entered the suspend sleep state. Dec 31 12:13:30 LaptopHostName kernel: PM: suspend entry (s2idle) Dec 31 12:13:30 LaptopHostName kernel: Filesystems sync: 0.032 seconds Dec 31 12:13:32 LaptopHostName kernel: Freezing user space processes Dec 31 12:13:32 LaptopHostName kernel: Freezing user space processes completed (elapsed 0.003 seconds) Dec 31 12:13:32 LaptopHostName kernel: OOM killer disabled. Dec 31 12:13:32 LaptopHostName kernel: Freezing remaining freezable tasks Dec 31 12:13:32 LaptopHostName kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds) Dec 31 12:13:32 LaptopHostName kernel: printk: Suspending console(s) (use no_console_suspend to debug) Dec 31 12:13:32 LaptopHostName kernel: queueing ieee80211 work while going to suspend Dec 31 12:13:32 LaptopHostName kernel: PM: suspend devices took 0.282 seconds Dec 31 12:13:32 LaptopHostName kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F41FC00000). Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: SMU is resuming... Dec 31 12:13:32 LaptopHostName kernel: [drm] PCIE GART of 512M enabled (table at 0x00000081FEB00000). Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: PSP is resuming... Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: SMU is resumed successfully! Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8 Dec 31 12:13:32 LaptopHostName kernel: nvme nvme0: 16/0/0 default/read/poll queues Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: reserve 0x1300000 from 0x81fc000000 for PSP TMR Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming... Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x00000035, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x00525c00 (82.92.0) Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched Dec 31 12:13:32 LaptopHostName kernel: usb 9-1: reset full-speed USB device number 7 using xhci_hcd Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully! Dec 31 12:13:32 LaptopHostName kernel: [drm] DMUB hardware initialized: version=0x07002A00 Dec 31 12:13:32 LaptopHostName kernel: usb 9-1: PM: dpm_run_callback(): usb_dev_resume returns -5 Dec 31 12:13:32 LaptopHostName kernel: usb 9-1: PM: failed to resume async: error -5 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8 Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0 Dec 31 12:13:32 LaptopHostName kernel: [drm] ring gfx_32823.1.1 was added Dec 31 12:13:32 LaptopHostName kernel: [drm] ring compute_32823.2.2 was added Dec 31 12:13:32 LaptopHostName kernel: [drm] ring sdma_32823.3.3 was added Dec 31 12:13:32 LaptopHostName kernel: [drm] ring gfx_32823.1.1 ib test pass Dec 31 12:13:32 LaptopHostName kernel: [drm] ring compute_32823.2.2 ib test pass Dec 31 12:13:32 LaptopHostName kernel: [drm] ring sdma_32823.3.3 ib test pass Dec 31 12:13:32 LaptopHostName kernel: PM: resume devices took 1.520 seconds Dec 31 12:13:32 LaptopHostName kernel: OOM killer enabled. Dec 31 12:13:32 LaptopHostName kernel: Restarting tasks ... Dec 31 12:13:32 LaptopHostName kernel: usb 9-1: USB disconnect, device number 7 Dec 31 12:13:32 LaptopHostName kernel: done. Dec 31 12:13:32 LaptopHostName kernel: random: crng reseeded on system resumption Dec 31 12:13:32 LaptopHostName kernel: PM: suspend exit Dec 31 12:13:32 LaptopHostName audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 31 12:13:32 LaptopHostName plasmashell: org.kde.pulseaudio: No object for name "alsa_output.usb-ACTIONS_Pebble_V3-00.analog-stereo" Dec 31 12:13:32 LaptopHostName audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 31 12:13:32 LaptopHostName bluetoothd: Controller resume with wake event 0x0 Dec 31 12:13:32 LaptopHostName kded6: org.kde.pulseaudio: No object for name "alsa_output.usb-ACTIONS_Pebble_V3-00.analog-stereo" Dec 31 12:13:32 LaptopHostName systemd-sleep: System returned from sleep operation 'suspend'. ░░ Subject: System sleep state suspend left ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ The system has now left the suspend sleep state. Dec 31 12:13:32 LaptopHostName systemd: systemd-suspend.service: Deactivated successfully. I also came across a python script which helps identify sleep problems, and this is the result (I'm gonna cut to the main line as the log is full of emojis and I want to spare you that): > 2024-12-31 12:25:21,494 INFO: Suspend count: 1 > 2024-12-31 12:25:21,494 INFO: ○ GPIOs active: ['29', '29', '29', '29', '29', '29', '29'] > 2024-12-31 12:25:21,494 INFO: Wakeup triggered from IRQ 7: GPIO Controller > 2024-12-31 12:25:21,494 DEBUG: Used Microsoft uPEP GUID in LPS0 _DSM > 2024-12-31 12:25:21,494 INFO: Woke up from IRQ 7: GPIO Controller > 2024-12-31 12:25:21,495 DEBUG: ACPI Lid (/proc/acpi/button/lid/LID0/state): closed > 2024-12-31 12:25:21,495 ERROR: ❌ Userspace suspended for 0:00:04.616088 ( 2024-12-31 12:25:21,496 ERROR: ❌ Did not reach hardware sleep state So, I assume this has to do with the GPU, as unplugging the hdmi let's the laptop sleep, and it's triggered by IRQ 7. I have found that IRQ7 is pinctrl_amd, so I'm not sure it's the responsible part, as it's a general-purpose GPIO driver as far as I know. /sys/kernel/irq/7/wakeup is enabled but I'm not sure it would be a good idea to disable it, and I have not even been able to find where to disable it for a test. Some of the things I have tried: - disable wakeup for the gpu drivers (only one of the cards seems to have the wakeup file though) - disabled everything on /proc/acpi/wakeup - Disabled wake up capability from every device with powertop - Tried the kernel parameters amdgpu.runpm=1 (default is 0), amdgpu.dpm=1 (-1 default), amdgpu.bapm=1 (-1 default), acpi.ec_no_wakeup=1 (default 0)
Asked by altz3r0 (11 rep)
Jan 2, 2025, 05:56 PM
Last activity: Jan 2, 2025, 06:44 PM