[545.29.06-18.1]Flip event timeout error on startup, shutdown and sometimes suspend. Wayland unusable

shelter · 2024-03-01T09:07:42.067Z

@aplattner You might be onto something here, I moved ddcutil temporarily and rebooted/shutdown a few times without any issues.

aplattner · 2024-03-01T22:25:39.320Z

Thanks for confirming. I have a patch that should fix the problem that I’m getting reviewed now.

aplattner · 2024-03-03T02:22:48.617Z

If you want to give it a try, please restore ddcutil and then try this patch:

bash NVIDIA-Linux-x86_64-550.54.14.run --apply-patch nvidia-drm-take-modeset-ownership-earlier.patch
sudo bash NVIDIA-Linux-x86_64-550.54.14-custom.run

nvidia-drm-take-modeset-ownership-earlier.patch (2.8 KB)

shelter · 2024-03-03T07:18:51.293Z

It sort of works, it still happens but it didn’t keep on “looping” and bringing the entire system to a crawl however there was a minor delay still. There was only 2 flip event messages this time.
UPDATE: It seems to change a bit from time to time, I got 4 flip event timeouts during another boot.

[sön mar  3 08:13:29 2024] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
[sön mar  3 08:13:32 2024] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 1

aplattner · 2024-03-03T08:18:27.263Z

Did you get any flip failure messages, or just the flip event timeouts?

shelter · 2024-03-03T14:39:15.727Z

Just messages like the ones above, causing the boot to be a bit slow.

ptr1337 · 2024-03-03T16:20:39.718Z

Im not sure, if this patch fixed the issue many people facing here, since I dont have it on the 4070 super. Might come from the modules having in the initramfs included.

But ddcutil is still segfaulting for me:

dmesg:

[ 5.930498] ddcutil[618]: segfault at 0 ip 0000760ee139891c sp 00007ffc06dbd788 error 4 in libc.so.6[760ee1224000+18a000] likely on CPU 9 (core 9, socket 0)

journalctl:

Mär 03 17:15:36 cachyos-x8664 (udev-worker)[614]: hiddev3: Process '/usr/bin/ddcutil chkusbmon /dev/usb/hiddev3 -v' terminated by signal SEGV.
Mär 03 17:15:36 cachyos-x8664 (udev-worker)[614]: hiddev3: Failed to wait for spawned command '/usr/bin/ddcutil chkusbmon /dev/usb/hiddev3 -v': Input/output error

Edit:
but backlight is working without issues, maybe different issue

nvidia-bug-report.log.gz (3.2 MB)

shelter · 2024-03-03T16:42:21.138Z

Weird, you and I run basically the same stuff, except you have a 4070 Super and an AMD (?) CPU I have a regular 4070 and an Intel CPU. I also don’t currently have the modules loaded in initramfs because I needed to test if the flip event disappeared.
I ran:

journalctl |  grep ddcutil

No segfault, nothing in dmesg either.

shelter · 2024-03-06T07:28:47.856Z

It’s still causing havoc :(

[    6.177374] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
[    6.177558] Console: switching to colour dummy device 80x25
[    6.177577] nvidia 0000:01:00.0: vgaarb: deactivate vga console
[    6.507599] videodev: Linux video capture interface: v2.00
[    6.521081] usb 1-11.4: Found UVC 1.00 device <unnamed> (046d:0823)
[    6.558901] usbcore: registered new interface driver uvcvideo
[    6.879032] fbcon: nvidia-drmdrmfb (fb0) is primary device
[    6.946812] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -22
[    6.946840] Console: switching to colour frame buffer device 240x67
[    6.948642] nvidia 0000:01:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device
[    7.181478] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -22
[    9.405274] e1000e 0000:00:1f.6 eno2: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
[    9.605961] userif-2: sent link up event.
[    9.816456] userif-2: sent link up event.
[   10.034338] userif-2: sent link up event.
[   10.241545] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
[   13.249527] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 1
[   13.249756] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -22
[   16.257533] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
[   19.265532] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 1
[   19.265790] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -22

UrbenLegend · 2024-03-08T21:24:51.402Z

Interestingly enough, KDE 6 Wayland now works without fbdev=1. If I use fbdev=1, it will still exhibit the flip event timeout errors though.

user99468 · 2024-03-14T01:19:06.263Z

I’m encountering the same flip timeout errors using hyprland (and previously on sway) with an RTX 3080. I’ve been engaging in a hyprland thread here:

github.com/hyprwm/Hyprland

Swaylock crashes after wakeup

opened 01:39PM - 12 Dec 23 UTC

diniamo

bug

### Hyprland Version Hyprland, built from branch main at commit 8f38487884228…22c2cb36c57b4f3929eec1cc42c dirty (xwayland: don't change workspace on configure for invisible windows). Tag: v0.33.1-31-g8f384878 flags: (if any) debug ### Bug or Regression? Bug ### Description Seems to be similar to #1519, except I'm not on a laptop. This is not completely consistent, but it happens more often than not: annoying: sometimes, after my pc wakes up, swaylock crashes and becomes completely unresponsive. If I try to kill it from another tty, I get a red screen instead of Hyprland. I use https://aur.archlinux.org/packages/swaylock-effects-git / https://github.com/jirutka/swaylock-effects. ### How to reproduce 1. Call swaylock before sleep (I use swayidle) 2. Wake up the computer 3. Try to login ### Crash reports, logs, images, videos Not sure where I'm supposed to find logs for this

The interesting thing from the logs that I’ve seen is that according to libdrm, the ATOMIC_NONBLOCK flag is set, and looking at the open source driver (which I’m not using, but I don’t have access to the closed source driver’s source code), the “Flip event timeout” message should only be reported if ATOMIC_NONBLOCK is NOT set. Nothing in the code I traced through in wlroots, libdrm, the kernel drm, or the open source driver would explain this flag being wrong

ptr1337 · 2024-03-15T07:24:43.147Z

Hi @aplattner ,

We on CachyOS recently released a new ISO, which defaults now to Plasma Wayland.
Some users expierencing issues, (mainly on 40xx cards) that the graphical session is not correctly loaded.

We are using fbdev=1 and drm.modeset, we can confirm that this issue is fixed when patching the nvidia module with this above patch.
Please consider to pull this into the next (beta) release.

Thanks!

UrbenLegend · 2024-03-25T01:02:28.518Z

ptr1337:

On CachyOS we noticed that several user facing this issue, when fbdev=1 is used and mkinitcpio does not include the NVIDIA Modules as default.

I added nvidia nvidia_modeset nvidia_uvm nvidia_drm to the MODULES line in mkinitcpio.conf on my Arch machine and now fbdev option works! It no longer just freezes on the boot console and now shows a high resolution TTY.

Why is this necessary for fbdev though?

EDIT: I also had to move modeset=1 and fbdev=1 out of my modprobe.d and into the bootloader config as nvidia_drm.modeset=1 and nvidia_drm.fbdev=1, otherwise fbdev would not take into effect.

ptr1337 · 2024-03-25T17:19:21.860Z

It seems that something else takes the ownership before fbdev/modeset itself somehow.

I wonder why this didnt got into 550.67.

@aplattner
Is it planned to provide this in a future release?
Fedora is also using fbdev=1 as default and as soon this is solved, I would also bring it on archlinux as default forward.

gulafaran · 2024-03-29T12:28:11.548Z

im not entirerly sure if im hitting the same issue but i tried both fbdev=1 and 0, setting it on bootloader and only in modprobed.d/nv.conf , ive also tried applying nvidia-drm-take-modeset-ownership-earlier.patch ontop of 550.67 but if i have hdmi plugged in while booting and plasma tries to start it freezes and drops this in dmesg

mar 29 13:19:33 tom-legion kernel: BUG: unable to handle page fault for address: ffffb50f81f97d88
mar 29 13:19:33 tom-legion kernel: #PF: supervisor read access in kernel mode
mar 29 13:19:33 tom-legion kernel: #PF: error_code(0x0000) - not-present page
mar 29 13:19:33 tom-legion kernel: PGD 100000067 P4D 100000067 PUD 10026e067 PMD 10620d067 PTE 0
mar 29 13:19:33 tom-legion kernel: Oops: 0000 [#2] PREEMPT SMP
mar 29 13:19:33 tom-legion kernel: CPU: 2 PID: 1066 Comm: systemd-logind Tainted: P S   UD    O       6.8.2-gentoo-tom #1
mar 29 13:19:33 tom-legion kernel: Hardware name: LENOVO 82WQ/LNVNB161216, BIOS KWCN42WW 09/15/2023
mar 29 13:19:33 tom-legion kernel: RIP: 0010:_nv035940rm+0x1ac/0x480 [nvidia]
mar 29 13:19:33 tom-legion kernel: Code: 48 63 47 08 48 01 c2 48 8b 07 48 85 c0 75 1b e9 2b 02 00 00 66 2e 0f 1f 84 00 00 00 00 00 48 8b 48 10 48 85 c9 74 17 48 89 c8 <48> 39 30 77 ef 0f 83 f9 01 00 00 48 8b 48 18 48 85 c9 75 e9 48 89
mar 29 13:19:33 tom-legion kernel: RSP: 0018:ffffb50f81e674c8 EFLAGS: 00010086
mar 29 13:19:33 tom-legion kernel: RAX: ffffb50f81f97d88 RBX: ffffffffc11c4e6b RCX: 0000000225c17d03
mar 29 13:19:33 tom-legion kernel: RDX: ffff9fbee20d5f20 RSI: 000000000000042a RDI: ffffffffc1eae5b8
mar 29 13:19:33 tom-legion kernel: RBP: ffff9fbee20d5eb0 R08: 0000000000000000 R09: ffff9fbee20d5f48
mar 29 13:19:33 tom-legion kernel: R10: 00000000c1d00001 R11: ffffb50f81675008 R12: ffff9fbee20d5ed0
mar 29 13:19:33 tom-legion kernel: R13: 00000000c3720101 R14: ffff9fbeccbf9008 R15: 00000000c1d00001
mar 29 13:19:33 tom-legion kernel: FS:  00007ffff76ea8c0(0000) GS:ffff9fd60d480000(0000) knlGS:0000000000000000
mar 29 13:19:33 tom-legion kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
mar 29 13:19:33 tom-legion kernel: CR2: ffffb50f81f97d88 CR3: 0000000111901000 CR4: 0000000000750ef0
mar 29 13:19:33 tom-legion kernel: PKRU: 55555554
mar 29 13:19:33 tom-legion kernel: Call Trace:
mar 29 13:19:33 tom-legion kernel:  <TASK>
mar 29 13:19:33 tom-legion kernel:  ? __die+0x1f/0x60
mar 29 13:19:33 tom-legion kernel:  ? page_fault_oops+0x161/0x4b0
mar 29 13:19:33 tom-legion kernel:  ? fixup_exception+0x22/0x270
mar 29 13:19:33 tom-legion kernel:  ? exc_page_fault+0x42f/0x780
mar 29 13:19:33 tom-legion kernel:  ? asm_exc_page_fault+0x22/0x30
mar 29 13:19:33 tom-legion kernel:  ? _nv045234rm+0x4b/0x1a0 [nvidia]
mar 29 13:19:33 tom-legion kernel:  ? _nv035940rm+0x1ac/0x480 [nvidia]
mar 29 13:19:33 tom-legion kernel:  ? _nv045234rm+0x4b/0x1a0 [nvidia]
mar 29 13:19:33 tom-legion kernel:  ? _nv049667rm+0xd6/0x1d0 [nvidia]
mar 29 13:19:33 tom-legion kernel:  ? _nv045234rm+0x4b/0x1a0 [nvidia]
mar 29 13:19:33 tom-legion kernel:  ? _nv023020rm+0x1e16/0x22e0 [nvidia]
mar 29 13:19:33 tom-legion kernel:  ? _nv000582rm+0x5e/0x70 [nvidia]
mar 29 13:19:33 tom-legion kernel:  ? rm_kernel_rmapi_op+0x127/0x220 [nvidia]
mar 29 13:19:33 tom-legion kernel:  ? nvkms_call_rm+0x2f/0x40 [nvidia_modeset]
mar 29 13:19:33 tom-legion kernel:  ? _nv002792kms+0x42/0x50 [nvidia_modeset]
mar 29 13:19:33 tom-legion kernel:  ? _nv002479kms+0xf0/0x850 [nvidia_modeset]
mar 29 13:19:33 tom-legion kernel:  ? psi_task_change+0x81/0xa0
mar 29 13:19:33 tom-legion kernel:  ? _nv002892kms+0x119/0x270 [nvidia_modeset]
mar 29 13:19:33 tom-legion kernel:  ? _nv002893kms+0x59/0x160 [nvidia_modeset]
mar 29 13:19:33 tom-legion kernel:  ? _nv002852kms+0x19c5/0x4a40 [nvidia_modeset]
mar 29 13:19:33 tom-legion kernel:  ? nv_kthread_q_stop+0x1340/0x4ae0 [nvidia_modeset]
mar 29 13:19:33 tom-legion kernel:  ? nvKmsIoctl+0xf9/0x270 [nvidia_modeset]
mar 29 13:19:33 tom-legion kernel:  ? nvkms_ioctl_from_kapi+0x70/0xd0 [nvidia_modeset]
mar 29 13:19:33 tom-legion kernel:  ? _nv002234kms+0x1cce/0x3310 [nvidia_modeset]
mar 29 13:19:33 tom-legion kernel:  ? nv_drm_internal_framebuffer_create+0x840/0x8f0 [nvidia_drm]
mar 29 13:19:33 tom-legion kernel:  ? drm_atomic_add_encoder_bridges+0x45/0xa0
mar 29 13:19:33 tom-legion kernel:  ? drm_mode_to_nvkms_display_mode+0x12/0x1740 [nvidia_drm]
mar 29 13:19:33 tom-legion kernel:  ? drm_atomic_check_only+0x5b6/0xa20
mar 29 13:19:33 tom-legion kernel:  ? drm_atomic_commit+0x46/0xa0
mar 29 13:19:33 tom-legion kernel:  ? __drm_printfn_seq_file+0x20/0x20
mar 29 13:19:33 tom-legion kernel:  ? nv_drm_atomic_helper_disable_all+0x1ec/0x4b0 [nvidia_drm]
mar 29 13:19:33 tom-legion kernel:  ? nv_drm_exit+0x1204/0x17e0 [nvidia_drm]
mar 29 13:19:33 tom-legion kernel:  ? drm_dropmaster_ioctl+0xad/0x130
mar 29 13:19:33 tom-legion kernel:  ? drm_setmaster_ioctl+0x160/0x160
mar 29 13:19:33 tom-legion kernel:  ? drm_ioctl_kernel+0x86/0xe0
mar 29 13:19:33 tom-legion kernel:  ? drm_ioctl+0x231/0x460
mar 29 13:19:33 tom-legion kernel:  ? drm_setmaster_ioctl+0x160/0x160
mar 29 13:19:33 tom-legion kernel:  ? __x64_sys_ioctl+0x8a/0xb0
mar 29 13:19:33 tom-legion kernel:  ? do_syscall_64+0x80/0x190
mar 29 13:19:33 tom-legion kernel:  ? do_syscall_64+0x8c/0x190
mar 29 13:19:33 tom-legion kernel:  ? syscall_exit_to_user_mode+0x73/0x180
mar 29 13:19:33 tom-legion kernel:  ? do_syscall_64+0x8c/0x190
mar 29 13:19:33 tom-legion kernel:  ? do_syscall_64+0x8c/0x190
mar 29 13:19:33 tom-legion kernel:  ? entry_SYSCALL_64_after_hwframe+0x46/0x4e
mar 29 13:19:33 tom-legion kernel:  </TASK>

it works however if i leave hdmi unplugged until plasma is up and then plug it in.

ales.astone · 2024-07-02T13:19:59.484Z

I can still reproduce all the time in Ubuntu 24.04 with nvidia 550.90.07 from the ubuntu package and fbdev=1.
initcall_blacklist=simpledrm_platform_driver_init makes no difference.

What seems to fix it here is delaying the startup of gdm with

Wants=systemd-udev-settle.service
After=systemd-udev-settle.service

Instead i never hit this issue in Fedora, presumably because the boot sequence takes longer on my install…?

leigh123linux · 2024-07-02T14:26:15.785Z

Try using these cmdline options instead

nvidia-drm.modeset=1 nvidia-drm.fbdev=1

ales.astone · 2024-07-02T14:46:09.356Z

Sorry, I did not specify because all the previous messages were about fbdev, but yes my issue is triggered by nvidia-drm.fbdev=1 and goes away when delaying gdm.

ales.astone · 2024-07-15T13:43:07.892Z

Further investigation shows that this bug with fbdev=1 is triggered in ubuntu by gpu-manager.service, which early in the boot (before display-manager.service) opens /dev/dri/card1 and that triggers this bug.

After the bug is triggered you will see close(open("/dev/dri/card1")) hanging for few seconds.

Making sure that we only open /dev/dri/card1 after udev rules for nvidia-drm have fully loaded works around that.

@aplattner i hope that helps debugging what’s wrong on the driver side. I’m running the driver version 550.90.07

armync · 2024-07-18T08:32:28.590Z

On my end, it happens too with [drm:nv_drm_atomic_commit [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset. Error code: -22. because of adding parameter nvidia-drm.modeset=1 to the boot loader (I have systemd-boot).

Tried with nvidia-drm.fbdev 0/1 (no difference). ddcutil isn’t enabled on my system.

OS: openSUSE Tumbleweed
Kernel: 6.9.9-1-default

Jul 18 10:40:18 localhost systemd[1]: Started nvidia-powerd service.
Jul 18 10:40:18 localhost /usr/bin/nvidia-powerd[1194]: nvidia-powerd version:1.0(build 1)
Jul 18 10:40:19 localhost.localdomain kernel: nvidia: loading out-of-tree module taints kernel.
Jul 18 10:40:19 localhost.localdomain kernel: nvidia: module license 'NVIDIA' taints kernel.
Jul 18 10:40:19 localhost.localdomain kernel: nvidia: module license taints kernel.
Jul 18 10:40:19 localhost.localdomain kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 235
Jul 18 10:40:19 localhost.localdomain kernel: nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
Jul 18 10:40:19 localhost.localdomain kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
Jul 18 10:40:19 localhost.localdomain kernel: nvidia-uvm: Loaded the UVM driver, major device number 511.
Jul 18 10:40:20 localhost.localdomain kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  550.90.07  Fri May 31 09:30:47 UTC 2024
Jul 18 10:40:20 localhost.localdomain kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Jul 18 10:40:20 localhost.localdomain systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:nvidia_0...
Jul 18 10:40:20 localhost.localdomain kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 1
Jul 18 10:40:20 localhost.localdomain kernel: nvidia 0000:01:00.0: vgaarb: deactivate vga console
Jul 18 10:40:21 localhost.localdomain systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:nvidia_0.
Jul 18 10:40:21 localhost.localdomain kernel: fbcon: nvidia-drmdrmfb (fb0) is primary device
Jul 18 10:40:21 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -22
Jul 18 10:40:21 localhost.localdomain kernel: nvidia 0000:01:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device
Jul 18 10:40:21 localhost.localdomain /usr/bin/nvidia-powerd[1194]: Dbus Connection is established
Jul 18 10:40:24 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:40:28 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:40:31 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:40:34 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:40:37 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:40:40 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:40:44 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:40:47 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:40:50 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:40:53 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:40:57 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:41:00 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:41:03 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:41:06 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:41:09 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:41:13 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:41:16 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:41:19 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:41:22 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:41:26 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:41:29 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 10:44:55 localhost.localdomain nvidia-settings[4739]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jul 18 10:46:48 localhost.localdomain sudo[5653]:   user : TTY=pts/3 ; PWD=/home/user ; USER=root ; COMMAND=/usr/sbin/modprobe -r nvidia-drm
Jul 18 10:57:38 localhost.localdomain sudo[10503]:   user : TTY=pts/4 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/cat /sys/module/nvidia_drm/parameters/modeset
Jul 18 11:05:55 localhost.localdomain systemd[1]: Stopping nvidia-powerd service...
Jul 18 11:05:55 localhost.localdomain systemd[2213]: app-nvidia\x2dsettings@09a75fccc5404c6cadb37c29a7c4989c.service: Main process exited, code=exited, status=1/FAILURE
Jul 18 11:05:55 localhost.localdomain systemd[2213]: app-nvidia\x2dsettings@09a75fccc5404c6cadb37c29a7c4989c.service: Failed with result 'exit-code'.
Jul 18 11:05:55 localhost.localdomain /usr/bin/nvidia-powerd[1194]: Quit successfully
Jul 18 11:05:55 localhost.localdomain systemd[1]: nvidia-powerd.service: Deactivated successfully.
Jul 18 11:05:55 localhost.localdomain systemd[1]: Stopped nvidia-powerd service.
Jul 18 11:05:55 localhost.localdomain systemd[1]: nvidia-powerd.service: Consumed 11.696s CPU time.
Jul 18 11:05:59 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 11:06:02 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 11:06:05 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
Jul 18 11:06:09 localhost.localdomain kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0

+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.90.07              Driver Version: 550.90.07      CUDA Version: 12.4     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 3060 ...    Off |   00000000:01:00.0  On |                  N/A |
| N/A   43C    P5             26W /  130W |     586MiB /   6144MiB |      5%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
                                                                                         
+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A      1878      G   /usr/bin/Xorg.bin                             152MiB |
|    0   N/A  N/A      2292      G   /usr/bin/kwalletd6                              2MiB |
|    0   N/A  N/A      2441      G   /usr/bin/ksmserver                              2MiB |
|    0   N/A  N/A      2443      G   /usr/bin/kded6                                  2MiB |
|    0   N/A  N/A      2444      G   /usr/bin/kwin_x11                              19MiB |
|    0   N/A  N/A      2555      G   /usr/bin/plasmashell                           51MiB |
|    0   N/A  N/A      2562      G   /usr/libexec/kactivitymanagerd                  2MiB |
|    0   N/A  N/A      2565      G   ...c/polkit-kde-authentication-agent-1          2MiB |
|    0   N/A  N/A      2566      G   /usr/libexec/org_kde_powerdevil                 2MiB |
|    0   N/A  N/A      2567      G   /usr/libexec/xdg-desktop-portal-kde             2MiB |
|    0   N/A  N/A      2742      G   /usr/bin/kaccess                                2MiB |
|    0   N/A  N/A      2744      G   /usr/libexec/DiscoverNotifier                   2MiB |
|    0   N/A  N/A      2747      G   /usr/bin/kalendarac                             2MiB |
|    0   N/A  N/A      2790      G   /usr/bin/akonadi_control                        2MiB |
|    0   N/A  N/A      2807      G   /usr/bin/akonadi_akonotes_resource              2MiB |
|    0   N/A  N/A      2808      G   /usr/bin/akonadi_archivemail_agent              2MiB |
|    0   N/A  N/A      2809      G   /usr/bin/akonadi_birthdays_resource             2MiB |
|    0   N/A  N/A      2810      G   /usr/bin/akonadi_contacts_resource              2MiB |
|    0   N/A  N/A      2811      G   .../bin/akonadi_followupreminder_agent          2MiB |
|    0   N/A  N/A      2812      G   /usr/bin/akonadi_ical_resource                  2MiB |
|    0   N/A  N/A      2813      G   /usr/bin/akonadi_indexing_agent                 2MiB |
|    0   N/A  N/A      2814      G   /usr/bin/akonadi_maildir_resource               2MiB |
|    0   N/A  N/A      2828      G   /usr/bin/akonadi_maildispatcher_agent           2MiB |
|    0   N/A  N/A      2829      G   /usr/bin/akonadi_mailfilter_agent               2MiB |
|    0   N/A  N/A      2830      G   /usr/bin/akonadi_mailmerge_agent                2MiB |
|    0   N/A  N/A      2831      G   /usr/bin/akonadi_migration_agent                2MiB |
|    0   N/A  N/A      2832      G   /usr/bin/akonadi_newmailnotifier_agent          2MiB |
|    0   N/A  N/A      2833      G   /usr/bin/akonadi_notes_agent                    2MiB |
|    0   N/A  N/A      2834      G   /usr/bin/akonadi_sendlater_agent                2MiB |
|    0   N/A  N/A      2836      G   /usr/bin/akonadi_unifiedmailbox_agent           2MiB |
|    0   N/A  N/A      3047      G   /usr/lib64/firefox/firefox                    186MiB |
|    0   N/A  N/A      3197      G   /usr/lib/mozilla/kmozillahelper                 2MiB |
|    0   N/A  N/A      4738      G   /usr/libexec/baloorunner                        2MiB |
|    0   N/A  N/A      7134      G   /usr/libexec/xdg-desktop-portal-kde             2MiB |
|    0   N/A  N/A      7391      G   /usr/bin/systemsettings                        22MiB |
|    0   N/A  N/A      8473      G   /usr/bin/konsole                                2MiB |
+-----------------------------------------------------------------------------------------+

0000:00:02.0 VGA compatible controller: Intel Corporation TigerLake-H GT1 [UHD Graphics] (rev 01)
0000:01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1)

I have an MUX hybrid-capable system (now only the dedicate gpu is enabled).