On Thu, Apr 09, 2026 at 09:32:22AM -0400, Stefan Monnier wrote: > >> > Hi, that was all good advice. I'd add that before making a bug report, > >> > I'd suggest checking something like: > >> > > >> > $ sudo journalctl -b -g 'not supported' > >> > > >> > because if the GPU driver is reporting that certain graphics capabilities > >> > are not supported, then the bug would be in the software that attempts > >> > to use those capabilities when they aren't available. > >> > >> If it crashes the whole OS, the bug is not just in the application but > >> further down (somewhere in the stack, as described by the Wanderer). > > > > Usually, but not always, I can ssh in, send a few signals to some > > applications and then type 'poweroff'. > > Aha: I assumed "crashes Trixie" means the whole OS crashed. > > If you can still access the machine via SSH, then presumably only the > video part is wedged. Still: if the whole user session is made unusable > and the graphics stack is sufficiently confused that you can't "log out and > log back in" (as seems to be the case based on your description), then > the problem is not just in the application but somewhere within the > graphics stack.
Your description is correct. Graphics/console becomes unusable, it freezes showing whatever was being displayed. Curiously the mouse still moves. Sometimes (wild estimate of 1 in 5 times) the screen goes completely white. I set firefox (& librewolf) config to not use hardware acceleration. Stable for a week, but a couple of hours after me telling the list it happened again. I clicked on a link in Firefox and it froze. I was able to ssh in send HUP to important applications & start shutdown. Messages in the system journal, many like this: Apr 08 16:22:16 mint.phcomp.co.uk kernel: radeon 0000:01:00.0: ring 0 stalled for more than 10484msec Apr 08 16:22:16 mint.phcomp.co.uk kernel: radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000002bf98d1 last fence id 0x0000000002bf9958 on ring 0) Apr 08 16:22:16 mint.phcomp.co.uk kernel: radeon 0000:01:00.0: ring 5 stalled for more than 10236msec Apr 08 16:22:16 mint.phcomp.co.uk kernel: radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000041106 last fence id 0x0000000000041107 on ring 5) Apr 08 16:22:16 mint.phcomp.co.uk kernel: radeon 0000:01:00.0: ring 3 stalled for more than 10236msec Then some: Apr 08 16:22:17 mint.phcomp.co.uk kernel: radeon 0000:01:00.0: scheduling IB failed (-35). Apr 08 16:22:17 mint.phcomp.co.uk kernel: [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35) lshw says that is a Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] I prolly ought to just replace it, it is 14 years old. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>
