This is most likely my combination of FW13 and Crucial NVMe, but will probably affect others.
Here’s the bug 218736 – 6.9.0-rc4-: NVME disk disappears on s2idle resume on Framework 13 AMD.
Posting here because I probably wont have time to investigate further before 6.9.0 is released and want to get it on the radar of others.
FWIW no issues suspending into/out of s2idle with Fedora’s -rc6 build. However I’m using a Samsung 990 PRO NVMe.
May 06 21:04:39 kernel: PM: suspend entry (s2idle)
May 06 21:04:39 kernel: Filesystems sync: 0.014 seconds
May 06 21:05:22 kernel: Freezing user space processes
May 06 21:05:22 kernel: Freezing user space processes completed (elapsed 0.001 seconds)
May 06 21:05:22 kernel: OOM killer disabled.
May 06 21:05:22 kernel: Freezing remaining freezable tasks
May 06 21:05:22 kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
May 06 21:05:22 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
May 06 21:05:22 kernel: atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug
May 06 21:05:22 kernel: queueing ieee80211 work while going to suspend
May 06 21:05:22 kernel: PM: suspend devices took 0.141 seconds
May 06 21:05:22 kernel: pcieport 0000:00:08.3: quirk: disabling D3cold for suspend
May 06 21:05:22 kernel: ACPI: EC: interrupt blocked
May 06 21:05:22 kernel: ACPI: EC: interrupt unblocked
May 06 21:05:22 kernel: nvme nvme0: D3 entry latency set to 10 seconds
May 06 21:05:22 kernel: [drm] PCIE GART of 512M enabled (table at 0x000000807FD00000).
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
May 06 21:05:22 kernel: nvme nvme0: 16/0/0 default/read/poll queues
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
May 06 21:05:22 kernel: [drm] DMUB HPD callback: link_index=8
May 06 21:05:22 kernel: [drm] DMUB HPD callback: link_index=7
May 06 21:05:22 kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
May 06 21:05:22 kernel: amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
May 06 21:05:22 kernel: [drm] ring gfx_32772.1.1 was added
May 06 21:05:22 kernel: [drm] ring compute_32772.2.2 was added
May 06 21:05:22 kernel: [drm] ring sdma_32772.3.3 was added
May 06 21:05:22 kernel: [drm] ring gfx_32772.1.1 ib test pass
May 06 21:05:22 kernel: [drm] ring compute_32772.2.2 ib test pass
May 06 21:05:22 kernel: [drm] ring sdma_32772.3.3 ib test pass
May 06 21:05:22 kernel: usb 7-1.4.2.3: reset high-speed USB device number 19 using xhci_hcd
May 06 21:05:22 kernel: PM: resume devices took 0.647 seconds
May 06 21:05:22 kernel: OOM killer enabled.
May 06 21:05:22 kernel: Restarting tasks ... done.
May 06 21:05:22 kernel: random: crng reseeded on system resumption
May 06 21:05:22 kernel: PM: suspend exit