Bug: 570.124.04 - freeze on monitor wakeup - "Flip event timeout"

Graphics / Linux Linux
1

Started right after I upgraded to 570.124.04.

Was not present in 570.86.16.

To replicate -

  1. Lock the system with two monitors. Wait until monitors are switched off.
  2. Press any key.
  3. Symptoms: Primary monitor wakes up but system is frozen. The other monitor does not wake up.

I tried Ctrl+Alt+F1 to reboot, unfortunately that did not work either; it froze the system completely (Capslock no longer lit up on keyboard).

System configuration -

GPU: RTX 3090
Monitors: Two
Operating System: Arch Linux
Desktop Environment: KDE (Wayland)
Display Manager: ly (text-based, instead of SDDM)

Journal excerpt -

repeat of this many times -
Mar 02 12:42:05 workstation kwin_wayland[1190]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
Mar 02 12:42:05 workstation kwin_wayland[1190]: kwin_wayland_drm: Please report this at Linux - NVIDIA Developer Forums
Mar 02 12:42:05 workstation kwin_wayland[1190]: kwin_wayland_drm: With the output of ā€˜sudo dmesgā€™ and ā€˜journalctl --user-unit plasma-kwin_wayland --boot 0ā€™
Mar 02 12:42:06 workstation kwin_wayland[1190]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
Mar 02 12:42:06 workstation kwin_wayland[1190]: kwin_wayland_drm: Please report this at Linux - NVIDIA Developer Forums
Mar 02 12:42:06 workstation kwin_wayland[1190]: kwin_wayland_drm: With the output of ā€˜sudo dmesgā€™ and ā€˜journalctl --user-unit plasma-kwin_wayland --boot 0ā€™
Mar 02 12:42:06 workstation kwin_wayland[1190]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
Mar 02 12:42:06 workstation kwin_wayland[1190]: kwin_wayland_drm: Please report this at Linux - NVIDIA Developer Forums
Mar 02 12:42:06 workstation kwin_wayland[1190]: kwin_wayland_drm: With the output of ā€˜sudo dmesgā€™ and ā€˜journalctl --user-unit plasma-kwin_wayland --boot 0ā€™

interspersed sometimes with kernel: [drm:nv_drm_atomic_comit [nvidia_drm]] ERROR -
Mar 02 12:42:35 workstation kwin_wayland[1190]: kwin_wayland_drm: With the output of ā€˜sudo dmesgā€™ and ā€˜journalctl --user-unit plasma-kwin_wayland --boot 0ā€™
Mar 02 12:42:36 workstation kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Mar 02 12:42:36 workstation kwin_wayland[1190]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
Mar 02 12:42:36 workstation kwin_wayland[1190]: kwin_wayland_drm: Please report this at Linux - NVIDIA Developer Forums

7 Likes
2

Having the same problem. Iā€™ve submitted a bug report to NVIDIA. Iā€™m also getting: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress

Running 6.13.5-arch1-1 with 570.124.04-2 and when I turn off my monitor and turn it back on the screen is black and my second monitor that I didnā€™t turn off is frozen and the system completely freezes.

nvidia-bug-report.log (2.5 MB)

1 Like
3

I have the same issue when returning back from stand-by. It started happening on 570.124.04, but it was not an issue on 570.86.16.

Hereā€™s my journalctl dump:

kwin_wayland[1353]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
kwin_wayland[1353]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
kwin_wayland[1353]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
kwin_wayland[1353]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Framebuffer name must be generated before being bound.
kwin_wayland[1353]: kwin_scene_opengl: 0x506: GL_INVALID_FRAMEBUFFER_OPERATION error generated. Operation is not valid because a bound framebuffer is not framebuffer complete.
kwin_wayland[1353]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
kwin_wayland[1353]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
kwin_wayland[1353]: kwin_wayland_drm: Please report this at https://forums.developer.nvidia.com/c/gpu-graphics/linux
kwin_wayland[1353]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
kwin_wayland[1353]: kwin_wayland_drm: The main thread was hanging temporarily!
4

Workaround

It seems like the bug occurs only when two monitors are active.

Given that, here is my very hacky workaround without having to downgrade, until this is fixed.

