Announcement

Collapse
No announcement yet.

Linux 6.10 Preps A Kernel Panic Screen - Sort Of A "Blue Screen of Death"

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • wallentx
    replied
    Originally posted by duby229 View Post

    ^^^ This...

    Linux already had a means to display error messages in case of kernel panic.

    EDIT: I'm wrong about this statement, I had assumed that because I had seen kernel panic messages in the past, but it isn't true. I just spent half the day building a linux system testing this out and in fact it does hang on a black screen.

    I've never personally experienced a hang to a black screen, but if you have a desktop running then kernel panics do in fact...
    This is EXACTLY why I made this, which may have been unable to properly describe the problem: https://github.com/systemd/systemd/issues/30804

    If anyone can gather what I'm trying to say, and can paraphrase it, please, feel free to sound off in that issue.

    The "Troubleshooting a black screen" is a problem that is super annoying, and sort of needs to be handled at every DM level (and it seems like canonical is willing to take my PR for lightdm, except that its currently held up due to an exploit-ish issue i found in their GH actions), but the same fix will need to be implemented into GDM, SDDM, etc, if there is no encouraged standard for how to start X or Wayland with some form of failsafe function for child processes failing.

    EDIT: Maybe I let loose with my rant before fully reading and deciding if your anecdote was really 1:1 with the scenario I'm describing

    Leave a comment:


  • Weasel
    replied
    Originally posted by archkde View Post
    It's true that Linux kernel panics don't happen frequently, but I haven't seen a BSOD for a long time either.
    My neighbor's Windows 11 network driver causes a BSOD once a week. Super fun.

    Not saying Linux is immune. I've personally had my shares of stuff breaking with kernel updates, but at least it was broke almost completely, so I easily reverted until fixed.

    Leave a comment:


  • mathieu.cossette
    replied
    Originally posted by fallingcats View Post

    Only if you're not running a desktop environment while the panic is happening. AFAIK The linux kernel never had a way to switch to a tty in case of panic.
    I still remember my first days on a linux kernel, nothing happens when it freeze!

    Leave a comment:


  • nerdopolis
    replied
    Originally posted by ssokolow View Post

    Hmm. I wonder if I was thinking of something else or if that was just something they aspired to for a later version.
    They were talking about the possibility of QR encoded crash messages years ago, I think there are older articles about it, but I don't think anything came of that.

    Leave a comment:


  • ssokolow
    replied
    Originally posted by nerdopolis View Post

    The color is actually customizable, it defaults to 0x00000000 now though https://cgit.freedesktop.org/drm/drm...2c8fdfe0ff0a2a so you could compile a kernel with CONFIG_DRM_PANIC_BACKGROUND_COLOR=0x000080 if you so choose. lol

    But there is no QR code encoding in this iteration as there is no kernel mode qr encoding as of now in Linux yet AFAIK
    Hmm. I wonder if I was thinking of something else or if that was just something they aspired to for a later version.

    Leave a comment:


  • lowflyer
    replied
    It's time to abandon ship

    Leave a comment:


  • nerdopolis
    replied
    Originally posted by ssokolow View Post

    I believe they're taking inspiration from Haiku's QR Code-enabled kernel crash screen.

    ...though, even if they do make it blue, it'd still not be a Microsoft invention. Windows copied that color scheme from the firmware (i.e. BIOS/UEFI counterpart) for a MIPS box that Windows NT support was being worked on for at the time.
    The color is actually customizable, it defaults to 0x00000000 now though https://cgit.freedesktop.org/drm/drm...2c8fdfe0ff0a2a so you could compile a kernel with CONFIG_DRM_PANIC_BACKGROUND_COLOR=0x000080 if you so choose. lol

    But there is no QR code encoding in this iteration as there is no kernel mode qr encoding as of now in Linux yet AFAIK
    Last edited by nerdopolis; 19 April 2024, 11:23 PM.

    Leave a comment:


  • ssokolow
    replied
    Originally posted by tildearrow View Post
    Great, but please don't copy Windows.

    I am legitimately hoping the mentions of BSoD in the article are just clickbait...
    I believe they're taking inspiration from Haiku's QR Code-enabled kernel crash screen.

    ...though, even if they do make it blue, it'd still not be a Microsoft invention. Windows copied that color scheme from the firmware (i.e. BIOS/UEFI counterpart) for a MIPS box that Windows NT support was being worked on for at the time.

    Leave a comment:


  • spicfoo
    replied
    Originally posted by duby229 View Post
    So yeah, I just spent half the day trying to replicate this and you guys are absolutely right. I couldn't believe it but it's true. And it goes back years actually. I'm finding it incredible that a hang to a black screen is even possible.

    EDIT: I've always told people that one of the great things about Linux was that it couldn't just freeze with no output, but that's exactly what this does.... I'm glad this is getting resolved but somehow I feel let down.
    I generally avoid making statements along the lines of Linux will always do this or never do that without a direct expert source. There are thousands of configuration knobs for the kernel alone and the kernel developers themselves have never said that the kernel will never freeze. No a single mainstream OS will make that promise. If you trigger a bug before a subsystem responsible for showing the output is initialized, it is always possible to freeze. It is just atypical.

    Leave a comment:


  • duby229
    replied
    So yeah, I just spent half the day trying to replicate this and you guys are absolutely right. I couldn't believe it but it's true. And it goes back years actually. I'm finding it incredible that a hang to a black screen is even possible.

    EDIT: I've always told people that one of the great things about Linux was that it couldn't just freeze with no output, but that's exactly what this does.... I'm glad this is getting resolved but somehow I feel let down.
    Last edited by duby229; 19 April 2024, 08:28 PM.

    Leave a comment:

Working...
X