After a failed "incomplete" upgrade of Tiger over OS X 10.2.8 on my dual G4 500MHz Mac, I encountered a recurring kernel panic that appears to be identical to a bug that was supposedly fixed between 10.2.4 and 10.2.6, involving a conflict with Norton Utilities 2.0. (Three minutes after start-up the OS X 10.2+ kernel panic message window appears: "You need to restart your computer. Hold down the power button...")
While searching for a fix I've been seeing numerous posts from people with Tiger kernel panics who are madly/desperately ripping out memory and hardware but...
Contrary to extensive web-advice my problem had nothing to do with USB or memory or any other third-party hardware. I found this 2003 posting at MacNN:
http://www.macnn.com/feature.php?id=377
Subject: Do not install Mac OS X 10.2.4 if you have Norton Systemworks 2.0 / Utilities 7.0.x installed.
I removed everything from my boot drive with symantec, norton or NUM in its name and the kernel panics are gone and my 10.2.8 works properly again, albeit without Norton anything... I will wait and install Tiger on a brand new hard-drive... Below is the full text of the panic log entry: the major difference[?] I see from the 2003 message is that my log says (flags 0x60106220) instead of (flags 0x60006220)
Not to confuse matters, but when I attempted to install full Tiger on another [system-free] internal drive on my dual G4, THAT installation got hung up where it refused to recognize my keyboard, an Ortek extended EKB0880 v.1.2)... That installation seems to have worked but its another good reason to wait, I think...
My panic.log:
************************************************************
Mon May 9 17:30:08 2005
panic(cpu 1): getnewbuf: bp @ 0x1c402334 is LOCKED! (flags 0x60106220)
Latest stack backtrace for cpu 1:
Backtrace:
0x000857F4 0x00085C24 0x000287B4 0x000AA2CC 0x000A949C 0x000A8644 0x000A871C 0x1C00B7F8
0x000BE97C 0x001ED7C8 0x001ED610 0x0020FF8C 0x00092950 0x00300050
Kernel loadable modules in backtrace (with dependencies):
com.symantec.kext.symfs(7.0.2)@0x1c008000
dependency: com.symantec.kext.symdc(1.3)@0x1c39b000
Proceeding back via exception chain:
Exception state (sv=0x1C139C80)
PC=0x90000D6C; MSR=0x0000D030; DAR=0x1C09D6F1; DSISR=0x42000000; LR=0x00023FA8; R1=0xBFFFF680; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 6.8:
Wed Sep 10 15:20:55 PDT 2003; root:xnu/xnu-344.49.obj~2/RELEASE_PPC
While searching for a fix I've been seeing numerous posts from people with Tiger kernel panics who are madly/desperately ripping out memory and hardware but...
Contrary to extensive web-advice my problem had nothing to do with USB or memory or any other third-party hardware. I found this 2003 posting at MacNN:
http://www.macnn.com/feature.php?id=377
Subject: Do not install Mac OS X 10.2.4 if you have Norton Systemworks 2.0 / Utilities 7.0.x installed.
I removed everything from my boot drive with symantec, norton or NUM in its name and the kernel panics are gone and my 10.2.8 works properly again, albeit without Norton anything... I will wait and install Tiger on a brand new hard-drive... Below is the full text of the panic log entry: the major difference[?] I see from the 2003 message is that my log says (flags 0x60106220) instead of (flags 0x60006220)
Not to confuse matters, but when I attempted to install full Tiger on another [system-free] internal drive on my dual G4, THAT installation got hung up where it refused to recognize my keyboard, an Ortek extended EKB0880 v.1.2)... That installation seems to have worked but its another good reason to wait, I think...
My panic.log:
************************************************************
Mon May 9 17:30:08 2005
panic(cpu 1): getnewbuf: bp @ 0x1c402334 is LOCKED! (flags 0x60106220)
Latest stack backtrace for cpu 1:
Backtrace:
0x000857F4 0x00085C24 0x000287B4 0x000AA2CC 0x000A949C 0x000A8644 0x000A871C 0x1C00B7F8
0x000BE97C 0x001ED7C8 0x001ED610 0x0020FF8C 0x00092950 0x00300050
Kernel loadable modules in backtrace (with dependencies):
com.symantec.kext.symfs(7.0.2)@0x1c008000
dependency: com.symantec.kext.symdc(1.3)@0x1c39b000
Proceeding back via exception chain:
Exception state (sv=0x1C139C80)
PC=0x90000D6C; MSR=0x0000D030; DAR=0x1C09D6F1; DSISR=0x42000000; LR=0x00023FA8; R1=0xBFFFF680; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 6.8:
Wed Sep 10 15:20:55 PDT 2003; root:xnu/xnu-344.49.obj~2/RELEASE_PPC
