SUMMARY Plasma Wayland session hard crashes (full system lockup) when using the ASUS XG27ACDNG monitor with DisplayPort 1.4 or when HDR is enabled. System is completely unresponsive, even to TTY. Issue only occurs on Wayland; X11 works fine. STEPS TO REPRODUCE 1. Set monitor (ASUS XG27ACDNG) DisplayPort mode to 1.4 in monitor OSD 2. Attempt to log in to a Wayland session via SDDM or TTY (startplasma-wayland) 3. If DisplayPort 1.2 is used instead, log in and then enable HDR via KDE System Settings OBSERVED RESULT With DP 1.4: After attempting to start a Wayland session, the screen goes black and the entire system hard-freezes (requires physical reboot - no TTY available). With DP 1.2 + HDR enabled: Wayland session hard-freezes in the same way after toggling HDR. With DP 1.2 and HDR disabled: Wayland session works, but refresh rate is limited to 179.96Hz, and HDR functionality is lost. EXPECTED RESULT Plasma Wayland session should successfully initialize and remain stable with DisplayPort 1.4 and HDR enabled. High refresh rates (360Hz) and HDR should function without freezing the system. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.4.2 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.1 Kernel Version: 6.15.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor Memory: 96 GiB of RAM (93.4 GiB usable) Graphics Processor 1: NVIDIA GeForce RTX 4080/PCIe/SSE2 Graphics Processor 2: NVIDIA GeForce RTX 4080/PCIe/SSE2 ADDITIONAL INFORMATION Problem began immediately after switching from an older monitor to the XG27ACDNG. X11 sessions work without issue at 360Hz and with HDR enabled. Using Wayland, switching the monitor’s DP spec from 1.4 to 1.2 prevents crashes, but reduces refresh rate to 179.96Hz and disables HDR. Issue appears to be specific to the combination of: -NVIDIA 575.64.03 driver -DisplayPort 1.4 -HDR -Wayland session on Plasma 6.4.2
I mistakenly said "X11 sessions work without issue at 360Hz and with HDR enabled." Of course, it does not work with HDR enabled as their is no HDR in X11. Disregard that last part please. Thanks!
If something froze, it may have crashed. We need a backtrace of it so we can figure out what's going on. Can you look to see if there are core dumps, and please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ? Thanks!
Created attachment 183150 [details] journal-ctl
(In reply to TraceyC from comment #2) > If something froze, it may have crashed. We need a backtrace of it so we can > figure out what's going on. Can you look to see if there are core dumps, and > please attach a backtrace of the crash using the coredumpctl command-line > program, as detailed in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ? > > Thanks! Thanks for the follow-up! Unfortunately, coredumpctl didn’t show any entries related to the crash. That said, I didn’t want to return empty-handed. I reproduced the issue again by enabling HDR in Wayland and then captured the system journal from the previous boot using journalctl -b -1. I’ve attached the resulting log file (wayland-crash.log) for your review. Here are the repeating messages that filled the journal at the moment of the freeze: kwin_wayland_drm: Atomic modeset test failed! Invalid argument kwin_scene_opengl: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" These errors seem to loop rapidly until the system completely locks up and must be power-cycled. They happen consistently whenever HDR is enabled on my ASUS XG27ACDNG (360Hz, HDR10, DisplayPort 1.4), and only on Wayland. X11 works without issue, even with HDR and 360Hz enabled. Let me know if there’s anything else I can capture or test! I’m happy to help however I can!
(In reply to Nicholas Page from comment #4) > These errors seem to loop rapidly until the system completely locks up and > must be power-cycled. They happen consistently whenever HDR is enabled on my > ASUS XG27ACDNG (360Hz, HDR10, DisplayPort 1.4), and only on Wayland. X11 > works without issue, even with HDR and 360Hz enabled. Oops, again, HDR only exists in Wayland... Apologies. To clarify: These errors loop rapidly until the system locks up completely and requires a hard reboot. The issue only occurs under Wayland and is 100% reproducible when enabling HDR on my ASUS XG27ACDNG (360Hz, HDR10, DisplayPort 1.4).
Really need an edit button... One more comment, I did that last crash with my monitor set to DisplayPort 1.2, not 1.4.
Created attachment 183151 [details] ASUS XG27ACDNG EDID decode output
> kwin_wayland_drm: Atomic modeset test failed! Invalid argument Unfortunately, drivers are normally extremely light on details about what went wrong. Please follow https://invent.kde.org/plasma/kwin/-/wikis/Debugging/Debugging-DRM-issues to get a debug log of the problem.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
Created attachment 186653 [details] DRM Debug Log (First 20000 lines)
Created attachment 186655 [details] DRM Debug Log (Last 20000 lines)
Uploaded two log files using the resource provided. I wanted to wait NVIDIA driver 580.105.08 was out before continuing. After updating to that and to Plasma 6.5.2, some issues are resolved. HDR works completely normally and KWIN no longer hard crashes when setting the refresh rate to 359.98 Hz in the Display Configuration menu in the Settings. However, the displays only show black and that does not go away unless switching to a different TTY and then back. Upon doing so, the refresh rate is set back to 179.96 Hz even though the "Refresh rate" dropdown still shows 359.98 Hz selected.
I forgot to mention that I can also set the DisplayPort stream to 1.4 now without issue!