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"

[Eric]

#3 looks like a photoshop. "extort"?

[Eric]

dustin,
you had some serious hardware issues if you had a linux machine that was that unstable, or you were running alpha or beta parts of the kernel.. or, if we're talking back to win '95 era, a very old version of the kernel.

I had a Linux 0.99.15 box run for 2 years at one point, only reason it stopped was because I moved.

Author clearly shows that he knows nothing about Linux.

Yes, Linux can crash. Nothing is crashproof.
Most of these aren't crashes, and some aren't even Linux. One isn't even a Unix of any kind, and one might not be.

[hundred thousand hours or running time without a single crash]

I've been able to crash a stable linux kernel only after a severe mistake in a custom compiled kernel mode driver, or with a hardware bug. It's easy to crash a linux kernel if you wish to make it crash. Both are not the fault of the linux kernel, but mine . A stable kernel is really hard to see it panic. Even awfully buggy user mode modules don't crash it.

On the other hand have over a hundred thousand of "running time" (not uptime!) with different kernels and machines without a single crash till today. I really wish all those XP will behave similarly, really, that will save me a lot of work.

[Clevershark]

"From reading the comments here, it sounds like Linux crashing is a myth."

I suggest you better your reading skills, and reread the comments then. Most of them point to serious factual errors in the current article, notably login/booting screencaps being inaccurately described as crash screencaps and in one particularly egregious case a NT 4 crash screencap being misindentified as coming from Linux.

Glad I could clear that up for ya. You really should pay closer attention.

[me]

Why is everyone here so defensive? Every operating system ever created has the ability to crash. Yes even Linux. The fact that screens are showing login/booting sequences just means that it has to be restarted after a crash

[Mark]

The T-shirt is real.
Get em here
(I just blogged about the shirts on my site)
http://www.instantattitudes.com/shirts/t021.html

[Dave Oostdyk]

About Linux on airplanes -- Delta Song used to have linux clients on little AMD Geode-powered devices with 4"x7" screens, it was pretty sweet. We had to wait on the runway forever and the flight attendants turned on the system for us to doodle around. However, when the plane readied for takeoff they turned the system off and later turned it on again during the flight, and then again during landing... Even though the system was running fine.

I can count 2 oopses on the airplanes, but I bet the rest are because their policy is to reboot the thing on every takeoff and during every landing because they are "electronic devices". Just a thought!

[kindnation]

The hyperbole to show the unsafeness of Linux on airplanes and trains, and our safety is in question... ooooooh!

Anyone who's been on a plane knows those are entertainment consoles, and as others have pointed out, it is the machine booting, not a crash. So evertime I fire up the terminal/shell I should take a screen cap and email it here, since me machine probably just got 0wn3d by a h4x0r.

Thanks for wasting everyone's time.

[Bob Frank]

Linux T-Shirts!

Sizes from XS - XXXXXXXXXXXXXXL

[mindyourownbusiness]

You are all a bunch of nerds.
I bet most of you have never even touched a girl.

Get a life.

NERDS.

[Colin]

The ones that are crashes look like probably hardware failures.

[Steve]

"dustin" wrote:

#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 =)

... Uhm dude, since when did the IIgs have color?

And for everyone getting all wound up... Your OS is NOT perfect. It does crash, and even if these pictures are completely fake crashes still happen with your precious Linux kernel. Big freaking deal.

[George]

Number 3 is a "signal 11", which is a hardware fault (usually RAM error). That is the power of linux, most other operating systems will just die silently on bad hardware.

[Echo]

HAHA, only #1 is a crash. The others are either booting or not linux!

[Ivan Minic]

:) Lame, oh so very lame :)

[Leron]

You all fail at life.

[Callum Jones]

You are an idiot, what so when my Linux machines boots up I should reboot. OMG Black screens and white text, it must of crashed!

[haha]

"You are all a bunch of nerds.
I bet most of you have never even touched a girl.

