https://bugs.kde.org/show_bug.cgi?id=479958
Bug ID: 479958
Summary: nvidia spams journal/dmesg with a second monitor on a
dgpu setup
Classification: Plasma
Product: kwin
Version: 5.92.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: tomenglun...@gmail.com
Target Milestone: ---
SUMMARY
im not sure if this is a kwin bug or a nvidia one but if i use an external
monitor on my dgpu and run a game in wine or some other random thing eventually
it begins spamming "[drm] [nvidia-drm] [GPU ID 0x00000100] Framebuffer memory
not appropriate for scanout" in dmesg/journal. this happend before on 5.27.x
series and testing the 5.92.0 RC from archlinux kde-unstable repo it does
aswell. was seeing posts like
https://forums.developer.nvidia.com/t/hardware-cursor-is-not-working-on-wayland-drm-sessions/261853/2
so i thought id wait until that is figured out but if im not mistaken this RC
has the HW cursor patches from
https://invent.kde.org/plasma/kwin/-/merge_requests/4695
STEPS TO REPRODUCE
1. run a laptop with a nvidia dgpu and attach a external monitor
2. launch a wine game fullscreened
3. nvidia begins spamming
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.7.0
Kernel Version: 6.6.8-273-tkg-eevdf-llvm (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics
Memory: 30,7 GiB of RAM
Graphics Processor: AMD Radeon Graphics
--
You are receiving this mail because:
You are watching all bug changes.
