Thanks for that. I am someone effected heavily by the error.
Mostly playing wow Classic (TBC anniversary)
I have implemented the patch above into the new kernel and that particular error has stopped, but now am experiencing freezes with the below error. Apr 18 07:17:34 <hostname-redacted> plasma-systemmonitor[14531]: qrc:/qt/qml/org/kde/desktop/TreeViewDelegate.qml:126:13: Unable to assign [undefined] to QString Apr 18 07:17:34 <hostname-redacted> plasma-systemmonitor[14531]: Index QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid)
Since I seem to be having one issue after another (on Windows too) I’m finding it very hard to pinpoint if I’m having driver/software issues, or my hardware is just cooked.
i think that with new update which had a line in changelog broke the fix:
”dropped s01x power management due to issues with the nvidia 595 driver”.
When i first updated freezing returned within 5 minutes. I think this happened because the fix i used was “amdgpu.dcdebugmask=0x12” and i think this got disabled by the update. Is there a workaround to this?
Same here. Cross-posting what I said on the amdgpu forums…
Some background: Since GNOME removed Xorg support, I’ve been using COSMIC desktop without crashes these past few months. COSMIC runs on Wayland. Therefore, GNOME and KDE were doing something to cause my pageflip errors, which COSMIC was not. (It may still have been an amdgpu bug, as the error logs suggested, but the bottom line is that whatever was triggering that bug, it did not happen in COSMIC.)
Often, when a new Linux kernel version or Radeon driver became available, I would switch back to GNOME for a test, only to have it eventually seize up. After a recent kernel update, I did the same test, and everything has been working well so far. (Not to jinx it or anything.)
I recall doing my irregular GNOME test when Linux 7 first dropped, and the issue was not fixed. Whatever appears to have fixed it, happened in the last few minor version releases.
Currently on Linux 7.0.8-arch1-1. Couldn’t tell you if it’s this kernel version that fixed it, but dropping the version number here in case it’s useful to someone.
Hi there, Lenovo ThinkPad T14S here who is encountering this symptom
Unlike the OP, my tty’s do NOT seem accessible once the occourance happens. I have tried all kinds of things, alt+ctrl+fX combinations and so on, I can’t seem to get any responsiveness out of it.
My desktop went solid black, with a visible mouse cursor, most recently. And I spent several minutes mashing key combos until giving up and holding the power button down and doing a hard power-down
I will say though that this most definitely affected me on Pop_OS! with Cosmic as well – and I had originally chalked it up to being something wrong with Cosmic or Pop – but now that I’ve experienced & read about it here, I can see it’s actually a much wider-spread problem!
I am on the latest version of Cachy now, eager for the problem to be fixed. Thanks!