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.

  • Sanguine@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    1
    ·
    21 hours ago

    I never scan, just check the journal for errors from previous boot after restart. Most recent was my pcie low power shenanigans with my onboard WiFi. Simple fix and now its working /no bsod since.