Linux Crash Top 10 Images

I got a plenty of e-mails from microsofties pleading that I was to harsh on Windows, and should think about doing a top 10 Linux Crash post.  The reality is yes Linux can crash, although it tends to be harder to do as you tend to know exactly what you're doing when you install Linux.  Which is why this list is hilarious.  Some of the top 10 includes planes, and trains.  It was funny to see that most of the pictures are of airplanes. 

So next time your flying on your favorite airline, don't worry when you see Linux crash and reboot before your eyes.  It seems to be a common occurrence.  I have to say however, Linux has a million and one ways to "crash", and a lot of times it will just reboot, stop responding, stop working, and force you to reboot.  Therefore I am counting reboots that have to be done because the system is unusable as a crash.  At least Microsoft standardized most crashed requiring a reboot on the ugliest blue and white screen ever and called it the BSoD. lol.

 

1. A typical users computer that runs Linux.  Linux has definitely crashed here.
   
   
   
2. Linux crashes in an airliner.   This is great.  Windows I'm used to seeing crash, but Linux... Not a good sign. This was taken on an Air Algerie Airbus A330
   
   
   
3. More detailed close up of a Linux crash.
   
   
   
4. Turns out that a LOT of airplanes you fly these days use Linux! 
   
   
   
5. Linux Crash on a train running Centro's TV software
   
   
   
6. Another Linux crash on an airplane.  I love the retro carpet on seats lol.
     
   
7. A smart phone goes down hard with a Linux Kernel Panic.
   
   
   
8. Linux crash on a subway!
   
   
   
9. Nintendo DS Runs Linux!  This person must have been fooling around with a third party tool like EZ-Client.
     
   
   
10. Tim Horton's uses Linux!  I bet they were told it would never crash like Windows!  I'll have a large double double please! Thanks Colin for taking the picture! Check out his flickr image here.
    

 

Bonus Images

1. This guys is awesome.  If anyone knows where I can buy this shirt let me know!
   
    
2. A Linux Kernel Panic during a presentation at a Linux Rally Event!
   

 

Updated:  I wont delete the comments from the Linux posters (by the way I have 4 machines running SUSE Linux myself) as I find it hilarious how some people ruin it for everyone.  This is called "satire humor" people. Of course none of these are BSoD as there is not such thing in Linux.  However, if you get some bad hardware plugged into Linux, or put the average Joe that uses Windows in front of a Linux machine, the amount of hanging, crashes, kernel panics you will get will BLOW YOUR MIND.  All of these screens below do shoe rebooting in situations where a reboot should not have happened, aka, in a plane with hundreds of passengers seeing "engine" in the boot sequence.  End users don't know the difference. 

The entire purpose of this blog is "Real World" and in the "Real World" all of things above are crashes to people.  I can explain each one, but I won't as that is not the point.  The Linux users our there should just laugh and admit that the two operating systems are different, and applicable in different scenarios.  Some people are better at Basketball, some people are better at computers.  Some people are Olympic Gold Medallists in Hockey, but that same person might not even be able to swim.  Does that make one person better than the other? no.  Just different.  Will both people fail, and hopefully get back up after a failure?  Of course!  Nobody is invincible!  And no piece of software is "perfect".  There is room for both people in the world, as there is room for two different operating systems.   However I do feel that this "elitist" attitude is definitely hurting the adoption of Linux, instead of helping.  It's to bad really.

Comments

[cyber_rigger]

3. A segmentation fault is not an OS crash.

[buddy]

Successfully booting Linux on a Nintendo DS isn't a crash, either. The DS is waiting at a login: prompt--it hasn't crashed.

[dc]

the tim hortons one isn't a crash either, it's a reboot...

and #7 looks suspiciously unlike linux.

[gangals]

For one of those linux shirsts:

http://www.instantattitudes.com/shirts/t021.html

[deshi]

Your rank number 9 is not a crash at all, why is it on the list? It's the standard login promt of DSLinux.

[Deus]

n00b, hang your head in shame for not recognising a login promt on number nine!

[Bullshit]

Of the 10 images, 7 are bootups, and are not indicative of a crash. Two of the remaining 3 are problems of one sort, but likely recoverable, and of all the 10 images, but one appears to be a legitimate crash.

[Chris C.]

#7 isn't linux. It's NT.

[Zydeco]

How strange, some windows users associate text consoles with crashes

Are you sure that phone is running linux and not some windows NT?

(3) If a segmentation fault halts the boot process, I'd say its a crash.

[Logic]

I have seen number 2 with a BSOD as well. Smells like photoshop!!

[Keith]

Most of the airlines that have movie on demand run a linux backend.

Nearly every flight i've taken transalantic has had a crash of some sort. Usually one or two of the terminals don't work so they just reboot the whole system.

[NT4BSOD]

#7 is an NT4 crash.

2nd line says: *** STOP: CODE (address, address, address, address).

Following is debug messages that were removed from the NT5 and later kernels.

[MYLAR]

YOU ARE A FUCKING IDIOT. GO NOW AND DIE

[DiScDuCe]

NONE OF THESE ARE CRASHES!

[netcrusher88]

Nos. 2, 4, 5, 6, 8, 9, and 10 do not show any kind of crash. Those are normal messages. Note a couple of them are too blurry to read, so they might even be BSD or even OSX in diagnostics mode.