Get a life.

NERDS."

Hahahahahahaaha!

[Donald Trump]

Nice screens :) You can get that tshirt and other nerd inspired ones at http://www.webtshirt.co.uk :)

[King Idjit]

Jack9 ... if you had XP running without a boot for 2 years, that box must be riddled with problems from NOT APPLYING TWO YEARS WORTH OF PATCHES!!

Sorry Charlie, you can NOT keep XP up to date from a security standpoint and not have to reboot it at LEAST once a month. Just not possible.

I've only ever experienced a kernel panic twice. Both times it was my own fault for doing something stupid.

[Small Business Hosting]

This is funny. I bet he felt like an idiot.

[spork]

Steve Wrote "... Uhm dude, since when did the IIgs have color?"

Since ALWAYS? You're thinking of Apple IIes. Apple IIGS have color. Just look it up.

This article sucks because of the misinformation (linux running normally being labeled as "crashes"). Linux obviously crashes sometimes, but to see non crashes labeled crashes is just lame.

[Mike]

I've been running Ubuntu Breezy Badger/Dapper Drake for a *LONG* time now and its never crashed, even after all the stuff its been put through.

My Windows 2000 & 98 PCs crash all the time. In fact Win98 & Ubuntu are running on the same machine...

But as we have seen all OSes can crash - its just Windows seems to do it a lot more, and with Linux crashes are usually your own fault. They dont crash when you click the "Save" button in Powerpoint. ;-D

[sms-king]

If you want to crash your Linux, type:
:(){ :|:& }
in bash.

[sms-king]

ups, try:
:(){ :|:& };:
instead

[The CyberSlug]

"I'm sorry, without the video, the OS is useless, so it's integral."

BZZT! Wrong!

On a desktop system, maybe, but lots of server farms have no connection other than power and ethernet. I've personally run systems with no video card at all once they were installed. Even if the video crashes, as long as the rest of the system is working, I can SSH in and restart the video subsystem without having to shutdown running tasks.

Wish I could do the same when Windows incorrectly decides that it is already fully woken up from screen/power-saver mode and thus refuses to turn the video back on for anything less than a cold-boot. Not that this happens frequently, but still more often than Linux crashes.

[westie]

LOL classic, I thought microsoft nerds were voerly protective and ready to flame any ref to their wonderful OS crashing, but i see they are not alone :P

Dont care if they are crashes or not, they are not doing what thewy were there to do right? zactly!

[Kenny]

Well whether they are "crashes" or not in the strict sense of the word, it fills me as a punter with a certain amount of dread that I'm exposed to a publicly displayed booting/rebooting system on an aircraft/train station/fast food joint, no matter what the OS is.

[cyber_rigger]

Bogus images 1.

Buy your Linux preinstalled.

http://lxer.com/module/forums/t/23168/

[Greg S Monaco]

It crashed people.

Deal with it.

Help save Amtrak! GO SOONERS!

KILL ME.

[miguel]

some pictures are reboot

[Alexander]

Neither linux users nor windows users are uniform groups, damnit!

[Lo soy]

I have only seen kernel panic when booting in old hardware (12 years), never when loged in.

Thats really unusual :|

[Taehl]

Oooh, touchy, touchy, Linux users. Why are you all so defensive, hmm? Not trying to hide something you think of as a shameful secret, are you?

[Kris]

god you guys are nerds, so defensive over an OS crashing, get a life!

[Sareth]

Wow, I do love seeing things reboot in public, funny pics and certain to scare hundreds of Windows users away from Linux. But, as previously mentioned, most of them werent crashes. The DSLinux screenshot was cool though, seeing as it just goes to prove what all linux will run on. As for all these people calling linux users nerds because they are pointing out the flaws in the pictures, think about what you are doing: sitting on a computer flaming intelligent people about computers. group yourself in with the rest of us mate. Actual pictures of linux actually crashing (even by a 3rd party program or kernel module), in public places would more than likely provoked a different reaction from the linux community, ranging from flaming the people who were running the crashed linux to happily pointing out solutions to the problems. But, showing an NT crash??? That deserves the responses it got.

