Screen occasionally takes around 30 seconds to turn on after waking laptop from sleep

[broadways4640 (Max Fenti)]

Hi guys.

Sometimes, when I wake my laptop from sleep, the screen takes around 30 seconds to turn on.

I know that the laptop is not frozen because I can still unlock my profile with either my fingerprint or my password, all the while the screen is still off. I can also change my keyboard brightness during that time.

After around 30 seconds, the screen will turn on on its own, regardless of whether I unlocked my profile.

The issue only happens from time to time, specially after long period of sleeping it seems.

Could you recommend any fix, please?

Here is my current system info:

• Model: Lenovo ThinkPad P14s Gen 5 AMD
• Memory: 64.0 GiB
• Processor: AMD Ryzen™ 7 PRO 8840HS w/ Radeon™ 780M Graphics × 16
• Graphics: AMD Radeon™ 780M Graphics
• kernel version: Linux 7.2.7-200.fc44.x86_64
• Firmware version: R2LET42W (1.23 )
• Window System: Wayland
• OS: Fedora Linux 44 (Workstation Edition)

[barryascott]

Have a look at the system and user journals to see if there are clues as to why there is a delay.

After returning from sleep these show the logs in the last 10 minutes:

journalctl --since=-10min
journalctl --user --since=-10min

[sketch-exe (Shivank Sharma)]

[RESOLVED] Suspend does not work normally on ASUS FA507NV

Hi there, I wanted to follow up on this post as I have managed to resolve it myself, with further use of AI but mostly general research. The error here actually came from the iGPU, the last place I would assume to be broken. After running more diagnostic tests on my system, namely, pm-graph, the component that took the full 11 seconds to suspend was infact the iGPU. Investigating dmesg, I found out a constant stream of ERROR messages, both during boot and after suspend wake. Here’s the exact lo…

10-second s2idle suspend/resume delay possibly related to NVMe

I have a suspend/resume problem on a Lenovo Yoga 6 13ARE05 with an AMD Ryzen 4650U on Fedora 44 Workstation. My BIOS is updated. The laptop uses s2idle. I’m a newbie trying to fix this through a combination of searching online and asking LLMs, so forgive me if there’s anything weird about the troubleshooting done so far. I tested suspending and leaving it anywhere from 5–30 seconds and waking with the keyboard. In all cases, the keyboard responds immediately (Caps Lock flashes as on Windows), b…

So i guess there are few other reports of identical behaviour, consider checking them out but only after checking the logs as Barry said.

[et-ducky (Christopher Smith)]

Find the resume in the kernel log right after the next slow wake, before you reboot, and compare the timestamps between the resume and the display coming back.

journalctl -k -b -o short-precise --grep 'PM: suspend exit|amdgpu'

A gap of about 30 seconds after PM: suspend exit, or an amdgpu line with timeout or failed in it, puts the delay in the display driver rather than in GNOME.

I’d also test with Panel Self Refresh (PSR) turned off for a few days of normal sleep cycles. Add the kernel parameter and reboot.

sudo grubby --update-kernel=ALL --args="amdgpu.dcdebugmask=0x10"

If the delay doesn’t come back, keep the parameter. If it does, remove it with sudo grubby --update-kernel=ALL --remove-args="amdgpu.dcdebugmask=0x10".

Drafted with AI, reviewed by me.

[broadways4640 (Max Fenti)]

Hi. These are some of the logs from the command:

