Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.4: Fix a kernel panic after Security Update 2005-009' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Fix a kernel panic after Security Update 2005-009
Authored by: mshmgi on Dec 06, '05 07:17:11AM

I experienced a kernel panic on one out of 6 Macs that I applied this update to. The affected machine is a b/w G3. I rebooted into single user mode (COM-S) and ran /sbin/fsck -fy; exit;

The machine worked flawlessly after that.



[ Reply to This | # ]
10.4: Fix a kernel panic after Security Update 2005-009
Authored by: alanford on Dec 18, '05 03:44:30PM

Ok...
I've jut had my complete system reinstalled ( Tigar 10.4 )....due the fact that I had so much crashes of kernal panic problem....
I wanted to see what might be a problem..... I now that some applications are not compatible with Mac OSX, and should be checked out.
I reinstalled my system I got wireless NET working too.. I'm using DI-525 and DWL G-122 USb Adapter,therefore I installed 2500 Wireless Utlility USB taken from this site.....
I got the crash again.....

Could anyone now are these compatible with Mac OS X Tigar 10.4???
I assume that is the driver causes all these problems, but I cannot find out...
Any solution???

Which one would be suitable for my system???


MY LOG CRASH:

Sun Dec 18 17:50:03 2005


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000000000022C PC=0x00000000000A4458
Latest crash info for cpu 0:
Exception state (sv=0x2E96F000)
PC=0x000A4458; MSR=0x00001030; DAR=0x0000022C; DSISR=0x40000000; LR=0x000A43A4; R1=0x0D81B780; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x0010CB70 0x000FA574 0x000E150C 0x000E10A0 0x000D2400
0x002A8174 0x000ABA30 0x0BE80002
Proceeding back via exception chain:
Exception state (sv=0x2E96F000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2F0CAC80)
PC=0x9001BF00; MSR=0x0200F030; DAR=0x178A6040; DSISR=0x40000000; LR=0x90B0ABE4; R1=0xBFFFC200; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.0.0: Sat Mar 26 14:15:22 PST 2005; root:xnu-792.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095564 0x00095A7C 0x00026838 0x000A8184 0x000AB880
Proceeding back via exception chain:
Exception state (sv=0x2E96F000)
PC=0x000A4458; MSR=0x00001030; DAR=0x0000022C; DSISR=0x40000000; LR=0x000A43A4; R1=0x0D81B780; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x0010CB70 0x000FA574 0x000E150C 0x000E10A0 0x000D2400
0x002A8174 0x000ABA30 0x0BE80002
Exception state (sv=0x2F0CAC80)
PC=0x9001BF00; MSR=0x0200F030; DAR=0x178A6040; DSISR=0x40000000; LR=0x90B0ABE4; R1=0xBFFFC200; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.0.0: Sat Mar 26 14:15:22 PST 2005; root:xnu-792.obj~1/RELEASE_PPC
*********





[ Reply to This | # ]