47
BSOD (thelemmy.club)
submitted 3 days ago* (last edited 2 days ago) by to c/linux@lemmy.ml
37 comments fedilink hide all child comments
 

final edit: You want real logs instead? add this to your kernel command: drm.panic_screen=kmsg

Kinda funny, kinda neat.

I have no idea what the QR-code might reveal (I could not read it from this picture), so I pixelised it just to be sure.

FWIW I know exactly what happened and did not panic. To reproduce, boot your device with init=/bin/sh, then type exit.

CachyOS

The picture above is generated by Drm panic which is part of the kernel itself, or maybe a separate module. The data in the QR code is the kmsg log.

Not systemd, which wasn't running when that happened.

And it's been around for years; I guess I haven't had a kernel panic in a long time.

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 3 days ago

I disagree. The logs typically do not fit on the screen in text form, especially on low resolutions (like if the system has to fall back on an alternative graphics mode, which tends to happen more frequently in the event of a crash). Granted, a website is not the best possible solution and has the risk of leaking data but at least it is "a" solution. The data is encoded sure, but not in an obfuscated way. If you wanted, you could decode it with other means (for example a dedicated app that scans it).

  • permalink
  • fedilink
  • source
  • parent