[TRACKING] Cannot resume from suspend on AMD

Twice now, I’ve run into an issue where my Framework (AMD, Fedora 39) will not resume from suspend. It will not even try. The power button does not work, and none of the keyboard keys will wake the laptop up.

I have to hold down the power button until the system shuts off.

This topic reminded me of the issue, though I am not sure if they’re related.

Anyone else seeing this?

2 Likes

Yes, on Mint Victoria here. Sometimes frantically typing or fast clicking the power button works. Sometimes closing the lid and reopening works.

1 Like

BIOS is a work in progress with updates coming. That said, you have updated (today) to match what is shared here?

And has suspend been tested using the power off menu?

For Mint, default kernel is a no go. Make sure you’re running with this.

i have seen this 2 out of maybe 40-50 laptop lid opens on ubuntu 22.04.3 oem c kernel too

1 Like
  • Nothing else attached, double-verified the kernel is active with uname -r ?

  • Anything in journalctl -b -1 ?

  • Anything else attached? Displays, etc? If so, how are they connected (hub/dock,expansion card/type) and which connection type.

1
6.1.0-1023-oem


  1. nothing attached, using rear usb c both sides.
    left side usb a
    right side hdmi which came with the laptop, newest one im assuming.

i share this right now as I had a 45s freeze, but no resume issue

Please open a ticket and we’ll take a look at the logs as I have not been able to reproduce. Please link to this post.

@Matt_Hartley After upgrading to the 3.03 BIOS, the problem seems to be worse (or is at least unchanged, at best).

I often walk away from my laptop and it goes into suspend, and I am not able to wake it at least once or twice a day.

Edit: This happens even when suspend is triggered via power button. This last time, the laptop seemed to still be on. The chassis was very hot and when I held down the power button to shut off and restart, the fan came on full blast for a good minute or two to dissipate the heat. Yikes.

1 Like

Trying to replicate this without any success. I’m fully up to date, kernel 6.5.9.

Because I cannot replicate, this is what we’re needing folks to do.

1 Like

I have no idea what Fedora component this would be related to… susp and sleep bring up no entries, and power brings up a lot but I am not sure which to pick…

perhaps unrelated (i’m on arch, not fedora) but my laptop was freezing 100% of the time when resuming from suspend after upgrading to the amd mainboard. i found that removing nvme.noacpi=1 (which i had previously added to fix freezing on the intel mainboard lol) fixed this.

Just a reminder, AMD users, do not use nvme.noacpi=1 as it will absolutely cause issues with suspend.

1 Like

I am also seeing this on an new Framework 13 AMD 76540U with Fedora 39 and 2xUSB-c, HDMI and USB-A expansion cards. It’s happened twice so far with nothing obvious to me in the logs (see below). The power button was blinking but not responsive, and I also had to eventually just hold it down to force a reboot.

$ uname -a
Linux fw 6.5.11-300.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Nov  8 22:37:57 UTC 2023 x86_64 GNU/Linux