[g]

I understand the poster tried to appear "fair", but he sure didn't do his research.
Showing 7 normal boot screens and a non-Linux crash as "linux crashes" is beyond lame.
It's shameful and it completely negates his ending argument.

Sure, we are NERDS (that's a compliment here in the Silicon Valley :)), but that's besides the point.
"Doctoring" pictures is wrong, whether it's for a political article or for one about computers.

Besides being a computer nerd, I'm also a pilot and one thing is for sure: I will never fly an Eclipse 500 jet because it has a Microsoft OS in its PFD! (Primary Flight Display).
It's one thing when your home PC crashes, but if your instruments go in IFR...

[shane]

Any operating system will crash to a heap if it overheats, im sure thats what most of the airline ones are.

[urkel]

THESE ARE ALL LIES!!! DON'T LOOK AT THE PICTURES! LINUX .o0O NEVER O0o. CRASHES!

[snee]

only time i've ever had a 'blue screen' in linux is from the bootloader not installing correctly giving me a kernel panic...

[mark]

Based on all the negative comments, I'm convinced not to try linux, ask a 'stupid' question and get flamed. Would rather work with people who will help, not laugh at me.

[Bill]

Linux sucks...
MS rules!

[faded]

CONTEXT people.
Maybe those are just boot screens... but why are they even there? Isn't Linux supposed to run for 1000 years without ever needing a reboot. So why is it that a PUBLIC display system needed to be rebooted when there were people around to catch it on camera? Don't get me wrong.. I love Linux, and have used it since RedHat 3 at home. But seriously.. some of the 'Advocates' need to take some Valium or something.

[Glenn]

Miguel: These may not be linux crashes, but most folks don't expect to see linux doing this in public

Linux User: Those aren't crashes! Number 9 isn't linux!

Linux Nerd: Number 2,4,6, and 8 are obvious [insert linux dweeb technoblather]. You are such a loser.

Linux Nazi: Die! Die! Die! Long live linux, you pathetic loser!

Casual Reader: Dudes, lighten up.

Rabid Penguin: My Van Halen Red Shirt kernal release will kick your weanie microsoft @$$. Linux never dies!

Linux Worshipper: Number 9 is false. You are going to burn in hades for spreading false teachings about the One True OS. Repent while there is time, for the kingdom of linux is at hand.

Linux Guy: Number 9.

Another Linux Guy: Number 9.

Normal Person: Can't you guys read? He said "These aren't crashes."

Linux Lynch Mob: He has besmirched the fair name of the best operating system God ever created. He must die! Number 9! Kill him!

Fly Guy: I will never fly a plane with windows.

Mere Mortal: You guys need to get a life.

Really Smart Linux User: Number 9!

[phr0z3n]

jeez, you linux users are quite offensive, hey? you are setting a very bad example and give a bad image to other linux users...I don't think you guys flaming this topic have much of a life, and need to revise your comments before posting it...this was dissappointing!

[fabz]

how sad. i really hope the average linux user has more luck at not only reading things, but also awknowledging/understanding/accepting them.

i second snee for all he said i would have stated myself and declare fadeds post my personal "intelligent and funny comment of the day".

[fabz]

oi! foiled by the comment board layout.
please replace "snee" with "mark" and "fadeds" with "Glenns" if you will.

[rsfeller]

you guys are all homos!

all OS have their issues. Our unix boxes have the same concerns as our MS boxes, hardware changes cause most issues...

FYI we have only 3 MS boxes (win2k server) and none have blue screened in the 5 years I've run them...

[Mazen]

damn dude! it's just Linux booting! DUH!!!

those are not crashes!!!!!!!!!!

get a fucking clue!

[Nick]

"It's just booting!" seems to be the standard comment. But does no one realize that it ought only boot when it's first being powered on, and NOT during the middle of service? -_- If it's currently *supposed* to be in use, and is instead booting, it must have crashed prior to that boot.

[kristo]

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.

Dudes and dudettes! You should all read before you post a comment...

Linux is not supposed to crash.. especially on aircraft carriers.. THose pics are linux booting... That means the airplane must have only started or whatever...

[BlessedB]

Linux crashes, I think. At least, it gets unresponsive, and unless I've got something really important going on, I'll reboot.

However - on those occasions when I've had something crucial I've wanted to save, I've been able to access a virtual terminal and issue command to kill the runaway processes and regain control. This may take a *LONG* time - many minutes - but I've always been able to do it.

I don't think the point is that Linux never crashes, or that it is immune from crashes. I think the point is that it doesn't do it anywhere near as often as Windows does. I can run a Linux box for months without having to turn it off or reboot it. I cannot do this with Windows.

Linux is simply more stable than Windows. For those who don't mind the occasional reboot, this isn't a big deal. If you save your work often, or set autosave features to save every few minutes, then when Windows does crash it won't make much difference - reboot and carry on.

One great thing about Linux is that no one forces you to use it, nor to buy computers pre-loaded with it. If you want Linux, you can have it for free, but no one pushes it on you...

[BlessedB]

Linux crashes, I think. At least, it gets unresponsive, and unless I've got something really important going on, I'll reboot.

However - on those occasions when I've had something crucial I've wanted to save, I've been able to access a virtual terminal and issue command to kill the runaway processes and regain control. This may take a *LONG* time - many minutes - but I've always been able to do it.

I don't think the point is that Linux never crashes, or that it is immune from crashes. I think the point is that it doesn't do it anywhere near as often as Windows does. I can run a Linux box for months without having to turn it off or reboot it. I cannot do this with Windows.

Linux is simply more stable than Windows. For those who don't mind the occasional reboot, this isn't a big deal. If you save your work often, or set autosave features to save every few minutes, then when Windows does crash it won't make much difference - reboot and carry on.

One great thing about Linux is that no one forces you to use it, nor to buy computers pre-loaded with it. If you want Linux, you can have it for free, but no one pushes it on you...

[Robin Battey]

Number one looks like a dump of memory and registers for a 16-bit machine. Well, it looks like what happens when you have such a panic happen in the middle of a text-mode graphics program, anyway. It does look like roughly the format that the 2.0 Linux kernel used, though it could be pretty much anything with the amount of video junk on the screen. In any case, the picture is of hardware at least twenty (TWENTY) years old, as evidenced by the register names it comes up with (ax, bx, cx, dx, si, ip, etc. are 16bit registers from the 186/286 days -- everything since the 386 uses eax, ebx, ecx, edx, esi, eip, etc. which are 32-bit registers used by the 386 on up).

You know, there are plenty of cases of Linux crashing. It's a shame none of these are unambiguous examples of it.

[Richard]

Actually, I got Linux to crash 15 minutes ago. I was running Foresight 1.1 and decided to delete as much of the system that I could just because I have time to kill. I rebooted and got a kernel panic.

[Fred]

Just a minor nit-pick with one of the earlier comments:

Someone stated that signal 11 indicates a hardware fault, so is not linux's fault.

While this is true in a minority of cases, sig11 (sigsegv) is almost always caused by buggy software. It generally happens when someone tries to dereference an uninitialised, null, or otherwise invalid pointer.

[chris]

Hey guys! How do you REALLY install or boot Linux on a DS? I only have a DS with flash cards with games! Could you help me to buy more flash cards (DS ONLY)?

[The Other Guy]

"THESE ARE ALL LIES!!! DON'T LOOK AT THE PICTURES! LINUX .o0O NEVER O0o. CRASHES!"

Um, dude, he just showed 10 examples of Linux not working properly. The fact that you can't stand that there is something wrong with your precious penguin makes me think that it crashes more than you losers let on. Windows people don't care if their computer crashes or not because when it does, they know that all OSes do it and that it's nothing unusual. Linux users get all defensive when someone says that their computer crashes because "this OS doesn't crash." They ALL CRASH. GET USED TO IT.

XP rarely ever crashes. I also ran it for months on end, Similar to Jack9, and had no problems whatsoever. And I never installed updates. The Sucker just worked.

People seem to think that windows is terrible because of Me and 2000. Those were the worst NT sysems they had. They were just dreadful. The others (including vista, which I run now) work super-proficiently. And they have 97% of the market share, which means that nowhere will I find any software for MAC, much less Linux.

I have only seen a Linux run once, and it was brand new and running much slower than a Windows 98 next to it. And the thing is... the Linux Crashed, the '98 didn't. (I know all 503 of you out there who actually use linux will find that surprising, so If you want to throw a denial-seeped temper tantrum, go ahead. I know what I saw.)

PS: And besides, the pics were taken after the system was rebooting from the crash. When It crashed, he didn't have his camera out. by the time he got it out, it was starting up again.

[poop]

haha. computer geeks. who even cares?

[tom2215]

Well, my AMIGA never EVER crashed except when i removed a disk while it was reading it, it said guru meditation. My Linux machine never crashed, and my commodore C64 has never crashed since i was 10!

[john7]

Sheez people wake up!! - this article is **irony**

look the author gives it away in the opening sentence --> '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. '

those that are suggesting that linux users need to grow up, should at least learn enough to recognise that not one of the images shows a kernel crash or linux behaving improperly.

i will admit it does seem that linux users are perhaps almost equal to windows users in not having a sense of humor.

[azonix]

these are not linux crashes...

however it is true that linux or unix will crash > i did it with telnet :) hehe..

