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
[–] 22 points 3 days ago (1 child)

Edit: yes, it was Systemd who implemented it.

Nah, systemd-bsod is different and designed to show info about boot failures:

systemd-boot screenshot

It's rather quite useless.

drm_panic on the other hand has nothing to do with systemd, and is what's shown in OPs post. The link can be quite useful for users to post their issues on bug reports or whatever. But if you know what you're doing, then it's pretty easy to configure it to print text instead.

Also remember, the reason drm_panic exists is because graphical outputs would otherwise freeze during a kernel panic, and not show anything useful.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •