https://bugs.kde.org/show_bug.cgi?id=494044
--- Comment #1 from Matt Fagnani <matt.fagn...@bell.net> ---
coredumpctl gdb showed that in KWin::DrmGpu::presentationClock the pointers
this and m_presentationClock appeared to be invalid or corrupted since
dereferencing them resulted in errors like "Cannot access memory at address
0xcb71386c291b0381" and similarly in KWin::DrmGpu::pageFlipHandler for the
pointer gpu in frame 5. The pageflip timeouts might've been related to such
problems.
Core was generated by `/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0
--xwayland-fd 8 --xwayl'.
Program terminated with signal SIGSEGV, Segmentation fault.
--Type <RET> for more, q to quit, c to continue without paging--c
#0 0x00007f9dd7280944 in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7f9dd9b8bb80 (LWP 2147))]
(gdb) bt
#0 0x00007f9dd7280944 in __pthread_kill_implementation () from
/lib64/libc.so.6
#1 0x00007f9dd722825e in raise () from /lib64/libc.so.6
#2 0x00007f9ddaeaa1a2 in KCrash::defaultCrashHandler(int) () from
/lib64/libKF6Crash.so.6
#3 <signal handler called>
#4 KWin::DrmGpu::presentationClock (this=0xcb71386c291b0381) at
/usr/src/debug/kwin-6.1.90-4.fc42.x86_64/src/backends/drm/drm_gpu.cpp:131
#5 KWin::DrmGpu::pageFlipHandler (fd=22, sequence=0, sec=2683, usec=631215,
crtc_id=36, user_data=0x7f9d9800a470)
at
/usr/src/debug/kwin-6.1.90-4.fc42.x86_64/src/backends/drm/drm_gpu.cpp:566
#6 0x00007f9dd7739580 in drmHandleEvent (fd=22, evctx=0x7fffbef87cc0) at
../xf86drmMode.c:1070
#7 0x00007f9dda8f0b8c in KWin::DrmGpu::dispatchEvents (this=<optimized out>)
at /usr/src/debug/kwin-6.1.90-4.fc42.x86_64/src/backends/drm/drm_gpu.cpp:581
#8 0x00007f9dd794c872 in void doActivate<false>(QObject*, int, void**) () from
/lib64/libQt6Core.so.6
#9 0x00007f9dd795a44d in QSocketNotifier::activated(QSocketDescriptor,
QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from
/lib64/libQt6Core.so.6
#10 0x00007f9dd795ac5b in QSocketNotifier::event(QEvent*) () from
/lib64/libQt6Core.so.6
#11 0x00007f9dd8c3d218 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt6Widgets.so.6
#12 0x00007f9dd78e6e08 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt6Core.so.6
#13 0x00007f9dd7aa68c6 in
QEventDispatcherUNIXPrivate::activateSocketNotifiers() () from
/lib64/libQt6Core.so.6
#14 0x00007f9dd7aa71d4 in
QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /lib64/libQt6Core.so.6
#15 0x00007f9dd8656492 in
QUnixEventDispatcherQPA::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() from /lib64/libQt6Gui.so.6
#16 0x00007f9dd78f3b43 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib64/libQt6Core.so.6
#17 0x00007f9dd78ef9fc in QCoreApplication::exec() () from
/lib64/libQt6Core.so.6
#18 0x0000564cb5f588de in main ()
(gdb) frame 4
#4 KWin::DrmGpu::presentationClock (this=0xcb71386c291b0381) at
/usr/src/debug/kwin-6.1.90-4.fc42.x86_64/src/backends/drm/drm_gpu.cpp:131
131 return m_presentationClock;
(gdb) p this
$1 = (const KWin::DrmGpu * const) 0xcb71386c291b0381
(gdb) p *this
Cannot access memory at address 0xcb71386c291b0381
(gdb) p m_presentationClock
Cannot access memory at address 0xcb71386c291b03ad
(gdb) frame 5
#5 KWin::DrmGpu::pageFlipHandler (fd=22, sequence=0, sec=2683, usec=631215,
crtc_id=36, user_data=0x7f9d9800a470)
at
/usr/src/debug/kwin-6.1.90-4.fc42.x86_64/src/backends/drm/drm_gpu.cpp:566
566 std::chrono::nanoseconds timestamp =
convertTimestamp(gpu->presentationClock(), CLOCK_MONOTONIC,
(gdb) p gpu
$3 = (KWin::DrmGpu * const) 0xcb71386c291b0381
(gdb) p *gpu
Cannot access memory at address 0xcb71386c291b0381
The idle state I mentioned involved a dimming or shutting off of the VM screen
with a lock screen possibly briefly shown. In Power Management in System
Settings, the Dim automatically setting was 5 minutes and Turn off screen was
10 minutes by default. The VM's screen was dimmer than usual after kwin
crashed.
--
You are receiving this mail because:
You are watching all bug changes.