I created this script to switch to one monitor on screen lock, and reset to my original config on unlock.

#!/bin/bash
# one_monitor_on_screenlock.sh

set -uexo pipefail

dbus-monitor --session "type='signal',interface='org.freedesktop.ScreenSaver',member='ActiveChanged'" | \
while read line; do
    if echo "$line" | grep -q "boolean true"; then
        kscreen-doctor output.DP-1.enable output.DP-4.disable
    elif echo "$line" | grep -q "boolean false"; then
        kscreen-doctor output.DP-4.enable output.DP-4.position.2560,0 output.DP-4.priority.1 output.DP-1.enable
    fi
done

Then I added it as a Login Script in KDE Settings ā†’ Autostart.

5

I have the exact same issue (Arch 6.13.5, Hyprland), except I have a single monitor (AW3821DW) and the moment it goes into DPMS ON (from the lock screen) I canā€™t have it turn on again. Requires a full reboot.

I get the following in the journal:

[drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000a00] Flip event timeout on head 0

Iā€™ve reverted to 570.86.16 which is working properly.

6

I see this issue too, started with 570.124.04, did not happen with previous 570.86.16.
Iā€™m on Gentoo with Linux 6.13.5-gentoo-dist and I have two monitors, 1 TFT connected via Displayport and a TV connected via HDMI. After I turn off all the screens, it seems everything is frozen and I canā€™t get any of the screens to turn on again. I can however ssh into the system and issue a soft reboot, so it is not actually frozen

7

I am also experiencing this but with three monitors.

[drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 2
[drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -22

kwin_wayland_drm: atomic commit failed: Device or resource busy

kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
kwin_wayland_drm: Please report this at https://forums.developer.nvidia.com/c/gpu-graphics/linux
kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
8

There is a new version, 570.124.06, in the cuda repository and I donā€™t have this issue on that version.

Iā€™m sorry this isnā€™t true. Happened after the third time my monitors woke up. Although I did get this log event instead:

kwin_wayland_drm: No drm events for gpu "/dev/dri/card0" within last 1 second
9

Confirming. Same issue on latest Arch, with same logs on desktop with RTX4070 and one external monitor via DisplayPort.

mar 04 11:47:01 onyx kwin_wayland[751]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
mar 04 11:47:01 onyx kwin_wayland[751]: kwin_wayland_drm: Please report this at https://forums.developer.nvidia.com/c/gpu-graphics/linux
mar 04 11:47:01 onyx kwin_wayland[751]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
mar 04 11:47:02 onyx kwin_wayland[751]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
mar 04 11:47:02 onyx kwin_wayland[751]: kwin_wayland_drm: Please report this at https://forums.developer.nvidia.com/c/gpu-graphics/linux
mar 04 11:47:02 onyx kwin_wayland[751]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
mar 04 11:47:03 onyx kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
mar 04 11:47:03 onyx kwin_wayland[751]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
mar 04 11:47:03 onyx kwin_wayland[751]: kwin_wayland_drm: Please report this at https://forums.developer.nvidia.com/c/gpu-graphics/linux
mar 04 11:47:03 onyx kwin_wayland[751]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
mar 04 11:47:04 onyx kwin_wayland[751]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
mar 04 11:47:04 onyx kwin_wayland[751]: kwin_wayland_drm: Please report this at https://forums.developer.nvidia.com/c/gpu-graphics/linux
mar 04 11:47:04 onyx kwin_wayland[751]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
mar 04 11:47:05 onyx kwin_wayland[751]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
mar 04 11:47:05 onyx kwin_wayland[751]: kwin_wayland_drm: Please report this at https://forums.developer.nvidia.com/c/gpu-graphics/linux
mar 04 11:47:05 onyx kwin_wayland[751]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
mar 04 11:47:06 onyx kwin_wayland[751]: kwin_wayland_drm: Pageflip arrived after all, 43546ms after the commit
mar 04 11:47:06 onyx kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
mar 04 11:47:06 onyx kwin_wayland[751]: kwin_wayland_drm: atomic commit failed: Permission denied
mar 04 11:47:09 onyx kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
mar 04 11:47:12 onyx kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
10

Same here, with two screens, Wayland on EndeavourOS with latest driver 570.124.04 on nvidia-open.

11

Same here, with one screen, Wayland (Gnome and KDE) on Nobara41 with latest nvidia-open and closed.
Only a Downgrade to 570.86.16 Helped.

13

Same monitor (i have only 1 monitor) with a 4070 super and using Bazzite that come with 570.124.04 driver and the system freeze when resuming from sleep :

drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -22
drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0

nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67e:6 2:0:2824:2816
Mar 03 20:34:38 bazzite kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67e:6 2:0:2824:2816

570.86.16 is fine.

14

Hi all,

The Pageflip timed out! issue is being tracked on NVIDIA Bug # 5158370.
The nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress issue is being tracked on NVIDIA Bug # 5141371 (bananenā€™s report).

They may have the same root cause but are being tracked separately for now.

Thank you

2 Likes
15

Thank you very much! I could not find a link to #5158370, is it in an internal tracker?

Please let me know if you need any inputs, e.g. for replicating the issue.

Some more details from me -

Software: KDE, Arch Linux
GPU: RTX 3090
Monitors: Two 1440p monitors connected directly to the GPU via the two Displayport connectors.

How to replicate:

  1. To make it quicker to replicate, set Display & Brightness ā†’ Turn of Screen ā†’ ā€œWhen Locked: Immediatelyā€.
  2. Lock screen with Win+L. Your monitors will turn off, while the CPU should still be active.
  3. Wake up the monitors by moving the mouse or pressing a key.
  4. If the issue occurs, youā€™ll notice one of the monitors does not wake up and the other freezes.

Frequency of the issue: Happens with a very high probability, perhaps every time.

16

Similar here and have had to revert back to 570.86.16

System Config:
Arch Linux
4 monitors (all at 60 Mhz, Iā€™m a dba/dev, not a gamer)
XORG
GPU: GeForce RTX 4060 Ti (8 GB RAM).
CPU: AMD Ryzen 5 3600
Window Manager: i3

It does not matter whether GSP is enabled or disabled.

On resuming from suspend:

  • two monitors (out of four) do not come back. The ones that do not come back are numbers 1 and 2 in the ordering sequence.
  • any graphics slows to a crawl - e.g. mouse may move jerkily 4 pixels every 3 seconds.
  • keyboard still works but it may take a couple of minutes to get the system to recognize that I want focus at monitor 3
  • I can ssh in with no problem - However, attempts to shutdown and restart get blocked by the following error message: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c77d:0 2:0:348:336
  • The other error that is seen is:
    nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000c67e:6:0:1230
2 Likes
17

Yes. This is an internal bug. I will post updates from our investigation when available. Thanks

1 Like
18

Iā€™m having a similar, although possibly different, bug. The monitor will freeze, but the system otherwise continues to work. Music keeps playing, USB devices can still control audio, and if Iā€™m on call with people they can still hear me + see my camera if it was on. I get the same error message from journalctl though, and the symptoms seem similar.

System config:
Fedora 42
1 monitor (AW34DWF)
Wayland
GPU: 4090
CPU: Ryzen 9 5950x
KDE

For me, the bug occurs somewhat randomly, although it maybe is related to browsers/electron apps. It works fine almost all the time, but occasionally it freezes during them. That being said, most of what I do on my computer is in browsers or electron apps, so might not be a real pattern.

Hereā€™s the output from journalctl --user-unit plasma-kwin_wayland --boot -1

Mar 15 22:29:50 fedora kwin_wayland[5693]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x559233542230)
Mar 15 22:29:50 fedora kwin_wayland[5693]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x559233542230)
Mar 15 22:31:48 fedora kwin_wayland[5693]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x559233542230)
Mar 15 22:31:49 fedora kwin_wayland[5693]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x559233542230)
Mar 15 22:31:50 fedora kwin_wayland[5693]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x559233542230)
Mar 15 22:31:51 fedora kwin_wayland[5693]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x559233542230)
Mar 15 22:31:52 fedora kwin_wayland[5693]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x559233542230)
Mar 15 22:31:53 fedora kwin_wayland[5693]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x559233542230)
Mar 15 22:31:54 fedora kwin_wayland[5693]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x559233542230)
Mar 15 23:26:13 fedora kwin_wayland[5693]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
Mar 15 23:26:13 fedora kwin_wayland[5693]: kwin_wayland_drm: Please report this at Linux - NVIDIA Developer Forums
Mar 15 23:26:13 fedora kwin_wayland[5693]: kwin_wayland_drm: With the output of ā€˜sudo dmesgā€™ and ā€˜journalctl --user-unit plasma-kwin_wayland --boot 0ā€™
Mar 15 23:26:14 fedora kwin_wayland[5693]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver

