Suspend exits immediately after installation of m2 ssd (nvme)

Hi, I’ve been running Fedora 35 for a while, 34 before that, the KDE spin using X11 with the proprietary nvidia driver. I’ve also been using Nvidia’s power management Chapter 21. Configuring Power Management Support in order to keep opencl alive if an app using it is running when my desktop machine(Ryzen 5 3600, RTX 2060) suspends, which it does daily in my usage pattern.

Yesterday I did two things at once:

  • installed an M2 ssd (nvme)
  • ran sudo dnf update -y which upgraded the kernel from 5.14 → 5.15 among other things(bi-weekly update)

After both of those things the machine wakes immediately after suspend. It’s the same if I boot with the 5.14 kernel and if I unplug all usb devices bar the keyboard.

I would have suspected an issue with the nvidia card but … the nvidia suspend and resume and hibernate services are enabled and seem to trigger alright (Howto/NVIDIA - RPM Fusion )

These are log entries from successful suspend and immadiate wake:

dec 01 07:07:12 feds systemd[1]: Reached target Sleep.
dec 01 07:07:12 feds systemd[1]: Starting NVIDIA system suspend actions...
dec 01 07:07:12 feds suspend[4407]: nvidia-suspend.service
dec 01 07:07:12 feds logger[4407]: <13>Dec  1 07:07:12 suspend: nvidia-suspend.service
dec 01 07:07:12 feds kernel: snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 10
dec 01 07:07:13 feds systemd[1]: nvidia-suspend.service: Deactivated successfully.
dec 01 07:07:13 feds systemd[1]: Finished NVIDIA system suspend actions.
dec 01 07:07:13 feds audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-suspend comm="sy>
dec 01 07:07:13 feds audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-suspend comm="sys>
dec 01 07:07:13 feds systemd[1]: Starting System Suspend...
dec 01 07:07:13 feds systemd-sleep[4431]: Entering sleep state 'suspend'...
dec 01 07:07:13 feds kernel: PM: suspend entry (deep)
dec 01 07:07:15 feds kernel: Filesystems sync: 1.659 seconds

dec 01 07:07:20 feds kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
dec 01 07:07:20 feds kernel: OOM killer disabled.
dec 01 07:07:20 feds kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
dec 01 07:07:20 feds kernel: printk: Suspending console(s) (use no_console_suspend to debug)
dec 01 07:07:20 feds kernel: sd 0:0:0:0: [sda] Stopping disk
dec 01 07:07:20 feds kernel: sd 3:0:0:0: [sdc] Stopping disk
dec 01 07:07:20 feds kernel: sd 2:0:0:0: [sdb] Stopping disk
dec 01 07:07:20 feds kernel: PM: suspend devices took 1.141 seconds
dec 01 07:07:20 feds kernel: ACPI: PM: Preparing to enter system sleep state S3
dec 01 07:07:20 feds kernel: ACPI: PM: Saving platform NVS memory
dec 01 07:07:20 feds kernel: Disabling non-boot CPUs ...
dec 01 07:07:20 feds kernel: smpboot: CPU 1 is now offline
dec 01 07:07:20 feds kernel: smpboot: CPU 2 is now offline
dec 01 07:07:20 feds kernel: smpboot: CPU 3 is now offline
dec 01 07:07:20 feds kernel: smpboot: CPU 4 is now offline
dec 01 07:07:20 feds kernel: smpboot: CPU 5 is now offline
dec 01 07:07:20 feds kernel: smpboot: CPU 6 is now offline
dec 01 07:07:20 feds kernel: smpboot: CPU 7 is now offline
dec 01 07:07:20 feds kernel: smpboot: CPU 8 is now offline
dec 01 07:07:20 feds kernel: smpboot: CPU 9 is now offline
dec 01 07:07:20 feds kernel: smpboot: CPU 10 is now offline
dec 01 07:07:20 feds kernel: smpboot: CPU 11 is now offline
dec 01 07:07:20 feds kernel: ACPI: PM: Low-level resume complete
dec 01 07:07:20 feds kernel: ACPI: PM: Restoring platform NVS memory
dec 01 07:07:20 feds kernel: LVT offset 0 assigned for vector 0x400
dec 01 07:07:20 feds kernel: Enabling non-boot CPUs ...
dec 01 07:07:20 feds kernel: x86: Booting SMP configuration:
dec 01 07:07:20 feds kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
dec 01 07:07:20 feds kernel: microcode: CPU1: patch_level=0x08701021
dec 01 07:07:20 feds kernel: ACPI: \_SB_.PLTF.C002: Found 2 idle states
dec 01 07:07:20 feds kernel: CPU1 is up


