173
Panic "Screen of Death" To Gain Monochrome Fat Tux Logo In Linux 6.11
(www.phoronix.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Jun 2024
173 points (97.8% liked)
Linux
47345 readers
1330 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
This is making me realize that I have never encountered this equivalent of a blue screen of death on Linux.
It's very new. Previously the system would just drop to a console with a message saying "Kernel panic: not syncing: [reason]" and a whole bunch of debug info.
But still, on a well-maintained system, that pretty much never happens. Mainly because Linux is significantly more resilient to faults in device drivers than Windows.
Begs the question what's the point in all of this? In 20 or so years of using Linux (usually maintaining multiple systems at once) I've had a kernel panic maybe about 4 times for different reasons, and on those occasions the console debug info was fine. I don't really understand the excitement around making error messages look more like Windows. It can't be around being more newbie friendly since if you're having kernel panics you probably need to be an expert or have expert advice anyway.
funy pengin
I guess it will make developers who develop the kernel and its components go "hehe fat penguin anyway let's continue debugging this mess"
Running Linux on computers with Nvidia hardware proves that Linux and Windows both have their problems dealing with device drivers. Linux' benefit is that is has higher standards because the kernel devs need to sign off on driver, but that has downsides of turning away potential driver developers (as getting your code into Linux is a quite a complex thing just on its own). Linux also doesn't have many drivers in general it seems, unless your device has some kind of generic fallback that disables any special features.
My kernel panics generally don't display anything, the display just freezes and I need to force reboot the computer.
Linux is monolithic so it breaks when a kernel module fails. It can sometimes recover but sometimes the system is in such a bad state a panic is triggered to protect against further issues.
even on a less well-maintained system it's probably not going to be the kernel having a freakout, the kernel is going to be just fine while something else shits itself (probably graphics drivers on a desktop tbh, my vega 10 loves to vomit onto the screen and pass out)