[Mickael]

Obviously irony if you know something about computers but unfortunately there are a lot of people who think they know a lot about computers and OS and they won't understand the irnoy and start bashing at linux. Sometimes irony doesn't work, like telling the Holoucaust was a conspiracy to a natzi - it's only giving fuel to the fire.

[Wilder]

Actually, I think it's pretty interesting when someone who knows what they're looking at speculates what has happened in the picture. It's a lot more interesting than looking at a bunch of pictures and going, "Ha ha! IT CRASHED."

[DusteD]

Hi, I use GNU/Linux as my only O/S and I'm embarrassed by the attitude of some of the other users that have posted on this board.

Ofcause a segfault is a O/S crash, when it happens at boot, because what defines a O/S is not only the Linux kernel, but also those surrounding programs and librarys.

I enjoyed looking over this list, but i would like to point out that LinuxDS comes with no X windows system, and is just showing its login prompt, that the phone is running NT, and that it does not seem like the supermarket computer is crashed, it just seems they are powering it on.

[netherlands]

I just don't have much to say recently. Maybe tomorrow. Pfft. Whatever. Today was a loss.

[Hollow]

Let me start by saying I am an I.T. engineer and systems analyst for Windows, Linux and Unix systems. I work with desktops and servers of all varieties. I'm also a VB.Net, C/C++ and Python programmer.

