garbage screen of death
This has happened three times now, but this time I have a photo. Booting from the Jaguar boot CD and examining the disk reveals no problems. Reinstalling the system on the same cd will produce the same thing. And, even though I have a perfectly good system on another partition, the Apple boot cd for jaguar insists on making me install the system again because you cannot select a system to boot from from preferences on the cd.
Damned annoying, it is. Just a poipnt. There was no haxies or other third party software on the system. Nor did I have any OS9 software installed. Anyone else have this screen?
Comments
Unresolved kernel trap(cpu 0): 0x600 - Alignment DAR=0x00746f92 PC=0x0008d9ec
Latest crash info for cpu 0:
Exception state (sv=0x17ED1280)
PC=0x0008D9EC; MSR=0x00001030; DAR=0x00746F92; DSISR=0x00000080; LR=0x0002EB48; R1=0x10493B90; XCP=0x00000018 (0x600 - Alignment)
Backtrace:
0x00000001 0x0008D5DC 0x1794C33C 0x1794C734 0x1794BC50 0x1794B7F4 0x1794C2D0 0x002260B8
0x0003EE98 0x0003EDA0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleSCCSerial(1.2.3)@0x17944000
dependency: com.apple.iokit.IOSerialFamily(6.0.1d19)@0x178df00 0
Proceeding back via exception chain:
Exception state (sv=0x17ED1280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x01814000)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 6.0:
Sat Jul 27 13:18:52 PDT 2002; root:xnu/xnu-344.obj~1/RELEASE_PPC
panic(cpu 0): 0x600 - Alignment
Latest stack backtrace for cpu 0:
Backtrace:
0x0008593C 0x00085D6C 0x00028B8C 0x0008F648 0x000926B8
Proceeding back via exception chain:
Exception state (sv=0x17ED1280)
PC=0x0008D9EC; MSR=0x00001030; DAR=0x00746F92; DSISR=0x00000080; LR=0x0002EB48; R1=0x10493B90; XCP=0x00000018 (0x600 - Alignment)
Backtrace:
0x00000001 0x0008D5DC 0x1794C33C 0x1794C734 0x1794BC50 0x1794B7F4 0x1794C2D0 0x002260B8
0x0003EE98 0x0003EDA0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleSCCSerial(1.2.3)@0x17944000
dependency: com.apple.iokit.IOSerialFamily(6.0.1d19)@0x178df00 0
Exception state (sv=0x01814000)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 6.0:
Sat Jul 27 13:18:52 PDT 2002; root:xnu/xnu-344.obj~1/RELEASE_PPC
<a href="http://docs.info.apple.com/article.html?artnum=106227"; target="_blank">Mac OS X: What Is a Kernel Panic?</a>
A kernel panic is a type of error that occurs when the core (kernel) of an operating system receives an instruction in an unexpected format, or that it fails to handle properly...
<a href="http://docs.info.apple.com/article.html?artnum=106228"; target="_blank">Mac OS X: How to Log a Kernel Panic</a>
By recording the correct information during a kernel panic, you may provide useful feedback to Apple...
[ 11-26-2002: Message edited by: Brad ]</p>
I also the advice of some crawlingparanoia and tried to update the firmware. It said it copuldn't be updated with his version of software (Jaguar) The firmware thingie was also a classic program, which meant trying to find OS 9, installing it and restarting... yadda yadda yadda...
It's just so frustrating... and I just know that there are going to be some serious ramifications with newbies getting new machines, with gobs of hard drive space, and a serious problem like this cropping up to ruin their day. I only lose 14-20G of stuff, most of which is recorded on CD's if the absolute worst happens. With one of the new machines, it can be up to 40 or 80, or more.
I shudder to think of what would happen.
To think most of the hassle of fixing something like this could have been offset if only I was able to set a startup device from the boot cd's, instead of having to install a new system somewhere else.
It is no big deal. I am trying not to run any classic programs for the time being or any haxies on the system. I haven't had any problems. I will try what you suggested, honest...
I appreciate your input, I really do. Is there a way to check the firmware without using the update? I know I updated it a while ago, but I can't remember when. System Profiler didn't seem to generate the firmware as part of its data collection.
The system appears stable. Some ninny I lent it to set the speed to 375mhz, and I have since turned on journalling. No haxies and we wait and see...
Thanks to everyone for the constructive technical assistance. I shall keep you posted.