dec 01 07:07:20 feds kernel: usb usb3: root hub lost power or was reset
dec 01 07:07:20 feds kernel: usb usb4: root hub lost power or was reset
dec 01 07:07:20 feds kernel: nvme nvme0: 15/0/0 default/read/poll queues
dec 01 07:07:20 feds kernel: ata2: SATA link down (SStatus 0 SControl 300)
dec 01 07:07:20 feds kernel: ata6: SATA link down (SStatus 0 SControl 330)
dec 01 07:07:20 feds kernel: usb 1-7: reset full-speed USB device number 2 using xhci_hcd
dec 01 07:07:20 feds kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
dec 01 07:07:20 feds kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
dec 01 07:07:20 feds kernel: ata1.00: supports DRM functions and may not be fully accessible
dec 01 07:07:20 feds kernel: ata4.00: supports DRM functions and may not be fully accessible
dec 01 07:07:20 feds kernel: ata1.00: disabling queued TRIM support
dec 01 07:07:20 feds kernel: ata4.00: NCQ Send/Recv Log not supported
dec 01 07:07:20 feds kernel: ata1.00: supports DRM functions and may not be fully accessible
dec 01 07:07:20 feds kernel: ata4.00: supports DRM functions and may not be fully accessible
dec 01 07:07:20 feds kernel: ata4.00: NCQ Send/Recv Log not supported
dec 01 07:07:20 feds kernel: ata1.00: disabling queued TRIM support
dec 01 07:07:20 feds kernel: ata4.00: configured for UDMA/133
dec 01 07:07:20 feds kernel: ata1.00: configured for UDMA/133
dec 01 07:07:20 feds kernel: PM: resume devices took 0.715 seconds
dec 01 07:07:20 feds kernel: OOM killer enabled.
dec 01 07:07:20 feds kernel: Restarting tasks ... done.
dec 01 07:07:20 feds kernel: thermal thermal_zone1: failed to read out thermal zone (-61)
dec 01 07:07:20 feds kernel: PM: suspend exit
dec 01 07:07:20 feds systemd-resolved[891]: Clock change detected. Flushing caches.
dec 01 07:07:20 feds systemd-sleep[4431]: System returned from sleep state.
dec 01 07:07:20 feds upowerd[944]: treating change event as add on /sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-7
dec 01 07:07:20 feds upowerd[944]: treating change event as add on /sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-7
dec 01 07:07:21 feds kernel: ata5: failed to resume link (SControl 0)
dec 01 07:07:21 feds kernel: ata5: SATA link down (SStatus 0 SControl 0)
dec 01 07:07:21 feds systemd[1]: systemd-suspend.service: Deactivated successfully.
dec 01 07:07:21 feds systemd[1]: Finished System Suspend.
dec 01 07:07:21 feds audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="s>
dec 01 07:07:21 feds audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="sy>
dec 01 07:07:21 feds systemd[1]: systemd-suspend.service: Consumed 1.185s CPU time.
dec 01 07:07:21 feds systemd[1]: Stopped target Sleep.
dec 01 07:07:21 feds systemd[1]: Reached target Suspend.
dec 01 07:07:21 feds systemd[1]: Starting NVIDIA system resume actions...
dec 01 07:07:21 feds systemd[1]: Stopped target Suspend.
dec 01 07:07:21 feds suspend[4596]: nvidia-resume.service
dec 01 07:07:21 feds logger[4596]: <13>Dec  1 07:07:21 suspend: nvidia-resume.service
dec 01 07:07:21 feds systemd-logind[938]: Operation 'sleep' finished.

“ACPI: PM: Low-level resume complete” seems a bit ambiguous. Anyway the nvidia services appear OK, so what might be the issue?

I would still try to temporarily replace the NVIDIA driver with NOUVEAU, just to rule it completely out as the origin of the issue.

These areas are related, and when it comes to proprietary drivers (I often find their behavior and journaling unpredictable), I don’t want to take the logs too literally (I know, that’s an opinion rather than a fact). But as we have no other clues… I think its worth a try.