#1 looks like SVGAlib crashed, implying bad third-party software, but that's not what a kernel panic (linux itself crashing) looks like.

#3 again, looks like some third-party software crashed. Linux is doing exactly what it ought to, prompting to launch a recovery ("diagnostics") console

#7 isn't even Linux. That's what Windows looks like when it crashes, my friend.

As for those listed at the beginning of this comment...

#9 and #10 are perfectly normal. That's what DS Linux looks like after a successful boot, and #10 shows LILO saying it successfully loaded the kernel.

# 2, 4, 5, 6 are too blurry to read. They appear to be normal kernel messages during boot. I can't even confirm whether 5 is Linux.

#7 displays an inability to access the drive it's configured to access. Either bad configuration - which is user error - or hardware problems, which is not a problem. Either way, it does not show a single fatal error - the picture shows a successful boot.

The bonus crash image looks like some kid was trying to demo his software and it segfaulted. His fault (bad code), not a Linux crash.

As for the t-shirt... is this meant to be a joke, then?

[netcrusher88]

> #7 displays an inability to access the drive it's configured to access.

Oops, i meant #8 ;)

[Ebola]

Wow, looks like someone did a lot of research!

[Dave]

double you tea eff is linux? is that the new microsoft office product for vista?

[Churn-o-matic]

Miguel - do you think Windows has crashed when a DOS window is displayed full screen? You seem to be from the touchy-feely world where anything other than idiot interface on the screen must mean severe trouble.

This is so sad it is laughable.

[DJ]

Dude ;
Go learn a little about linux before you write this kind of CRAP. Most of this screens are simple bootups,on the airliners this happens every time they SHUTDOWN THE PLANE'S POWER, rebooting the consoles... and as it was said before #7 is indeed NT and #9 is just a login screen....

Shame on you Dude...

[Tek]

I like satyre. :)

[Somebody]

Sheesh, it looks like some of the commenters need to grow up. Maybe some of the screens were misidentified -- so what? No need to get your panties in a knot! It sort of makes it embarrassing for the rest of us who use Linux -- we don't want to be identified with losers who freak out and post the same thing over seven times, or curse up and down whenever somebody says our OS isn't perfect.

And read the d*mn commentary before you post complaining that such and such is only a login screen:

"Therefore I am counting reboots that have to be done because the system is unusable as a crash."

[Jack9]

I love the people saying it's 3rd party vendors crashing...like the video driver. I'm sorry, without the video, the OS is useless, so it's integral. When the video driver goes down, shouldn't linux encapsulate the failure, OH WAIT IT CANT! Good try though. You can't say the OS is uncrashable if it becomes unusable through how the OS works.

[dustin]

From reading the comments here, it sounds like Linux crashing is a myth. Of course, how could a linux user admit to a crash after all the windows bashing?

I installed Linux for the first time 10 years ago, and can say that I could keep the Linux machine up without a crash for slightly longer than win 95 and 98. Once 2000 came out, the Linux box was far less stable than windows. My windows xp machine has been on for a year without a reboot. Thanks to Win 95 and 98, it will always be assumed that windows is less stable.

[Riskable]

Umm, "Somebody" wrote,

"I love the people saying it's 3rd party vendors crashing...like the video driver. I'm sorry, without the video, the OS is useless, so it's integral. When the video driver goes down, shouldn't linux encapsulate the failure, OH WAIT IT CANT! Good try though. You can't say the OS is uncrashable if it becomes unusable through how the OS works."

Two things to note:

1) If you have no idea what you're talking about (which it is clear you don't), best not to comment.

2) SVGALib isn't a 3rd party video driver. It is an open-source library used to run graphics on a console (i.e. without a real X server). It is often used in embedded systems with limited amounts of memory.

Since you're referring to #3, (the SVGALib segfault) it is just an application crash. Just as if Microsoft Word crashed on a Windows system, except that this system isn't configured to have a GUI (to save resources, wish Windows could do this) so instead of dropping back to the desktop, Linux dropped back to the console. Precisely what it was supposed to do.

Also, #3 is probably a very old picture. I can see in the image that one of the library paths indicates Red Hat Server 7.3 (aka "Valhalla") which was released in May of 2002.

As for the rest of the pictures, none of them look like a kernel panic (except for maybe bonus image #2). A typical kernel panic literally says, "kernel panic" with a whole bunch of useful information regarding what the kernel was doing when it panicked. For an example, see:

http://en.wikipedia.org/wiki/Kernel_panic

With the exception of #1 and #7, all of these images are merely pictures of the kernel boot messages (what you'd see if you didn't have a framebuffer console enabled with a pretty picture). Regarding those two I mentioned:

#1. This could be _anything_. It could be a Mac, a Windows box, DOS, some old Unix machine, or even an Apple IIgs (in fact, that is what first came to mind when I saw the pic). If it is a linux machine, it is most likely a corrupted console framebuffer. In all likelyhood, if you were seeing this on your screen after booting up Linux you have set a bad vga mode for your terminal (and forced it down Linux throat since it normally doesn't let you choose bad modes without doing as much). Regardless, it isn't indicative of a crash. Linux is probably humming along in the background doing everything it is supposed to. You could probably even login via ssh and reset your console to something basic and resume normal operations =).

#7, obviously an old-school NT kernel dump. Not Linux.

-Riskable
http://riskable.com
"I have a license to kill -9"