$ sudo journalctl -r -b -1
Nov 16 09:40:09 fw kernel: PM: suspend entry (s2idle)
Nov 16 09:40:09 fw systemd-sleep[38541]: Entering sleep state 'suspend'...
Nov 16 09:40:09 fw systemd[1]: Starting systemd-suspend.service - System Suspend...
Nov 16 09:40:09 fw systemd[1]: Reached target sleep.target - Sleep.
Nov 16 09:40:06 fw wpa_supplicant[34658]: nl80211: deinit ifname=wlp1s0 disabled_11b_rates=0
Nov 16 09:40:06 fw wpa_supplicant[34658]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Nov 16 09:40:06 fw wpa_supplicant[34658]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Nov 16 09:40:06 fw NetworkManager[34455]: <info>  [1700145606.4175] device (wlp1s0): set-hw-addr: reset MAC address to 14:AC:60:46:7E:DB (unmanage)
Nov 16 09:40:06 fw chronyd[34329]: Source 174.142.148.226 offline
Nov 16 09:40:06 fw chronyd[34329]: Can't synchronise: no selectable sources
Nov 16 09:40:06 fw chronyd[34329]: Source 149.56.47.60 offline
Nov 16 09:40:06 fw chronyd[34329]: Source 68.69.221.61 offline
Nov 16 09:40:06 fw chronyd[34329]: Source 69.196.158.106 offline
Nov 16 09:40:06 fw NetworkManager[34455]: <info>  [1700145606.3731] device (wlp1s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 16 09:40:06 fw wpa_supplicant[34658]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
Nov 16 09:40:06 fw systemd-resolved[34125]: wlp1s0: Bus client reset DNS server list.
Nov 16 09:40:06 fw systemd-resolved[34125]: wlp1s0: Bus client set default route setting: no
Nov 16 09:40:06 fw avahi-daemon[34162]: Interface wlp1s0.IPv4 no longer relevant for mDNS.
Nov 16 09:40:06 fw avahi-daemon[34162]: Leaving mDNS multicast group on interface wlp1s0.IPv4 with address 192.168.1.150.
Nov 16 09:40:06 fw avahi-daemon[34162]: Withdrawing address record for 192.168.1.150 on wlp1s0.
Nov 16 09:40:06 fw avahi-daemon[34162]: Registering new address record for 192.168.1.150 on wlp1s0.IPv4.
Nov 16 09:40:06 fw avahi-daemon[34162]: New relevant interface wlp1s0.IPv4 for mDNS.
Nov 16 09:40:06 fw avahi-daemon[34162]: Joining mDNS multicast group on interface wlp1s0.IPv4 with address 192.168.1.150.
Nov 16 09:40:06 fw NetworkManager[34455]: <info>  [1700145606.1290] device (wlp1s0): set-hw-addr: set MAC address to 1A:91:7E:92:A5:49 (scanning)
Nov 16 09:40:06 fw avahi-daemon[34162]: Withdrawing address record for 192.168.1.150 on wlp1s0.
Nov 16 09:40:06 fw avahi-daemon[34162]: Leaving mDNS multicast group on interface wlp1s0.IPv4 with address 192.168.1.150.
Nov 16 09:40:06 fw avahi-daemon[34162]: Interface wlp1s0.IPv4 no longer relevant for mDNS.
Nov 16 09:40:06 fw avahi-daemon[34162]: Interface wlp1s0.IPv6 no longer relevant for mDNS.
Nov 16 09:40:06 fw audit[34429]: NETFILTER_CFG table=firewalld:10 family=1 entries=26 op=nft_unregister_rule pid=34429 subj=system_u:system_r:firewalld_t:s0 comm="firewalld"
Nov 16 09:40:06 fw avahi-daemon[34162]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address fe80::ff61:6cc9:6748:71fa.
Nov 16 09:40:06 fw avahi-daemon[34162]: Withdrawing address record for fe80::ff61:6cc9:6748:71fa on wlp1s0.
Nov 16 09:40:06 fw NetworkManager[34455]: <info>  [1700145606.0180] dhcp4 (wlp1s0): state changed no lease
Nov 16 09:40:06 fw NetworkManager[34455]: <info>  [1700145606.0180] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Nov 16 09:40:06 fw NetworkManager[34455]: <info>  [1700145606.0180] dhcp4 (wlp1s0): canceled DHCP transaction
Nov 16 09:40:06 fw wpa_supplicant[34658]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Nov 16 09:40:06 fw NetworkManager[34455]: <info>  [1700145606.0177] device (wlp1s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Nov 16 09:40:06 fw NetworkManager[34455]: <info>  [1700145606.0175] device (wlp1s0): supplicant interface state: completed -> disconnected
Nov 16 09:40:06 fw wpa_supplicant[34658]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Nov 16 09:40:06 fw wpa_supplicant[34658]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=34:3a:20:a4:f6:72 reason=3 locally_generated=1
Nov 16 09:40:05 fw kernel: wlp1s0: deauthenticating from 34:3a:20:a4:f6:72 by local choice (Reason: 3=DEAUTH_LEAVING)
Nov 16 09:40:05 fw audit[1]: 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'
Nov 16 09:40:05 fw systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Nov 16 09:40:05 fw systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Nov 16 09:40:05 fw NetworkManager[34455]: <info>  [1700145605.8413] device (wlp1s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Nov 16 09:40:05 fw NetworkManager[34455]: <info>  [1700145605.8411] manager: NetworkManager state is now ASLEEP
Nov 16 09:40:05 fw ModemManager[34426]: <info>  [sleep-monitor-systemd] system is about to suspend
Nov 16 09:40:05 fw NetworkManager[34455]: <info>  [1700145605.8407] device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 16 09:40:05 fw NetworkManager[34455]: <info>  [1700145605.8404] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Nov 16 09:40:05 fw systemd-logind[34270]: Suspending...
Nov 16 09:40:05 fw systemd-logind[34270]: Lid closed.
Nov 16 09:39:57 fw kernel: i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
Nov 16 09:39:53 fw firefox.desktop[36735]: ATTENTION: default value of option mesa_glthread overridden by environment.
Nov 16 09:39:51 fw wpa_supplicant[34658]: RRM: Unsupported radio measurement type 9
Nov 16 09:39:46 fw firefox.desktop[36735]: ATTENTION: default value of option mesa_glthread overridden by environment.
Nov 16 09:39:46 fw firefox.desktop[36735]: ATTENTION: default value of option mesa_glthread overridden by environment.
Nov 16 09:39:46 fw firefox.desktop[36735]: ATTENTION: default value of option mesa_glthread overridden by environment.
Nov 16 09:39:44 fw firefox.desktop[36735]: ATTENTION: default value of option mesa_glthread overridden by environment.
Nov 16 09:39:23 fw firefox.desktop[36735]: ATTENTION: default value of option mesa_glthread overridden by environment.
Nov 16 09:39:23 fw firefox.desktop[36735]: ATTENTION: default value of option mesa_glthread overridden by environment.
Nov 16 09:38:18 fw wpa_supplicant[34658]: RRM: Unsupported radio measurement type 9

Confirming you’re on the latest BIOS?

sudo dmidecode -s bios-version

If you are on 3.03, please run this as sudo and report back:

sudo python3 amd_s2idle.py

Yup, bios 3.03. I ran amd_s2idle.py from drm / amd · GitLab

1st attempt: it suspended and then shortly afterwards rebooted the machine
2nd attempt: it suspended the machine, but wouldn’t wake up (reproduced the bug)
3rd attempt: it suspended, and woke up once and then exited.

Here are the outputs for all the attempts: Filebin | lq8rgnovrxkv0ozo

(The discussion board won’t let me post the entire log file.)

2 Likes

Everyone experiencing this, on a hunch. Can you list what is attached to your Framework laptops (AMD Ryzen 7040 Series only):

  • Peripherals
  • Displays (how attached; USB, USB hub/dock, HDMI or DP expansion card - please be detailed)

I’m going to try and replicate here before sending this off to engineering.


Appreciate this, thank you.

@Matt_Hartley I’m running an AMD 76540U, Fedora 39. 2xUSB-c, HDMI and USB-A expansion cards, with no peripherals or displays.

@Matt_Hartley Ryzen 5 7640U, Fedora 39, 2xUSB-C, HDMI, USB-A expansion cards.

Looks like @jonp and I have the same expansion cards!

Displays are irrelevant, but has happened with:

  • Standalone (no external displays)
  • USB-C display (to 1 monitor, then daisy-chained via DP to another)

I wonder if this is related (based on what I saw with the amd_s2idle.py behaviour), but a few times now I’ve had my machine restart after suspending (similar to attempt #1 above).

Nothing obvious to me in the logs:

jp@fw:~$ sudo journalctl -r -b -1 | head -n 41
Nov 20 13:10:18 fw systemd[1]: Starting systemd-suspend.service - System Suspend...
Nov 20 13:10:18 fw wpa_supplicant[2181]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Nov 20 13:10:18 fw systemd[1]: Reached target sleep.target - Sleep.
Nov 20 13:10:18 fw NetworkManager[1708]: <info>  [1700503818.3028] device (wlp1s0): set-hw-addr: reset MAC address to 14:AC:60:46:7E:DB (unmanage)
Nov 20 13:10:18 fw chronyd[1596]: Source 206.108.0.133 offline
Nov 20 13:10:18 fw chronyd[1596]: Can't synchronise: no selectable sources
Nov 20 13:10:18 fw chronyd[1596]: Source 68.233.120.40 offline
Nov 20 13:10:18 fw chronyd[1596]: Source 158.69.20.38 offline
Nov 20 13:10:18 fw chronyd[1596]: Source 173.183.146.26 offline
Nov 20 13:10:18 fw NetworkManager[1708]: <info>  [1700503818.2621] device (wlp1s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 20 13:10:18 fw NetworkManager[1708]: <info>  [1700503818.2618] device (wlp1s0): supplicant interface state: disconnected -> interface_disabled
Nov 20 13:10:18 fw NetworkManager[1708]: <info>  [1700503818.1923] device (wlp1s0): set-hw-addr: set MAC address to 7E:1B:0E:66:7B:BC (scanning)
Nov 20 13:10:18 fw audit[1674]: NETFILTER_CFG table=firewalld:28 family=1 entries=26 op=nft_unregister_rule pid=1674 subj=system_u:system_r:firewalld_t:s0 comm="firewalld"
Nov 20 13:10:18 fw systemd-resolved[1386]: wlp1s0: Bus client reset DNS server list.
Nov 20 13:10:18 fw systemd-resolved[1386]: wlp1s0: Bus client set default route setting: no
Nov 20 13:10:18 fw avahi-daemon[1422]: Interface wlp1s0.IPv4 no longer relevant for mDNS.
Nov 20 13:10:18 fw avahi-daemon[1422]: Leaving mDNS multicast group on interface wlp1s0.IPv4 with address 192.168.2.79.
Nov 20 13:10:18 fw avahi-daemon[1422]: Withdrawing address record for 192.168.2.79 on wlp1s0.
Nov 20 13:10:18 fw NetworkManager[1708]: <info>  [1700503818.0779] dhcp4 (wlp1s0): state changed no lease
Nov 20 13:10:18 fw avahi-daemon[1422]: Interface wlp1s0.IPv6 no longer relevant for mDNS.
Nov 20 13:10:18 fw NetworkManager[1708]: <info>  [1700503818.0779] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Nov 20 13:10:18 fw avahi-daemon[1422]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address fe80::a660:1e6a:259c:c26c.
Nov 20 13:10:18 fw NetworkManager[1708]: <info>  [1700503818.0779] dhcp4 (wlp1s0): canceled DHCP transaction
Nov 20 13:10:18 fw avahi-daemon[1422]: Withdrawing address record for fe80::a660:1e6a:259c:c26c on wlp1s0.
Nov 20 13:10:18 fw wpa_supplicant[2181]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
Nov 20 13:10:18 fw NetworkManager[1708]: <info>  [1700503818.0774] device (wlp1s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Nov 20 13:10:18 fw wpa_supplicant[2181]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Nov 20 13:10:18 fw NetworkManager[1708]: <info>  [1700503818.0772] device (wlp1s0): supplicant interface state: completed -> disconnected
Nov 20 13:10:18 fw wpa_supplicant[2181]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Nov 20 13:10:18 fw wpa_supplicant[2181]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=02:ec:da:f2:2b:e3 reason=3 locally_generated=1
Nov 20 13:10:17 fw kernel: wlp1s0: deauthenticating from 02:ec:da:f2:2b:e3 by local choice (Reason: 3=DEAUTH_LEAVING)
Nov 20 13:10:17 fw audit[1]: 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'
Nov 20 13:10:17 fw systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Nov 20 13:10:17 fw systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Nov 20 13:10:17 fw NetworkManager[1708]: <info>  [1700503817.9169] device (wlp1s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Nov 20 13:10:17 fw NetworkManager[1708]: <info>  [1700503817.9167] manager: NetworkManager state is now ASLEEP
Nov 20 13:10:17 fw ModemManager[1672]: <info>  [sleep-monitor-systemd] system is about to suspend
Nov 20 13:10:17 fw NetworkManager[1708]: <info>  [1700503817.9163] device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Nov 20 13:10:17 fw NetworkManager[1708]: <info>  [1700503817.9161] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Nov 20 13:10:17 fw systemd-logind[1509]: Suspending...
Nov 20 13:10:17 fw systemd-logind[1509]: Lid closed.