47
BSOD (thelemmy.club)
submitted 4 days ago* (last edited 3 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
[–] [S] 2 points 3 days ago (1 child)

I get what you mean but this is not fediverse-specific.

I have meanwhile found out that the screen above was not produced by systemd but rather by the drm_panic kernel module. Makes sense since systemd wasn't running when it happened.

Next time it happens (hopefully not) I'll try to switch ttys, maybe the logs are still visible, white on black.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 3 days ago*

    It's a subculture phenomenon, and lemmy linux is a subculture of a subculture, so it's more intense.

    I've been a moderator on some linux reddits in the past. And the less users there were in the sub, the more negativity, rudeness, gatekeeping and other toxicity was there. But ofc what I say is just an opinion based on my subjective experience so idk.

    The linux kernel bsod is even younger than that, august 2024 iirc.

  • permalink
  • fedilink
  • source
  • parent