 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / General / Hardware / November 2007"You must restart your computer" dialog box
Recently I was in the midst of typing some information on a web page when a gray wash appeared on the screen and I got a dialog box in four languages saying that I must restart the computer. The computer was unresponsive after the dialog showed up. I shut it down by holding the power button for a few seconds, and then restarted. Things seem fine so far. Does anyone know what might have caused this? The dialog contained no error numbers, and no identification as to whether it was from the OS (I'm running 10.3.9 on a dual 2GHz PowerPC G5), or some other program. Thanks for any help. > Recently I was in the midst of typing some information on a web page > when a gray wash appeared on the screen and I got a dialog box in four > languages saying that I must restart the computer. The computer was > unresponsive after the dialog showed up. That's a system crash.  SignatureWhile its true that "you can't fix stupid", apparently you can package it up and sell it. -- fnorgby on TMBO >> Recently I was in the midst of typing some information on a web page >> when a gray wash appeared on the screen and I got a dialog box in four >> languages saying that I must restart the computer. The computer was >> unresponsive after the dialog showed up. > > That's a system crash. Wow, two new dramatic system behaviours uncovered in c.s.m.h.m in the space of a few hours. Unheard of! Unless of course both of you failed to Google "You must restart your computer". It's a kernal panic folks, plain and simple. Covered many times since the dawn of OS X. To the OP: perhaps your interpretation as a "dialog box" lead you astray. A dialog box is something else indeed. Searching for info on a grey screen, or the error message you see would have lead you to a kernel panic, then hopefully to one of the better references, Apple's own KB article: <http://docs.info.apple.com/article.html?artnum=106227> The original Google search I suggested actually turns up a nice lead too: <http://forums.macosxhints.com/archive/index.php/t-37828.html> Signature*--------------------------------------------------------* | ^Nothing is foolproof to a sufficiently talented fool^ | | Heath Raftery, HRSoftWorks _\|/_ | *______________________________________m_('.')_m_________* > > That's a system crash. > > It's a kernal panic folks, plain and simple. Covered many times since > the dawn of OS X. What part of what you said conflicts with my simple explaination? SignatureWhile its true that "you can't fix stupid", apparently you can package it up and sell it. -- fnorgby on TMBO >> > That's a system crash. >> >> It's a kernal panic folks, plain and simple. Covered many times since >> the dawn of OS X. > > What part of what you said conflicts with my simple explaination? System crash != kernal panic. Ta-da. Signature*--------------------------------------------------------* | ^Nothing is foolproof to a sufficiently talented fool^ | | Heath Raftery, HRSoftWorks _\|/_ | *______________________________________m_('.')_m_________* > >> > That's a system crash. > >> [quoted text clipped - 4 lines] > > System crash != kernal panic. Ta-da. I've been a system programmer and system administrator on a variety of operating systems ranging from mainframes to microcomputers for 25 years, and in my experience they're essentially equivalent. A system crash is when the OS can't operate properly. If the kernel is able to detect this, it may be able to intercept it and reboot gracefully, which is what a panic is. But in either case the OS has failed, data may be lost, etc. SignatureBarry Margolin, barmar@alum.mit.edu Arlington, MA *** PLEASE post questions in newsgroups, not directly to me *** *** PLEASE don't copy me on replies, I'll read them in the group *** >> >> > That's a system crash. >> >> [quoted text clipped - 8 lines] > operating systems ranging from mainframes to microcomputers for 25 > years, and in my experience they're essentially equivalent. Interesting. Indeed, across the spectrum of OSs they are "essentially equivalent". But in your 25 years I'm sure you've grown to understand the importance of correct terminology. The behaviour the OP was describing is a kernal panic. It's essentially equivalent to a BSOD, or a system crash or a OS failure or a fatal system error or a system bomb or a computer freeze. But it's not, it's a kernal panic. I'm sure you'll agree, regardless of whether you share my fastidiousness over the correct label. I am pedantic about nomenclature because I'm well aware of the destructiveness of vague, loose or fluid technical terms. I'm sure you wouldn't appreciate a young whipper-snapper like me considering our computing experience to be on par because mainframes are "essentially equivalent" to iMacs. Okay, not a perfectly well- formed analogy, but I hope you get my point. Signature*--------------------------------------------------------* | ^Nothing is foolproof to a sufficiently talented fool^ | | Heath Raftery, HRSoftWorks _\|/_ | *______________________________________m_('.')_m_________* >>>>>> That's a system crash. >>>>> It's a kernal panic folks, plain and simple. Covered many times since [quoted text clipped - 21 lines] > are "essentially equivalent" to iMacs. Okay, not a perfectly well- > formed analogy, but I hope you get my point. Fastidious is one word for it. Dude, it's a /crash/. Arguing over the specific pedigree of the crash helps the OP about as much as the rest of this thread. And, yes: I've been in this business for many, many years, and *everyone* just calls it a "crash" unless pressed for details, or there is a need to expand upon the problem in a bug report. /Then/ you use the jargon you've learned to fill in as many details as you can. Ask yourself the question, "did the answer address the original query, and was the language used clear enough even for someone unfamiliar with OS internals?" I'm sorry, but "kernel panic" means nothing to my mom. "System crash", however, certainly does. At least remember to spell it right. There is a time to use specific jargon, and a time to generalize using words that most of your audience will get. Signatureclvrmnky <mailto:spamtrap@clevermonkey.org> Direct replies will be blacklisted. Replace "spamtrap" with my name to contact me directly. >>>>>>> That's a system crash. >>>>>> It's a kernal panic folks, plain and simple. Covered many times since [quoted text clipped - 26 lines] > Dude, it's a /crash/. Arguing over the specific pedigree of the crash > helps the OP about as much as the rest of this thread. Oh but that's one of my points precisely - if the OP were to search for more information on a "system crash" they'd be on a wild goose chase. Looking for more info on a kernel panic will lead them to much more useful sources. Alternatively if they were to describe the problem to a more technologically-inclined friend, calling it a kernel panic would save a great deal of ambiguity. By the way, this sub-thread is not necessarily for the OP! > And, yes: I've been in this business for many, many years, and > *everyone* just calls it a "crash" unless pressed for details, or there > is a need to expand upon the problem in a bug report. /Then/ you use > the jargon you've learned to fill in as many details as you can. Obviously *everyone* doesn't include me then :p or the author of Tech Note 106227 for that matter. > Ask yourself the question, "did the answer address the original query, > and was the language used clear enough even for someone unfamiliar with > OS internals?" I'm sorry, but "kernel panic" means nothing to my mom. > "System crash", however, certainly does. Apology accepted, I would be more concerned if your Mum did know what a kernel panic is. I think a reply that says "that's a system crash" is about as useful as "you have a buggered tendon". Both replies would be met with a request for more information and a solution. Calling it a "torn ACL" or something would give the person much greater ability to go further with the problem, regardless of whether they know what a torn ACL is. The knee is in pain whether you call it a peach or a plum, but only calling it an ACL will put you on the right path to answers and solutions. > At least remember to spell it right. Argh! I knew when I was writing it I was making a mistake, but it didn't click until I read Ars Technica's Leopard review last night. I was hoping to get in here this morning and make amends in time, but alas... > There is a time to use specific jargon, and a time to generalize using > words that most of your audience will get. Ah, this is comp.sys.mac.hardware.misc. I'm sure we can lend ourselves to a little precision! The OP now knows what a kernel panic is. I don't think that's a bad thing. Signature*--------------------------------------------------------* | ^Nothing is foolproof to a sufficiently talented fool^ | | Heath Raftery, HRSoftWorks _\|/_ | *______________________________________m_('.')_m_________* > >> >> > That's a system crash. > >> >> [quoted text clipped - 13 lines] > the importance of correct terminology. The behaviour the OP was > describing is a kernal panic. Yes, I understand the importance of correct terminology. But in this case, it's just a difference in jargon from different communities. For some reason the Unix folks didn't like the connotation of "crash", so they called it "panic". IBM mainframers called it "ABEND". They're all basically the same thing -- the OS gets so messed up that it has to reboot (or "IPL" in the IBM case). SignatureBarry Margolin, barmar@alum.mit.edu Arlington, MA *** PLEASE post questions in newsgroups, not directly to me *** *** PLEASE don't copy me on replies, I'll read them in the group *** > > What part of what you said conflicts with my simple explaination? > > System crash != kernal panic. Ta-da. I want to argue, but I can't. <sigh> SignatureWhile its true that "you can't fix stupid", apparently you can package it up and sell it. -- fnorgby on TMBO > >> Recently I was in the midst of typing some information on a web page > >> when a gray wash appeared on the screen and I got a dialog box in four [quoted text clipped - 24 lines] > > <http://forums.macosxhints.com/archive/index.php/t-37828.html> Well, thanks for the answer and the links, and thanks, I guess, for the gentle chiding. I did indeed search at Apple, but I had restarted the computer and had not written down the exact message. "You must restart your computer" doesn't find it, but "You need to restart your computer" does. My mistake for not noting the exact message. Thanks again. -aj |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.