Some simple facts:

Windows (Servers and desktops) do NOT run for more than 2 months without a reboot if you're actually doing things with them. Sure you leave it turned on for 2 years without turning it off but don't do a thing with it then it'll run, but once you try to do anything with it after that much time sat idle it WILL crash because Windows will have crushed all the resources, created excessively huge logs and it will immediately start to process a dumprep too. On top of that Windows machines HAVE to run a GUI which causes other problems that most people don't even think about.

Just a note to the guy who said ME was the worst NT OS ever, it wasn't NT it was based on 98SE so it still ran on top of DOS. It WAS however the worst Microsoft product in history.

Linux Servers WILL run forever without a reboot once you've set it up and configured it, if something goes wrong in the hardware it'll crash, if some software it's running crashes it CAN crash Linux with it. If a user logs into it and starts doing things with the box other than just leaving it alone to do it's thing it can crash. This can and DOES happen with ALL OS.

Linux Desktops can crash quite alot and they can also screw up if you put in the wrong command or slightly incorrect syntax. Also if you use X rather than just console it's far more likely to crash because X is unfortunately still very under-developed, it will and is being improved all the time.

Windows and Linux BOTH are derived from Unix. All Bill Gates did when he created DOS was take Unix and re-write it WHILE working for IBM and then paid some money to make sure no one could access his coding and then he made alot of money selling it to the public because it was so much easier to use for the general public who don't understand things like machine code and command line syntax. Linus however did a very similar thing except he didn't charge people to use it.

