Bug 493754 - random hard freeze - kwin_wayland_drm: Pageflip timed out! This is a kernel bug
Summary: random hard freeze - kwin_wayland_drm: Pageflip timed out! This is a kernel bug
Status: RESOLVED DUPLICATE of bug 493277
Alias: None
Product: kwin
Classification: Plasma
Component: platform-drm (show other bugs)
Version: 6.1.5
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-27 20:58 UTC by Tim D
Modified: 2024-10-17 12:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
journalctl -b -1 (3.47 MB, text/x-log)
2024-09-27 20:58 UTC, Tim D 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tim D 2024-09-27 20:58:40 UTC 
Created attachment 174158 [details]
journalctl -b -1

I get random intermittent hard freezes around sleep. this has been an issue for majority of 2024, so doesnt appear related to a specific version of software. This can be a hard freeze attempting to enter sleep, or on resume.  This can be frequent multiple times a day, or weeks between a freeze. Unable to reliably reproduce. backtrace log attempts have been unsuccessful.

The system is completely unresponsive. sysReq+REISUB does not work, CapsLock doesnt toggle the indicator led, and system does not recover after any period of time.

Typically I get no info in dmesg/journalctl, but this time there appears to be something (rather than absolutely nothing). I've included a full `journalctl -b -1` output log file.
Laptop is Framework 13", WD SN770 black nvme, 2x 16GB ram. Fedora40 KDE Spin.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2
Kernel Version: 6.10.11-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × 12th Gen Intel® Core™ i5-1240P
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Comment 1 Nate Graham 2024-09-30 19:43:51 UTC 

*** This bug has been marked as a duplicate of bug 493277 ***