I am on the newest version of Fedora running 11th gen i5.
I’d say 1/10 times my computer enters sleep mode, I cannot wake it by pressing a keyboard button, moving my mouse, etc. I have to hold down the power button to turn it off and reboot it.
Does anyone else have this problem?
Do you have an external monitor at hand? I had what sounds like a very similar experience, and in my case, when this happened, if I plugged in an external monitor I could see that the laptop was running, just the built-in screen was black, and the keyboard/touchpad/powerbutton were “dead” until I did a hard reset by holding power button for 10 seconds.
It took a long time for customer service and me to work it out, but in the end I’m pretty certain one (or both) of the following fixed the issue for me:
I can’t say which was the issue, but I lean towards the mainboard reset fixing my problem. It’s possible that flashing to the 3.03 left something in a wonky state. I did this fix on Jan 7th IIRC, and haven’t had an issue since.
It does happen most often with an external monitor plugged in. The power light remains on but everything becomes unresponsive.
How do I update SSD firmware on Linux?
Thanks for the info!
That sounds like it might be a different problem than I had - as in my case, when my machine ostensibly died, I could still plug in an external monitor/keyboard/mouse and use it. In my case, the input cover would die - the power light would be off too, but the computer itself was running.
Regarding updating the SSD firmware, it was pretty complex. Start by reading this thread:
Don’t give up hope!
After understanding the issue as described in the thread, I used the script here (note: it’s been moved, but read it and follow instructions anyway):
Which BIOS/kernel are you using?
sudo dnf install lshw dmidecode -y && sudo dmidecode | grep -A3 'Vendor:\|Product:' && sudo lshw -C cpu | grep -A3 'product:\|vendor:' && uname -r
Provide the output from the above please.
Since the error forces a reboot, let’s take a look at the previous boot when you’re forced to restart.
Suspend. It fails to resume, you’re forced to power off, power on.
Run the following at the new boot up:
journalctl -b -1 | grep -i suspend | less
Paste the output here. I’m looking to see if we can get an idea where the resume is failing.
I’ve literally just resolved this issue myself. I encountered it with deep sleep enabled, and a network drive mounted.
The network drive being in use would cause the system to never manage to enter deep sleep, which caused a rapid switching between waking and sleeping. If that happened enough times then it would cause the whole system to freeze up, requiring a forced power off to fix.
Now that I make sure any network mounts in Files (SFTP, FTP, etc) are unmounted before suspending, my problems have gone.
I know this is a super specific situation I’ve described, but hope that helps you investigate at the very least!
Reporting that I’m also facing similar if not the same problems. Running the KDE spin of Fedora on my Ryzen 7 mainboard and when asleep for prolonged periods of time it’ll sometimes refuse to wake up from sleep.
From what I’ve gathered from looking around the forums, it’s sometimes related to SSD firmware?? The Crucial P5 seemed to be somewhat infamous in the past, but I’m currently running Fedora KDE on a Crucial P3 at the moment, and I haven’t heard any issues with specifically those SSDs.
I’ll try to gather more data the next time it happens, including that journalctl comment mentioned.
Ah, yes, this would create some challenges. You would be surprised how common stuff like this is, but it never mentioned in the repro steps. Appreciate you sharing this.
I’d want to start here.
sudo python3 amd_s2idle.py
It seems for whatever reason, the specific issue of the laptop simply not waking up has disappearing magically. Although I’ve begun running into a slightly different problem now: Fedora KDE 39 - "The screen locker is broken"
Glad to hear this has been resolved, replied to the other thread.
I have the same issue I think. My laptop running fedora 39 will just randomly go to sleep while I’m in the middle of using it. In fact I tried to reply to this forum on my laptop and in the middle of typing it went to sleep and then the keyboard and trackpad became unresponsive on waking it. Very frustrating haha. Missing notes in class because of this.
Edit: I misread the post this seems like a different issue.
Hi,
I have the same problem, in my case it relates with the NVME flash it seems, sometimes I’m able to recover to the login screen and use the fingerprint reader, but the OS is fully on read-only mode.
I have TPM, secure boot and hw encryption. My storage volumes also use LUKS and BTRFS.
I remember that I didn’t have any issues until I activated the HW encryption, so I disabled it (I can live with LUKS), it’s not perfect yet, but now I can recover to running OS (it just takes 37 seconds), but the good part is that I can retrieve a log 
As you can see the NVME still takes a ton of time to wake up, I didn’t have this with a WD black 1TB flash module, now I have a Samsung SSD 990 PRO 4TB.
I’m trying to understand why the NVME takes so long to wake up, the same flash module with the same OS on a desktop wakes up just fine.
My laptop is a framework 13, with an AMD Ryzen 7 7840U w and 64GB Ram.
I don’t use my laptop that much and this is lingering for months now, and I had a hope that an update would fix it. But this issue basically renders the laptop useless, as I always revert to the desktop to work.
Here’s the relevant excerpt of the log:
[ 213.258653] ACPI: EC: interrupt blocked
[ 218.497501] ACPI: EC: interrupt unblocked
[ 255.993441] clocksource: Long readout interval, skipping watchdog check: cs_nsec: 37438863515 wd_nsec: 37438782019
[ 255.993861] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 255.993869] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 255.993874] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 255.993879] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 255.993884] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 255.993889] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 255.993893] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 255.993898] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 255.993903] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 255.993908] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 255.995747] AMD-Vi: IOMMU Event log restarting
[ 256.009590] [drm] PCIE GART of 512M enabled (table at 0x00000080FFD00000).
[ 256.009702] amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
[ 256.013821] amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
[ 256.083464] nvme nvme0: D3 entry latency set to 10 seconds
[ 256.086137] nvme nvme0: 16/0/0 default/read/poll queues
[ 256.204860] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[ 256.205146] amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
[ 256.205342] amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[ 256.205344] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 256.205345] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 256.205347] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[ 256.205348] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[ 256.205349] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[ 256.205350] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[ 256.205351] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[ 256.205352] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[ 256.205353] amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[ 256.205354] amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
[ 256.205355] amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
[ 256.205356] amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
[ 256.209613] [drm] ring gfx_32792.1.1 was added
[ 256.210103] [drm] ring compute_32792.2.2 was added
[ 256.210587] [drm] ring sdma_32792.3.3 was added
[ 256.210629] [drm] ring gfx_32792.1.1 ib test pass
[ 256.210654] [drm] ring compute_32792.2.2 ib test pass
[ 256.210727] [drm] ring sdma_32792.3.3 ib test pass
[ 256.218564] PM: resume devices took 0.216 seconds
[ 256.218753] OOM killer enabled.
[ 256.218759] Restarting tasks ... done.
[ 256.221353] random: crng reseeded on system resumption
[ 256.225440] PM: suspend exit
[ 256.436181] usb 1-4: reset full-speed USB device number 2 using xhci_hcd
[ 256.722288] usb 1-4: reset full-speed USB device number 2 using xhci_hcd
[ 259.018254] wlp1s0: authenticate with de:47:32:aa:19:ed (local address=e6:51:99:2b:3c:23)
[ 259.177169] wlp1s0: send auth to de:47:32:aa:19:ed (try 1/3)
[ 259.181985] wlp1s0: authenticated
[ 259.182791] wlp1s0: associate with de:47:32:aa:19:ed (try 1/3)
[ 259.200633] wlp1s0: RX AssocResp from de:47:32:aa:19:ed (capab=0x1511 status=0 aid=1)
[ 259.227593] wlp1s0: associated
In my previous message I saw a entry about the clock source, just to make it clear I’ve forced the clocksource to be hpet, the message is gone, but the behaviour is still the same:
[ 92.247118] PM: suspend entry (s2idle)
[ 92.265404] Filesystems sync: 0.018 seconds
[ 92.375915] Freezing user space processes
[ 92.377850] Freezing user space processes completed (elapsed 0.001 seconds)
[ 92.377865] OOM killer disabled.
[ 92.377867] Freezing remaining freezable tasks
[ 92.378791] Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
[ 92.378795] printk: Suspending console(s) (use no_console_suspend to debug)
[ 92.385982] atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug
[ 92.391152] queueing ieee80211 work while going to suspend
[ 92.613705] PM: suspend devices took 0.234 seconds
[ 92.614376] pcieport 0000:00:08.3: quirk: disabling D3cold for suspend
[ 92.615239] ACPI: EC: interrupt blocked
[ 97.327198] ACPI: EC: interrupt unblocked
[ 133.630772] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 133.630781] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 133.630785] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 133.630790] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 133.630794] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 133.630797] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 133.630801] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 133.630805] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 133.630809] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 133.630813] nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0x58e5e000 flags=0x0000]
[ 133.632313] AMD-Vi: IOMMU Event log restarting
[ 133.645008] [drm] PCIE GART of 512M enabled (table at 0x00000080FFD00000).
[ 133.645099] amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
[ 133.647614] amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
[ 133.745361] nvme nvme0: D3 entry latency set to 10 seconds
[ 133.747905] nvme nvme0: 16/0/0 default/read/poll queues
[ 133.747983] nvme nvme0: async event result 00080202
[ 133.840660] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[ 133.840751] amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
[ 133.841102] amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[ 133.841104] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 133.841106] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 133.841107] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[ 133.841108] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[ 133.841109] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[ 133.841110] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[ 133.841111] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[ 133.841112] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[ 133.841114] amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[ 133.841115] amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
[ 133.841116] amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
[ 133.841117] amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
[ 133.845977] [drm] ring gfx_32792.1.1 was added
[ 133.846541] [drm] ring compute_32792.2.2 was added
[ 133.847081] [drm] ring sdma_32792.3.3 was added
[ 133.847109] [drm] ring gfx_32792.1.1 ib test pass
[ 133.847138] [drm] ring compute_32792.2.2 ib test pass
[ 133.847252] [drm] ring sdma_32792.3.3 ib test pass
[ 133.852955] PM: resume devices took 0.215 seconds
[ 133.853171] OOM killer enabled.
[ 133.853172] Restarting tasks ... done.
[ 133.856056] random: crng reseeded on system resumption
[ 133.864597] PM: suspend exit
In my case it seems it’s fixed, I’ve forced the iommu mode to be pass-through in the boot parameters.
As you can see below the resume is almost instant as expected 
My grub config (excerpt):
GRUB_CMDLINE_LINUX="... iommu=pt"
[ 40.316075] PM: suspend entry (s2idle)
[ 42.908050] Filesystems sync: 2.591 seconds
[ 43.019148] Freezing user space processes
[ 43.020576] Freezing user space processes completed (elapsed 0.001 seconds)
[ 43.020585] OOM killer disabled.
[ 43.020590] Freezing remaining freezable tasks
[ 43.021537] Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
[ 43.021540] printk: Suspending console(s) (use no_console_suspend to debug)
[ 43.028946] atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug
[ 43.033806] queueing ieee80211 work while going to suspend
[ 43.294228] PM: suspend devices took 0.272 seconds
[ 43.294983] pcieport 0000:00:08.3: quirk: disabling D3cold for suspend
[ 43.295818] ACPI: EC: interrupt blocked
[ 52.135445] ACPI: EC: interrupt unblocked
[ 57.785214] [drm] PCIE GART of 512M enabled (table at 0x00000080FFD00000).
[ 57.785334] amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
[ 57.788505] nvme nvme0: D3 entry latency set to 10 seconds
[ 57.789190] amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
[ 57.791461] nvme nvme0: 16/0/0 default/read/poll queues
[ 57.980545] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[ 57.980820] amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
[ 57.981170] amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[ 57.981173] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 57.981175] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 57.981177] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[ 57.981179] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[ 57.981180] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[ 57.981182] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[ 57.981184] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[ 57.981186] amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[ 57.981188] amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[ 57.981190] amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
[ 57.981191] amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
[ 57.981193] amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
[ 57.985766] [drm] ring gfx_32792.1.1 was added
[ 57.986264] [drm] ring compute_32792.2.2 was added
[ 57.986749] [drm] ring sdma_32792.3.3 was added
[ 57.986802] [drm] ring gfx_32792.1.1 ib test pass
[ 57.986836] [drm] ring compute_32792.2.2 ib test pass
[ 57.986911] [drm] ring sdma_32792.3.3 ib test pass
[ 57.994858] PM: resume devices took 0.216 seconds
[ 57.995262] OOM killer enabled.
[ 57.995266] Restarting tasks ... done.
[ 57.998928] random: crng reseeded on system resumption
[ 58.005301] PM: suspend exit