Oct 05 09:37:18 fedora kernel: Freezing user space processes
Oct 05 09:37:18 fedora kernel: Freezing user space processes completed (elapsed 0.003 seconds)
Oct 05 09:37:18 fedora kernel: OOM killer disabled.
Oct 05 09:37:18 fedora kernel: Freezing remaining freezable tasks
Oct 05 09:37:18 fedora systemd-resolved[720]: Clock change detected. Flushing caches.
Oct 05 09:37:18 fedora kernel: Freezing remaining freezable tasks completed (elapsed 0.002 seconds)
Oct 05 09:37:18 fedora systemd-logind[1146]: Lid opened.
Oct 05 09:37:18 fedora kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Oct 05 09:37:18 fedora kernel: PM: suspend devices took 0.443 seconds
Oct 05 09:37:18 fedora kernel: ACPI: EC: interrupt blocked
Oct 05 09:37:18 fedora kernel: ACPI: EC: interrupt unblocked
Oct 05 09:37:18 fedora kernel: ACPI: button: [Firmware Bug]: Unexpected lid state reported by firmware
Oct 05 09:37:18 fedora kernel: mhi mhi0: Requested to power ON
Oct 05 09:37:18 fedora kernel: mhi mhi0: Power on setup success
Oct 05 09:37:18 fedora sssd_kcm[820450]: Shutting down (status = 0)
Oct 05 09:37:18 fedora kernel: mhi mhi0: Wait for device to enter SBL or Mission mode
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: [drm] PCIE GART of 512M enabled (table at 0x00000080FFD00000).
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: SMU is resuming…
Oct 05 09:37:18 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd-kc>
Oct 05 09:37:18 fedora systemd[1]: sssd-kcm.service: Deactivated successfully.
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: SMU is resumed successfully!
Oct 05 09:37:18 fedora kernel: nvme nvme0: 16/0/0 default/read/poll queues
Oct 05 09:37:18 fedora kernel: ath11k_pci 0000:02:00.0: chip_id 0x12 chip_family 0xb board_id 0xff soc_id 0x400c1211
Oct 05 09:37:18 fedora kernel: ath11k_pci 0000:02:00.0: fw_version 0x11088c35 fw_build_timestamp 2024-04-17 08:34 fw_build_id WLAN.HSP.1.1->
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: ring sdma0 uses VM inv eng 12 on hub 0
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: ring jpeg_dec uses VM inv eng 1 on hub 8
Oct 05 09:37:18 fedora kernel: amdgpu 0000:c4:00.0: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Oct 05 09:37:18 fedora kernel: PM: resume devices took 0.433 seconds
Oct 05 09:37:18 fedora kernel: OOM killer enabled.
Oct 05 09:37:18 fedora kernel: Restarting tasks: Starting
Oct 05 09:37:18 fedora kernel: Restarting tasks: Done
Oct 05 09:37:18 fedora kernel: efivarfs: resyncing variable state
Oct 05 09:37:18 fedora kernel: efivarfs: finished resyncing variable state
Oct 05 09:37:18 fedora kernel: random: crng reseeded on system resumption
Oct 05 09:37:18 fedora systemd[1]: Starting fstrim.service - Discard unused blocks on filesystems from /etc/fstab…
Oct 05 09:37:18 fedora systemd[1]: Starting unbound-anchor.service - update of the root trust anchor for DNSSEC validation in unbound…
Oct 05 09:37:18 fedora systemd-sleep[829218]: System returned from sleep operation ‘suspend’.
Oct 05 09:37:18 fedora bluetoothd[1081]: Controller resume with wake event 0x0
Oct 05 09:37:18 fedora kernel: PM: suspend exit
Oct 05 09:37:18 fedora audit: BPF prog-id=448 op=LOAD
Oct 05 09:37:18 fedora systemd[1]: Starting logrotate.service - Rotate log files…
Oct 05 09:37:18 fedora audit: BPF prog-id=417 op=UNLOAD
Oct 05 09:37:18 fedora audit: BPF prog-id=416 op=UNLOAD
Oct 05 09:37:18 fedora audit: BPF prog-id=449 op=LOAD
Oct 05 09:37:18 fedora audit: BPF prog-id=450 op=LOAD
Oct 05 09:37:18 fedora audit: BPF prog-id=451 op=LOAD
Oct 05 09:37:18 fedora systemd[1]: Starting plocate-updatedb.service - Update the plocate database…
Oct 05 09:37:18 fedora proton.vpn.app.gtk.desktop[4343]: 2026-10-05T13:37:18.812473+00:00 | proton.vpn.session.session:279 | INFO | API:REQ>
Oct 05 09:37:18 fedora systemd[1]: user@1000.service: Unit now thawed.
Oct 05 09:37:18 fedora systemd[1]: session-2.scope: Unit now thawed.
Oct 05 09:37:18 fedora systemd[1]: user-1000.slice: Unit now thawed.
Oct 05 09:37:18 fedora systemd[1]: user.slice: Unit now thawed.
Oct 05 09:37:18 fedora systemd-sleep[829218]: Successfully thawed unit ‘user.slice’.
Oct 05 09:37:18 fedora systemd[1]: systemd-suspend.service: Deactivated successfully.
Oct 05 09:37:18 fedora systemd[1]: Finished systemd-suspend.service - System Suspend.
Oct 05 09:37:18 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=system>
Oct 05 09:37:18 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd>
Oct 05 09:37:18 fedora systemd[1]: Stopped target sleep.target - Sleep.
Oct 05 09:37:18 fedora systemd[1]: Reached target suspend.target - Suspend.
Oct 05 09:37:18 fedora systemd[1]: Stopped target suspend.target - Suspend.
Oct 05 09:37:18 fedora dnf5daemon-server[5939]: 2026-10-05T13:37:18+0000 [5939] DEBUG Loading plugin library file=“/usr/lib64/libdnf5/plugi>
Oct 05 09:37:18 fedora systemd-logind[1146]: Operation ‘suspend’ finished.
Oct 05 09:37:18 fedora ModemManager[1285]: [sleep-monitor-systemd] system is resuming
Oct 05 09:37:18 fedora systemd-resolved[720]: Closing all remaining TCP connections.
Oct 05 09:37:18 fedora systemd-resolved[720]: Resetting learnt feature levels on all servers.
Oct 05 09:37:18 fedora dnf5daemon-server[5939]: 2026-10-05T13:37:18+0000 [5939] INFO Loaded libdnf plugin “systemd-inhibit” (”/usr/lib64/li>
Oct 05 09:37:18 fedora dnf5daemon-server[5939]: 2026-10-05T13:37:18+0000 [5939] DEBUG Trying to load more plugins using the "systemd-inhibi>
Oct 05 09:37:18 fedora dnf5daemon-server[5939]: 2026-10-05T13:37:18+0000 [5939]

[sketch-exe (Shivank Sharma)]

Do the results differ when you are plugged in as compared to not plugged in to the charger?

[broadways4640 (Max Fenti)]

I ran the sudo grubby --update-kernel=ALL --args="amdgpu.dcdebugmask=0x10" command and the screen hasn’t had a delay since (I also downloaded some updates at around the same time too.). But I’ve noticed some occasional blinking when using the LibreWolf browser, and only that browser.

I remove the param for a couple of days and see it the screen goes back to delaying.If it does, then I’ll know that this is the fix.

[broadways4640 (Max Fenti)]

I am not sure, although I tried waking the laptop plugged and unplugged, I haven’t had screen delays since adding the param suggested by et-ducky.

[et-ducky (Christopher Smith)]

Does the blinking in LibreWolf stop during the days you have the parameter removed?

Drafted with AI, reviewed by me.

[broadways4640 (Max Fenti)]

The blinking did not happen prior to having the parameter. It started after adding the parameter. I just removed it and will test during the following days.

it does not happen often. But quite jarring when the only light source in my room is the laptop screen.

I noticed it also happens in Chrome.

[et-ducky (Christopher Smith)]

When it blinks in LibreWolf or Chrome, does the whole screen flash or only the browser window?

Drafted with AI, reviewed by me.

[broadways4640 (Max Fenti)]

Only the browser window, as far as I can tell