| Summary: | Screen stuck flipping between frames | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Jonathan L Hanmann <jhanmann> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | nate, xaver.hugl |
| Priority: | NOR | ||
| Version: | 6.1.90 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Requested journalctl output
Additional log from another freeze Wayland Crash/Lockup Journal Output X11 Crash/Lockup journalctl output |
||
|
Description
Jonathan L Hanmann
2024-09-15 12:34:44 UTC
Please attach the output of
> journalctl --user-unit plasma-kwin_wayland --boot 0
after the problem happens
Created attachment 173753 [details]
Requested journalctl output
Took a fairly long time to reproduce this time of course. Ran for several hours before freezing up.
Created attachment 173776 [details]
Additional log from another freeze
Freeze occurred around the Sep 17: 08:45-08:46 timestamp.
okay, there's some suspicious lines in there, but nothing clearly pointing at a specific problem.
When the freeze happens again, could you get the output of
> sudo dmesg
and attach the output of that here?
Created attachment 174429 [details]
Wayland Crash/Lockup Journal Output
This systemctl output is from a Plasma 6 Wayland session that locked up. There is a Panthor crash right at the time of the Plasma screen issue. I stripped out all the extraneous log information and zeroed it into the correct time and likely events related to the problem.
I expect you're going to say this is a kernel/Mesa problem and I probably couldn't disagree based on this information. Even if somehow Plasma was doing something wrong from an GL perspective it should cause this. I'll leave that up to your expertise though of course.
Created attachment 174430 [details]
X11 Crash/Lockup journalctl output
This is likely the same problem occurring on an X11 session. I don't know if this will contribute anything unique from that I provided for the Wayland session but here it is anways.
As some additional information, I am using Armbian kernel builds. I reverted from a kernel version 6.1.75 back to 6.1.43 and it doesn't appear to have the same screen lockup issue on X11 so far. I've run for about three days now and it seems stable. It is a little harder for me to test Wayland since I am having some other issues that appear unique to it. I'll continue testing and investigating and let you know if I find anything out. I still get a lot of these message but they don't appear to cause anything fatal. It may not be related to this particular issue but just FYI. Oct 07 02:46:51 rock-5b-3 kernel: [drm:vop2_plane_atomic_check] *ERROR* Invalid size: 64x3->64x3, min size is 4x4 or Oct 07 02:46:51 rock-5b-3 kernel: [drm:vop2_plane_atomic_check] *ERROR* Invalid size: 64x2->64x2, min size is 4x4 Another 2 days and still no crashes or other visible issues on X11 with 6.1.43 series kernel. Must be something changed in later kernel versions. Wayland still doesn't work well and Mesa overall is slower (glmark) than it should be even on X11. This seems to be something with my system but I haven't isolated the performance degradation cause yet. Different issue anyways... Yeah the plane size warning is weird - KWin never uses planes with a height that small - but the actual source of the problem seems to be
> [drm] *ERROR* Unhandled Page fault in AS1 at VA 0x00007FFFF6410000
Which is definitely a kernel bug
|