1. Please describe the problem:

After the screen lock activates (via KDE kscreenlocker), the laptop's built-in display (eDP-1) goes completely black and cannot be recovered. Mouse movement, keyboard input, and password entry do not restore the display. A hard reboot is required. The external monitor (DP-4) is unaffected.

The kernel log shows the following errors immediately before the display becomes unrecoverable:

    i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
    i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] commit wait timed out
    i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:506:eDP-1] commit wait timed out
    i915 0000:00:02.0: [drm] *ERROR* [PLANE:33:plane 1A] commit wait timed out

Hardware: Intel Meteor Lake-P [Intel Arc Graphics] [8086:7d55] (display controller), NVIDIA GeForce RTX 4060 Laptop GPU (discrete, unused for display). Session: KDE Plasma on Wayland, SDDM

2. What is the Version-Release number of the kernel:

7.0.4-100.fc43.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

Yes. The issue first appeared with kernel 7.0.4-100.fc43.x86_64. The previous kernel, 6.19.12-200.fc43.x86_64, did not exhibit this problem.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

1. Boot kernel 7.0.4-100.fc43.x86_64
2. Log in to a KDE Plasma Wayland session via SDDM
3. Leave the system idle until the screen lock activates (or trigger it manually via the lock screen shortcut)
4. The laptop display (eDP-1) goes black and does not recover on any input.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Not yet tested

6. Are you running any modules that not shipped with directly Fedora's kernel?:

kmod-nvidia-580.159.03-1.fc43.x86_64

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Attached

Reproducible: Always