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 (1 child)

But who's going to go to that effort on their slab of glass?

Those who would like to make extra sure their data stays private. On an unrelated note, what kinds of data could be considered confidential in said log?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 2 points 2 days ago

    Those who would like to make extra sure their data stays private.

    Yes, well, exactly. You know not every question is a literal question, right?

    what kinds of data could be considered confidential in said log?

    I was wondering that myself. It's "the kmsg log", something to do with kernel mode switching or "graphics". My guess: the log itself is not problematic, but there might be some metadata added. Or then one creates that metadata by submitting the QR code.

  • permalink
  • fedilink
  • source
  • parent