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.

  • A_norny_mousse@piefed.zipOP
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    21 hours ago

    Thanks for the info, but this is not that.

    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 makes sense considering systemd was not running when that happened.