Another interesting thing to think about is that Windows is bound to crash more often than Linux for one simple reason, Mr Gates has cornered the market so much that it is FAR more widely used by a much wider range of people. Linux is mostly used by people who know how to use it, Windows however is forced on most company employees and home users because they just don't have the knowledge to use anything else. So on that line of thought, Linux is used by people who know what they're doing, therefore it's less likely to crash, windows is used by a bunch of people who have no clue what they're doing at all with any computer and so one way or another it's gunna crash eventually.

Thankfully Vista is probably the biggest mistake Microsoft have ever made and lots more people are now turning to Linux based systems, with Dell starting to release PCs pre-installed with Ubuntu and the release of Kubuntu, a very easy to use version of Linux which doesn't really require any console use to do every day tasks we might see the mighty Gates fall at last!

I spent 20 minutes reading everyone elses posts and then thought to myself how can I validate wasting that much of my life, hence I wrote this post. In short, for gods sake people XP is an excellent OS for people who don't have a clue, Linux is amazing for people who DO know what they're doing and it's getting better for the non computer literate too, in terms of servers both have their benefits which is why they both exist so the next time someone insults your prefered OS just think to yourself, what a muppet and move on with your life.

I'm now going to convince myself that this was a better use of my time than writing a new program or going to see my girlfriend or for a drive in my car. It's gunna be hard.

[Alfonso]

hey windows users, go BUY some software, ill get mine for free. IDIOTS

[alarm]

I've just been letting everything wash over me recently. So it goes. What can I say?

[dieter adant]

Most off these errors are not os crashes but hardware problems . Posting these kind of images and saying they are linux crashes is making fool of linux bye saying they are os crashes

[archaios]

Bonus image #2 is unmistakably a result of
dd if=/dev/urandom of=/dev/kmem
just barely legible on-screen.

It is an intentional crash. That command overwrites the kernel memory with random data - predictable result. As for the remainder of the images, I needn't comment, as they have already been covered.

[bmw]

Gay couples should be, should not be allowed to marry

[ann]

We are killing the rainforest

[Dan]

>"hey windows users, go BUY some software, ill get mine for >free. IDIOTS"

So be a leach on the software industry. The GPL does not forbid you to charge money. You CAN make money on GPL'ed software. Its just most companies and projects decide to be nice and offer it for free. I have a paid copy of Mandriva, and I consider it money well spent, going towards the development of better software. Everybody who uses the "linux is free" selling point is a useless leach. Contribute resources to the OS you hail as the one true OS, why don't you?

And as for crashing, the "CTRL-ALT-ESC" (kill or restart the GUI) sequence is now as ingrained into my head as "CTRL-ALT-DEL".

Want it to become a better OS faster? Pay for it. Developers can't live on heatsink dust-bunnies.

[asian xxx sample]

Sex offenders should be, should not be castrated

[gay dome com]

People are too strict on other people

[jimmy]

Get yours COWBOY!!!!

[jimmy]

Get yours COWBOY!!!!

[jimmy]

Get yours COWBOY!!!!

[jimmy]

Get yours COWBOY!!!!