Add to Technorati Favorites

« Blue Screen of Death Top 10 | Main | Online Casino Gambling - Texas Holdem »

October 15, 2006

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341bf85553ef00d8347872b569e2

Listed below are links to weblogs that reference Linux Crash Top 10 Images:

» Lo que todos sabíamos, pero nadie se atrevió a menear: ¡Linux también se cae! from meneame.net
Así es señores, por mucho que le escueza a algún que otro talibán linuxero, aquí enlazo una recopilación de pantallazos de la muerte de Linux en diferentes sistemas, desde transporte público hasta una hamburguesería. Pero mirad el lado positivo, quizás... [Read More]

» Linux Crash - Top 10 images from ÎÜñ|‹ø\/\/ñ [ÐëÞrëçã†ëð]'s Blog
Yes, there are probably more BSOD screens on the net that anything else, but these Top 10 Linux crashes [Read More]

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"

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

Great Sites



Feeds

  • Add to Technorati Favorites

    Add Miguel Carrasco's Feedburner

    Add Miguel Carrasco to Google

    Subscribe to MyMSN

    Subscribe to MyYahoo!

    Subscribe to Bloglines

    Subscribe to Newsgator

    Subscribe to Feedster

    Subscribe to NewsIsFree