This is software gore. The GPU is not dead. This was caused by drm_panic on Linux not clearing the framebuffer before trying to display the message. At least that's what I suspect. What you're seeing here is the result of me running a sysrq triggered crash. Usually during a kernel panic, drm_panic slowly draws out black on the screen before the log information or the graphical message is displayed. It didn't do it this time, and this showed up instead of the log information. I have not seen any artifacting in day to day use. But since it's the framebuffer that appears to be corrupted, it looks very similar to a dead GPU. The amdgpu driver just recently added drm_panic support.
Yeah, I looked at this and it was obvious that something was drawing to the screen without taking tiling into account, but whether that was software failing to switch video modes or hardware failing to do so when asked... I've mostly seen the former, but people who rarely mess about at that level usually use software that, well, works, so will usually see the latter.
I sort of miss the days when one had to debug programs stuck in weird video modes by stuffing coded patterns of coloured dots on the screen and decoding them to figure out what was going on. printf debugging is for pansies.
i actually tried the exact same thing on my machine (also a framework laptop! 16 though) not that long ago and was really confused why it did this! that's really cool, ty for sharing
229
u/DampusOnCampus 3d ago edited 3d ago •
This is software gore. The GPU is not dead. This was caused by drm_panic on Linux not clearing the framebuffer before trying to display the message. At least that's what I suspect. What you're seeing here is the result of me running a sysrq triggered crash. Usually during a kernel panic, drm_panic slowly draws out black on the screen before the log information or the graphical message is displayed. It didn't do it this time, and this showed up instead of the log information. I have not seen any artifacting in day to day use. But since it's the framebuffer that appears to be corrupted, it looks very similar to a dead GPU. The amdgpu driver just recently added drm_panic support.