19

I have pretty much the same issue as @maxwellalt123. It occurs most frequently, if not always, when a Chromium/Electron-based application is running and seems to be related to GPU acceleration during video decoding when two monitors are connected. Recently, it happened while watching YouTube on a Chromium browser with the new 570.124.04 drivers. It occurred precisely when I was adjusting the brightness of monitor #1. The image froze on monitor #1, but monitor #2 continued to function perfectly. Restarting plasmashell does nothing, and the only thing that helps (though not always) is either restarting the entire sddm or opening a separate tty window using Ctrl + F3 and starting a new graphical session.

System config:
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.6-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 Ɨ AMD Ryzen 7 2700X Eight-Core Processor
Memory: 23.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Ti
Manufacturer: Micro-Star International Co., Ltd
Product Name: MS-7B86
System Version: 7.0

This happens regardless of the kernel version and whether GSP or nvidia-drm.modeset=1 is enabled.
It always occurs on my primary monitor connected via DisplayPort.

Main Display Specs:
Acer Technologies XV242Y
165Hz 1080p DP
HDR: Disabled
Freesync: Disabled

Second Display Specs:
Acer Technologies VG220Q
75Hz HDMI

journalctl --user-unit plasma-kwin_wayland --boot 0

mar 16 23:57:25 fedora kwin_wayland[4653]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
mar 16 23:57:25 fedora kwin_wayland[4653]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
mar 16 23:57:25 fedora kwin_wayland[4653]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
mar 16 23:57:25 fedora kwin_wayland[4653]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
mar 17 00:01:01 fedora kwin_wayland[4653]: kwin_xwl: Could not create a source from 0x5594d2e2d0b0 0
mar 17 00:01:01 fedora kwin_wayland[4653]: kwin_xwl: Could not create a source from 0x5594d3d2be20 0
mar 17 00:01:09 fedora kwin_wayland[4653]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
mar 17 00:01:11 fedora kwin_wayland[4653]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
mar 17 00:01:11 fedora kwin_wayland[4653]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
mar 17 00:01:11 fedora kwin_wayland[4653]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
mar 17 00:02:59 fedora kwin_wayland[4653]: kwin_core: XCB error: 3 (BadWindow), sequence: 27741, resource id: 20971715, major code: 129 (SHAPE), minor code: 6 (Input)
mar 17 00:05:55 fedora kwin_wayland[4653]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
mar 17 00:15:57 fedora kwin_wayland[4653]: kwin_core: XCB error: 3 (BadWindow), sequence: 29549, resource id: 20971722, major code: 129 (SHAPE), minor code: 6 (Input)
mar 17 00:25:46 fedora kwin_wayland[4653]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
mar 17 00:44:08 fedora kwin_wayland[4653]: kwin_core: XCB error: 3 (BadWindow), sequence: 38921, resource id: 20971787, major code: 129 (SHAPE), minor code: 6 (Input)
mar 17 00:46:13 fedora kwin_wayland[4653]: kwin_core: XCB error: 3 (BadWindow), sequence: 39034, resource id: 20971790, major code: 129 (SHAPE), minor code: 6 (Input)
mar 17 00:47:19 fedora kwin_wayland[4653]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
mar 17 00:47:19 fedora kwin_wayland[4653]: kwin_wayland_drm: Please report this at https://forums.developer.nvidia.com/c/gpu-graphics/linux
mar 17 00:47:19 fedora kwin_wayland[4653]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
20

Now I that you mention it, my display is display port as well. There might be a pattern there.

21

Iā€™m seeing the same issue with a display port.
RTX 3060 on Linux 6.13.7-arch1-1 nvidia driver 570.124.04-4