Trouble with unexpected Kernel Panics |
June, 05, 2003 2:16 AM |
tempest |
Hello: I ran across a situation of unexpected kernel panics under 10.2.6, and maybe 10.2.5 as well. Usually, the panics would occur when I type my password to disable the screensaver, or whenever I launch Safari, just right after the location bar's blue status indicator turns off. It is a doozy of a panic, too--always ending up with a double-panic and always stopping in the mesh SCSI kernel extension the second time. At first I thought it was because of Safari 1.0b2v74 (cache files, etc), but then it soon happened again a while after I downgraded to v73. Of course it was also like clockwork. Everything is fine except for the once-in-a-while panic when I disable the screensaver; however with Safari, whenever I launch it, it would panic. On a hunch, I booted into single-user mode and ran fsck to see if the disk was a problem. Since I have journaling turned on, I didn't have to worry about fsck'ing the disk during unexpected crashes; but when I ran fsck -f (-f is required for journaled systems), it ended with a segmentation violation. Not good. Reboot into OS 9 and Disk First Aid would crash into Macsbug. Also not good. Add to the fact that the Sonnet G4 would go bonkers (black screen of death) whenever I reboot without using XPF. Solution with the G4 is to attach monitor to built-in display for "recovery." Finally, I used Norton under OS 9 and there were around a handful of errors in the directory structure--told Norton to fix them. Reran Disk First Aid and was given a clean bill of health; booted into OS X single-user mode and reran fsck and things look good again. Now Safari works, and I'm hopeful the random screensaver panics are a thing of the past. My experience tells me it's probably a good idea to run fsck to check a disk after an unexpected crash, especially if journaling is enabled. |
. |
RE: Trouble with unexpected Kernel Panics |
June, 07, 2003 8:56 PM |
mjoecups358 |
. |
I wasn't comfortable with the way the popped up, and I had a feeling they were stalling or crashing the computer at some points... I'm pretty sure I never had them in some prior versions of OSX... Anyhow that old legacy bus isn't too useful IMHO, although it sure is nice for older drives, and in my PowerWave I have a slot loading DVD drive hooked up to the internal bus, and that seems Okie dokie... WHo Knows? At some point these systems are a little too close to the edge of the abyss. Usually I have figured a way to pull back from the brink, by tweaking clock/ bus speeds and juggling devices. Marty |
. |
RE: Trouble with unexpected Kernel Panics |
June, 07, 2003 3:51 PM |
tempest |
. |
I think the Mesh arbitrate/reselect messages are normal because the error codes are 0. Probably a race/timing condition of some sort. |
. |
RE: Trouble with unexpected Kernel Panics |
June, 07, 2003 2:24 AM |
mjoecups358 |
. |
I have given up on the built in fast SCSI bus due to MESH Arbitrate/Reselect errors, which I couldn't seem to resolve 100%. I am using an Acard for IDE and a ATTO for ultra2 scsi. I do use the external built in SCSI 5Mbits/sec for my scanner too. Marty |
. |
RE: Trouble with unexpected Kernel Panics |
June, 05, 2003 3:30 PM |
tempest |
. |
Journaling would only reissue the writes required to reach the last checkpoint just prior to the crash, but would not do anything about checking the disk structures' integrity. |
. |
RE: Trouble with unexpected Kernel Panics |
June, 05, 2003 7:27 AM |
gregoryy |
. |
...or Safe Boot? and why would JFS not fix and repair on its own? or why doesn't Apple have a "dirty filesystem check" to trigger repairs automatically? I'd say you were lucky with Norton. I'd never run that risk and use it first. After Disk Warrior has worked and been safe, can't say the same for Mr. Disk Doctor. Never saved my bacon, but fried it a few! |
|
|