No one told me kernel panics could be diagonal

[-]

RyanGates69@reddit

This Advent Of Code is getting ridiculous

[-]

Training_Advantage21@reddit

I'm a bit confused. The kernel panic was on the linux box and the chromebook was used as a camera?

[-]

When the computer that panic'd is running normally, are the graphics sometimes messed up in that same way, such as during bootup or if you hit Ctrl+Alt+F1 (or F2, or F3...) to switch to a VTTY console?

[-]

FinancialTrade8197@reddit

looks like your ram is going bye bye....

graphical issue + concerning kernel stack corrupted message

[-]

spacelama@reddit

It's not a corrupted stack dump - it's a QR-code which encodes the stack-dump, with some graphical offset issue so the image is skewed.

[-]

FinancialTrade8197@reddit

If you look on the bottom right, it says "Kernel stack is corrupted"

[-]

bobpaul@reddit

But that's what caused the kernel panic in the first place. When the kernel detected stack corruption, the stack was dumped (in the form of the QR code) and execution was halted.

A display issue has caused QR code to display wrong. With a high resolution photo and some effort one could fix the QR code and scan it. We have no reason to assume the stack dump contained inside the QR code is corrupted. The display issue may or may not be related to the kernel panic.

[-]

britaliope@reddit

concerning kernel stack corrupted message

Concerning kernel stack corrupted corrupted message

[-]

monocasa@reddit

Nah, this doesn't look like a RAM issue, but a bug in kernel mode setting.

This kind of graphical issue is a crtc configuration error, which woudl be weird to be a RAM error and have gotten this far.

[-]

meancoot@reddit

Unless it was glitched before the error popped up this looks like a bug in the video driver setting up the “scan out” hardware for the error message than anything else. I don’t think bad ram would explain the block offsets here.

[-]

FinancialTrade8197@reddit

From my experience on Windows (back when I had bad ram, and I use Linux now) my bad RAM would sometimes screw with the graphics on the BSOD. It didn't look exactly like this, but it would have weird patterns. It wasn't the GPU as I replaced the RAM and it worked fine after that. That behavior is probably similar on Linux too

[-]

Norta92@reddit

Weeee, he doesn't know too. Now that's another level. Hahaha

[-]

xzer@reddit

Admin hes doing it sideways

[-]

7thhokage@reddit

Man, shit really went sideways on ya huh.

[-]

darkalemanbr@reddit

When the error errors too you just know it's BAD.

[-]

Broccoli_Potential@reddit

yeah when the panic message itself starts glitching out, that's when you know you're in deep

[-]

OptimalAnywhere6282@reddit

r/yourjokebutworse

[-]

Ridenberg@reddit

You KNOW your computer is in TROUBLE when even the COMMENTS start glitching and REPEATING

[-]

Tiger_man_@reddit

this is the linuxest linux ive ever see

[-]

whiskeytown79@reddit

Ah your kernel didn't drink its V-8 this morning!

[-]

markus40@reddit

I had kernel panics in the past. But now I realize I probably hadn't had one in over 15 years. I certainly never saw a panic with a blue screen and QR code. And I run Arch Linux on all my machines. I can't even remember when Gnome bailed out on me for the last time. It certainly has to be in the 3.x period and not in the 4x period. At work it is another story. I had servers crash on me. But mostly a VM underlying architecture of the client mismatch.

[-]