Hi Christopher,

Thanks for the suggestion. I uninstalled it as per Howto/NVIDIA - RPM Fusion then did the steps detailed under “Recover from NVIDIA installer” in the same document. Rebooted and then tried to suspend: symptom persists, immediate wake.

The logs now look like so:

dec 01 19:19:05 feds NetworkManager[995]: <info>  [1638382745.5853] device (eno1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-s>
dec 01 19:19:05 feds kernel: r8169 0000:04:00.0 eno1: Link is Down
dec 01 19:19:05 feds chronyd[937]: Source 194.58.200.20 offline
dec 01 19:19:05 feds chronyd[937]: Source 193.182.111.141 offline
dec 01 19:19:05 feds chronyd[937]: Source 91.209.0.19 offline
dec 01 19:19:05 feds chronyd[937]: Can't synchronise: no selectable sources
dec 01 19:19:05 feds chronyd[937]: Source 194.58.205.20 offline
dec 01 19:19:05 feds audit[973]: NETFILTER_CFG table=firewalld:8 family=1 entries=5 op=nft_unregister_rule pid=973 subj=system_u:system_r:firewalld_t:s0 c>
dec 01 19:19:05 feds systemd-resolved[855]: eno1: Bus client reset DNS server list.
dec 01 19:19:05 feds kscreenlocker_greet[3282]: Qt: Session management error: networkIdsList argument is NULL
dec 01 19:19:05 feds kscreenlocker_greet[3282]: file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.desktop/contents/components/UserList.qml:4>
dec 01 19:19:05 feds systemd[1]: Reached target Sleep.
dec 01 19:19:05 feds systemd[1]: Starting System Suspend...
dec 01 19:19:05 feds systemd-sleep[3339]: Entering sleep state 'suspend'...
dec 01 19:19:05 feds kernel: PM: suspend entry (deep)
dec 01 19:19:05 feds kscreenlocker_greet[3282]: file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.desktop/contents/components/UserList.qml:4>
dec 01 19:19:05 feds kernel: Filesystems sync: 0.042 seconds
dec 01 19:19:18 feds kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
dec 01 19:19:18 feds kernel: OOM killer disabled.
dec 01 19:19:18 feds kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
dec 01 19:19:18 feds kernel: printk: Suspending console(s) (use no_console_suspend to debug)
dec 01 19:19:18 feds kernel: sd 0:0:0:0: [sda] Stopping disk
dec 01 19:19:18 feds kernel: sd 3:0:0:0: [sdc] Stopping disk
dec 01 19:19:18 feds kernel: sd 2:0:0:0: [sdb] Stopping disk
dec 01 19:19:18 feds kernel: PM: suspend devices took 7.023 seconds
dec 01 19:19:18 feds kernel: ACPI: PM: Preparing to enter system sleep state S3
dec 01 19:19:18 feds kernel: ACPI: PM: Saving platform NVS memory
dec 01 19:19:18 feds kernel: Disabling non-boot CPUs ...
dec 01 19:19:18 feds kernel: smpboot: CPU 1 is now offline
dec 01 19:19:18 feds kernel: smpboot: CPU 2 is now offline
dec 01 19:19:18 feds kernel: smpboot: CPU 3 is now offline
dec 01 19:19:18 feds kernel: smpboot: CPU 4 is now offline
dec 01 19:19:18 feds kernel: smpboot: CPU 5 is now offline
dec 01 19:19:18 feds kernel: smpboot: CPU 6 is now offline
dec 01 19:19:18 feds kernel: smpboot: CPU 7 is now offline
dec 01 19:19:18 feds kernel: smpboot: CPU 8 is now offline
dec 01 19:19:18 feds kernel: smpboot: CPU 9 is now offline
dec 01 19:19:18 feds kernel: smpboot: CPU 10 is now offline
dec 01 19:19:18 feds kernel: smpboot: CPU 11 is now offline
dec 01 19:19:18 feds kernel: ACPI: PM: Low-level resume complete
dec 01 19:19:18 feds kernel: ACPI: PM: Restoring platform NVS memory
dec 01 19:19:18 feds kernel: LVT offset 0 assigned for vector 0x400
dec 01 19:19:18 feds kernel: Enabling non-boot CPUs ...
dec 01 19:19:18 feds kernel: x86: Booting SMP configuration:
dec 01 19:19:18 feds kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
dec 01 19:19:18 feds kernel: microcode: CPU1: patch_level=0x08701021
dec 01 19:19:18 feds kernel: ACPI: \_SB_.PLTF.C002: Found 2 idle states
dec 01 19:19:18 feds kernel: CPU1 is up
--
dec 01 19:19:18 feds kernel: ACPI: PM: Waking up from system sleep state S3
dec 01 19:19:18 feds kernel: usb usb1: root hub lost power or was reset
dec 01 19:19:18 feds kernel: usb usb2: root hub lost power or was reset
dec 01 19:19:18 feds kernel: sd 2:0:0:0: [sdb] Starting disk
dec 01 19:19:18 feds kernel: sd 0:0:0:0: [sda] Starting disk
dec 01 19:19:18 feds kernel: sd 3:0:0:0: [sdc] Starting disk
dec 01 19:19:18 feds kernel: nvme nvme0: 15/0/0 default/read/poll queues
dec 01 19:19:18 feds kernel: usb usb3: root hub lost power or was reset
dec 01 19:19:18 feds kernel: usb usb4: root hub lost power or was reset
dec 01 19:19:18 feds kernel: ata6: SATA link down (SStatus 0 SControl 300)
dec 01 19:19:18 feds kernel: ata2: SATA link down (SStatus 0 SControl 300)
dec 01 19:19:18 feds kernel: usb 1-8: reset full-speed USB device number 3 using xhci_hcd
dec 01 19:19:18 feds kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
dec 01 19:19:18 feds kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
dec 01 19:19:18 feds kernel: ata1.00: supports DRM functions and may not be fully accessible
dec 01 19:19:18 feds kernel: ata4.00: supports DRM functions and may not be fully accessible
dec 01 19:19:18 feds kernel: ata1.00: disabling queued TRIM support
dec 01 19:19:18 feds kernel: ata4.00: NCQ Send/Recv Log not supported
dec 01 19:19:18 feds kernel: ata4.00: supports DRM functions and may not be fully accessible
dec 01 19:19:18 feds kernel: ata1.00: supports DRM functions and may not be fully accessible
dec 01 19:19:18 feds kernel: ata4.00: NCQ Send/Recv Log not supported
dec 01 19:19:18 feds kernel: ata1.00: disabling queued TRIM support
dec 01 19:19:18 feds kernel: ata4.00: configured for UDMA/133
dec 01 19:19:18 feds kernel: ata1.00: configured for UDMA/133
dec 01 19:19:18 feds kernel: usb 1-7: reset full-speed USB device number 2 using xhci_hcd
dec 01 19:19:18 feds kernel: ata5: failed to resume link (SControl 0)
dec 01 19:19:18 feds kernel: ata5: SATA link down (SStatus 0 SControl 0)
dec 01 19:19:18 feds kernel: PM: resume devices took 1.179 seconds
dec 01 19:19:18 feds kernel: OOM killer enabled.
dec 01 19:19:18 feds kernel: Restarting tasks ... done.
dec 01 19:19:18 feds kernel: thermal thermal_zone1: failed to read out thermal zone (-61)
dec 01 19:19:18 feds kernel: PM: suspend exit
dec 01 19:19:18 feds audit[1]: 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 01 19:19:18 feds audit[1]: 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 01 19:19:18 feds systemd-resolved[855]: Clock change detected. Flushing caches.
dec 01 19:19:18 feds rtkit-daemon[888]: The canary thread is apparently starving. Taking action.
dec 01 19:19:18 feds systemd-sleep[3339]: System returned from sleep state.
dec 01 19:19:18 feds rtkit-daemon[888]: Demoting known real-time threads.
dec 01 19:19:18 feds systemd[1]: Starting Load/Save RF Kill Switch Status...
dec 01 19:19:18 feds bluetoothd[879]: Endpoint unregistered: sender=:1.75 path=/MediaEndpoint/A2DPSource/ldac
dec 01 19:19:18 feds systemd[1]: systemd-suspend.service: Deactivated successfully.
dec 01 19:19:18 feds bluetoothd[879]: Endpoint unregistered: sender=:1.75 path=/MediaEndpoint/A2DPSource/aac
dec 01 19:19:18 feds systemd[1]: Finished System Suspend.
dec 01 19:19:18 feds bluetoothd[879]: Endpoint unregistered: sender=:1.75 path=/MediaEndpoint/A2DPSink/sbc
dec 01 19:19:18 feds systemd[1]: Stopped target Sleep.
dec 01 19:19:18 feds bluetoothd[879]: Endpoint unregistered: sender=:1.75 path=/MediaEndpoint/A2DPSource/sbc
dec 01 19:19:18 feds systemd[1]: Reached target Suspend.
dec 01 19:19:18 feds bluetoothd[879]: Endpoint unregistered: sender=:1.75 path=/MediaEndpoint/A2DPSink/sbc_xq
dec 01 19:19:18 feds systemd[1]: Stopped target Suspend.
dec 01 19:19:18 feds bluetoothd[879]: Endpoint unregistered: sender=:1.75 path=/MediaEndpoint/A2DPSource/sbc_xq
dec 01 19:19:18 feds systemd-logind[894]: Operation 'sleep' finished.
dec 01 19:19:18 feds bluetoothd[879]: Endpoint unregistered: sender=:1.75 path=/MediaEndpoint/A2DPSource/faststream
dec 01 19:19:18 feds NetworkManager[995]: <info>  [1638382758.2771] manager: sleep: wake requested (sleeping: yes  enabled: yes)
dec 01 19:19:18 feds bluetoothd[879]: Endpoint unregistered: sender=:1.75 path=/MediaEndpoint/A2DPSource/faststream_duplex
dec 01 19:19:18 feds NetworkManager[995]: <info>  [1638382758.2775] device (eno1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
dec 01 19:19:18 feds rtkit-daemon[888]: Successfully demoted thread 2546 of process 2384 (/usr/lib64/firefox/firefox).
dec 01 19:19:18 feds rtkit-daemon[888]: Successfully demoted thread 1960 of process 1916 (/usr/bin/pipewire).
dec 01 19:19:18 feds rtkit-daemon[888]: Successfully demoted thread 1916 of process 1916 (/usr/bin/pipewire).
dec 01 19:19:18 feds rtkit-daemon[888]: Successfully demoted thread 1957 of process 1918 (/usr/bin/pipewire-pulse).
dec 01 19:19:18 feds rtkit-daemon[888]: Successfully demoted thread 1918 of process 1918 (/usr/bin/pipewire-pulse).
dec 01 19:19:18 feds rtkit-daemon[888]: Demoted 5 threads.
dec 01 19:19:18 feds ModemManager[971]: <info>  [sleep-monitor] system is resuming

Sorry for the longish log, I just wanted to paint a somewhat meaningful account.
I’m not sure it is though… “ACPI: PM: Low-level resume complete” might be when it wakes, and things happen after, it’s hard to say precisely if anything has to do with the wakeup signal.

A little later in the wakeup process there’s a similar time jump thing as in the last log:

dec 01 19:19:20 feds systemd[1]: Starting Network Manager Script Dispatcher Service...
dec 01 19:19:20 feds systemd[1]: Started Network Manager Script Dispatcher Service.
dec 01 19:19:20 feds 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'
dec 01 19:19:20 feds NetworkManager[995]: <info>  [1638382760.0683] device (eno1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
dec 01 19:19:20 feds NetworkManager[995]: <info>  [1638382760.0684] device (eno1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
dec 01 19:19:20 feds NetworkManager[995]: <info>  [1638382760.0686] manager: NetworkManager state is now CONNECTED_LOCAL
dec 01 19:19:20 feds NetworkManager[995]: <info>  [1638382760.0688] manager: NetworkManager state is now CONNECTED_SITE
dec 01 19:19:20 feds NetworkManager[995]: <info>  [1638382760.0689] policy: set 'RTL8125 2.5GbE' (eno1) as default for IPv4 routing and DNS
dec 01 19:19:20 feds NetworkManager[995]: <info>  [1638382760.0692] device (eno1): Activation: successful, device activated.
dec 01 19:19:20 feds NetworkManager[995]: <info>  [1638382760.0695] manager: NetworkManager state is now CONNECTED_GLOBAL
dec 01 19:19:20 feds systemd-resolved[855]: eno1: Bus client set default route setting: yes
dec 01 19:19:20 feds systemd-resolved[855]: eno1: Bus client set DNS server list to: 192.168.0.1
dec 01 19:19:20 feds systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive.
dec 01 19:19:20 feds chronyd[937]: Forward time jump detected!

That might be standard issue though (I don’t go looking in the journal enough when things are working as intended :slight_smile: )

Assuming that this is an ACPI issue, I found that: 12.04 - Why does my laptop resume immediately after suspend? - Ask Ubuntu

Maybe the solution using acpitool can help you as well (its in the fedora repo).

Thanks again, I tried disabling the two wake-enabled usb devices (part of the motherboard controller) with the acpitool, as the first reply indicated, to no effect. (the other wakeupers were the PCI controller on the motherboard…nvme?)
Then I removed all usb devices except for the keyboard again, and removed the ethernet cable as well, rebooted, then tried to suspend with the same result.

I’ll read up on the acpitool some more, and in the weekend if status quo both try without the m2 ssd and additionally perhaps update the motherboard bios. It’s not ancient but it isn’t the newest either. Both are sort of last-ditch efforts but I’d really rather find out what causes the issue or what can fix it as suspending is very handy.

To see whether to troubleshoot the m2 further I took it out and booted the machine and tried to suspend. No issue.

So the problem wasn’t the 5.15 update most like, it was the m2 ssd.
This particular model (Kingston A2000) has had issues in Linux on past fw versions: https://media.kingston.com/support/downloads/SA2000_S5Z42109_RN.pdf with system freezes but the current fw (that my drive came with) is later than the fw version that supposedly fixed the freezing on linux issue.

(GitHub - vulgo/kingston-a2000-firmware-bin-linux: Kingston A2000 firmware S5Z42109 for Linux. S5Z42109.BIN as such is not applicable. I tried, before I found the fw version of my drive. The message was simply that the fw image was invalid).

Solid state drive/NVMe - ArchWiki “there should be non-zero entries:” (there are):
sudo nvme get-feature /dev/nvme0 -f 0x0c -H

get-feature:0xc (Autonomous Power State Transition), Current value:0x000001
	Autonomous Power State Transition Enable (APSTE): Enabled
	Auto PST Entries	.................
	Entry[ 0]   
	.................
	Idle Time Prior to Transition (ITPT): 100 ms
	Idle Transition Power State   (ITPS): 3
	.................
	Entry[ 1]   
	.................
	Idle Time Prior to Transition (ITPT): 100 ms
	Idle Transition Power State   (ITPS): 3
	.................
	Entry[ 2]   
	.................
	Idle Time Prior to Transition (ITPT): 100 ms
	Idle Transition Power State   (ITPS): 3
	.................
	Entry[ 3]   
	.................
	Idle Time Prior to Transition (ITPT): 0 ms
	Idle Transition Power State   (ITPS): 0

“KINGSTON SA2000M81000G”
fw version: “S5Z44106”

(I bought it believing the new fw version had fixed the freezing problem in Linux, and , well, any problem in Linux, for I’ve seen no newer reports of issues with it. So it doesn’t freeze, it just prevents the machine from suspending)

Any suggestions? I will go ahead and update the bios but it’s one version and there isn’t anything about PCI-E or nvme in there. Is there something I can check with the nvme cli or smartmon?
I haven’t found any references to not suspending with an nvme / this nvme.

The only thing in the journal regarding “nvme” from when the machine tries to suspend and then wakes immediately is
nvme nvme0: 15/0/0 default/read/poll queues

Edit. I updated the bios (f13g- > f14, no difference). I tried entering the power save mode in Win10, success. (Neither Fedora nor Windows are on this Kingston nvme) . Feel free to suggest anything to get this thing suspending in Fedora : )

I hope it’s not bad form to make yet another reply. I wish to explain how the selected answer is the answer:

acpitool -w has the same list items whether the nvme ssd (Kingston A2000) is connected or not, however
7. GPP0 S4 *disabled pci:0000:00:01.1 becomes enabled.
Disabling it temporarily with sudo acpitool -W 7 made suspend work. I followed a link in the thread you provided and landed at systemd - ArchWiki

In order to make GPP0 unable to wake the machine at boot I created

#    Path                  Mode UID  GID  Age Argument
w    /proc/acpi/wakeup     -    -    -    -   GPP0

as /etc/tmpfiles.d/disable-nvme-wake.conf
and on reboot GPP0 is disabled for wakeupability and the machine suspends normally :slight_smile:

2 Likes

Wonderful troubleshooting skills :+1: