Direct scanout spams dmesg with framebuffer memory not appropriate for scanout

using an external monitor connected to my laptop and running wine games it eventually begins spamming to dmesg/journal “[drm] [nvidia-drm] [GPU ID 0x00000100] Framebuffer memory not appropriate for scanout”, i made a bugreport at 479958 – nvidia spams journal/dmesg with a second monitor on a dgpu setup but the devs seem to think “This happens because KWin tries to do direct scanout. If that fails, the driver should not log anything” and suggested i make a post here about it.

it only happends when an external monitor is connected and it requires wayland “direct scanout”, and i havent tried any other DE’s or window managers.

this has occured for a long time 525.xx up to 550.xx drivers

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

Same happens on Gnome. Nvidia driver 550 .54.14. Error is yeld to dmesg near login.

Two external monitors trough TB4 dock.

[   47.754856] [drm] [nvidia-drm] [GPU ID 0x00000100] Framebuffer memory not appropriate for scanout
[   47.754865] [drm] [nvidia-drm] [GPU ID 0x00000100] Framebuffer memory not appropriate for scanout