And they say mac's dont Crash: Part 2

MiniMan13

Well-known member
My friend was logging clips, and!
0405071922.jpg
 
That amazes me that that could happen. I know Mac OSX is UNIX based. UNIX doesn't usually kernel panic like that...
 
tommyinla said:
That amazes me that that could happen. I know Mac OSX is UNIX based. UNIX doesn't usually kernel panic like that...
Are you kidding? :)

Unix apps do core dumps of biblical proportions...
 
I am floored. I just got up this morning to see this cocker. In all my little time in this planet I've only seen 2 grey screens from a Unix based system. They were both caused by hardware failure on Sun Solaris boxes. If it were common then planes will be crashing into each other more often (Unix is standard for air traffic control systems), missiles will be launched accidentally (Unix is key for defence operations) , LSE (London Stock Exchange) will have more downtimes etc etc. And I'm willing to bet top £s that this site is hosted from a Unix like OS (most likely Linux)

Back to your crash, in my fascination I delved into google and it seems that this may have been common enough for Apple to even have a page for it on their site: http://docs.info.apple.com/article.html?artnum=106227

From your explanation though it seems like this happened during the read of an external device. Accessing an external device is done by the OS through communication with the device driver. As rough shot in the dark, I guess this happened like this; The driver must have said something like, "OSX, I have some data here. I guarantee that the data is not zero, meaningful, and it's X number of bytes." But when OSX tried to consume this data it wasn't exactly as indicated. Causing a null read, which throws an exception, which causes a kernel panic.

I'm actually curios to know what device was being accessed. Was it a DVX? Most unlikely because I always use mine without a glitch. So do many on this group. Did the Mac use it's own drivers or did your mate install his/her own? Has he/she used it with the Mac before? So many questions and so little time (I go on a long weekend break today)
 
Last edited:
Apple has come on strong over the past couple years with their marketing strategy of targeting "PC" which everyone knows means MS. Whatever backlash they get as a result, they've asked for by basically saying to the world that Apple computers are better, easier, and more well designed. The pendulum between the two has to swing back eventually.

Put all the marketing BS aside though for a minute and let's look at the two platforms. Both have their advantages and strengths. As an editor of video, graphic artist, web designer, and certified computer geek (Commodore Vic 20, Atari, Coleco Vision, C-64, Amiga 500, Amiga 1200, P60, P75, P100, P200, P2 266, etc etc etc....on and on building my own PCs for well over a decade) I can honestly say with a straight face that both are very useful to me every single day of my life and to be without either would be a huge blow.

Competition fuels the marketplace and drives quality. People who get militant about one or the other are only showing off their susceptibility to marketing.
 
ChuckS said:
Are you kidding? :)

Unix apps do core dumps of biblical proportions...

An application core dump though is much different (and more common) than the whole OS going t*ts up...(as happened here)

i have had not a single kernel panic with OS/X in about 3 years of owning it, but then also no BSOD on my windows laptop (which i hate with all my heart) in the last two years (except that it does randomly seem to shutdown overnight sometimes even though it is plugged in to the wall)
 
Guys, soo long as humans write programs and OS's, soner or later there gonna crash ;).

Erm as far as I understand Missile guidence systems use custom built embedded hardware (motsy ECL ICs), I would be surpised they would use anything like Unix OS (and related hardware). Now if you meant the F&C units then thats a different matter.

Anyways If you look carefully, its says Clearly "Corrupt Stack", so could also be an overflow errror.
 
I'm in the same boat as Ming. Systems crash... that's just about it. I was running Motion on a project just last week and my G5 started going haywire on render. It just happens.

You know? I'd have no problem with plunking down for a Mac Pro if it weren't so expensive. People are reporting flawless performance with Bootcamp 1.2, running processor intensive apps.

Even with the lack of support, I can't see myself turning one down if they were priced a bit better than they are now.

Shame.
 
Ive got a new line for this

Mac crashes are so rare, that when one does, someone has to take a pic and not only make 1 but 2 topics about it.
 
Are we still talking about this? Machines crash. If you want a computer that doesn't crash, buy one and don't turn it on.

I got into Macs because I was in advertising and didn't feel like juggling IRQ addresses (or whatever) all the time. Now I've invested a bunch of money in software that I'm not going to toss out. So there you go.
 
jobuc said:
I am floored. I just got up this morning to see this cocker. In all my little time in this planet I've only seen 2 grey screens from a Unix based system. They were both caused by hardware failure on Sun Solaris boxes. If it were common then planes will be crashing into each other more often (Unix is standard for air traffic control systems), missiles will be launched accidentally (Unix is key for defence operations) , LSE (London Stock Exchange) will have more downtimes etc etc. And I'm willing to bet top £s that this site is hosted from a Unix like OS (most likely Linux)

Back to your crash, in my fascination I delved into google and it seems that this may have been common enough for Apple to even have a page for it on their site: http://docs.info.apple.com/article.html?artnum=106227

From your explanation though it seems like this happened during the read of an external device. Accessing an external device is done by the OS through communication with the device driver. As rough shot in the dark, I guess this happened like this; The driver must have said something like, "OSX, I have some data here. I guarantee that the data is not zero, meaningful, and it's X number of bytes." But when OSX tried to consume this data it wasn't exactly as indicated. Causing a null read, which throws an exception, which causes a kernel panic.

I'm actually curios to know what device was being accessed. Was it a DVX? Most unlikely because I always use mine without a glitch. So do many on this group. Did the Mac use it's own drivers or did your mate install his/her own? Has he/she used it with the Mac before? So many questions and so little time (I go on a long weekend break today)
It was a Fullsized Panasonic Deck that i was capturing froim, and I didnt actually tell the owner what happend, i had to try and restart it (that failed) and then i had to flip it over and yank the battery out.

Oh and i know it is funny that i took a picture, but its only to clear the air that Mac's are Crash proof, All Systems crash/lockup once in awhile no matter the OS or hardware.
 
MiniMan13 said:
All Systems crash/lockup once in awhile no matter the OS or hardware.

ditto, its the same reason modern aircrafts have upto three redundant computer systems in case they crash, the theory being the possibilties of all four computer crashing being so extremly remote...
 
OT:

Micrsoft's Flight Simulator is indeed the best one. But I can't for the life of me figure out why it's so popular.

I mean, I get air combat flight sims. I play those (or used to) frequently. Big fan.

But why would anyone want to hop in the cockpit of a 747 and fly it above the clouds across the Pacific Ocean in real time? Just don't get it.
 
Back
Top