https://bugs.kde.org/show_bug.cgi?id=494044
--- Comment #8 from Matt Fagnani <matt.fagn...@bell.net> --- (In reply to Vlad Zahorodnii from comment #7) > From the sentry bug report, it's interesting to see "kwin_wayland_drm: > atomic commit failed: Invalid argument" in the logs. I reproduced the problem again with Plasma 6.2.0 with Lock screen set to 1 minute and Shut off screen set to 1 minute and submitted with drkonqi as an automatic report which is what you might have referred to. The journal in the 1-2 m before the four crashes of this type showed "kwin_wayland_wrapper[3539]: waiting got error - 16, slow gpu or hang?" then "kwin_wayland_drm: Pageflip timed out! This is a kernel bug" repeatedly with "kwin_wayland_drm: No drm events for gpu "/dev/dri/card1" within last 30 seconds" once. "kwin_wayland_drm: atomic commit failed: Invalid argument" was the last error before the crash in that automatic report I made, but it wasn't shown before the other three crashes. The pageflips timeouts and gpu errors might need to happen enough times when the screen turned off and on and the lock screen appeared. Then the gpu pointer in KWin::DrmGpu::pageFlipHandler might've been invalid so that when it was dereferenced by std::chrono::nanoseconds timestamp = convertTimestamp(gpu->presentationClock(), CLOCK_MONOTONIC, ... in it, the crash happened. The lock screen sometimes wasn't shown after the screen shut off and turned on again when I set Lock screen set to 1 minute and Shut off screen set to 1 minute, so for reproducing the problem might be more likely if one sets the lock screen time to be shorter than the Shut off screen time as is default so that the lock screen definitely has time to start first. So I set Lock screen set to 1 minute and Shut off screen set to 2 minutes, and reproduced the problem as before. I submitted an automatic report for that crash also. I didn't see this crash in VMs with 3D acceleration disabled using the llvmpipe mesa driver and virtio-gpu kernel driver, or on bare metal with radeonsi mesa driver and amdgpu kernel driver. So the problem might be specific to the virgl and virtio-gpu combination. Thanks. -- You are receiving this mail because: You are watching all bug changes.
