Originally posted by alien:
There should be a panic.log somewhere on the disk, try /var/log, /Library/Logs or ~/Library/Logs.
Post the log, which could give us a clue on what's happening.
Whoa. Cool! I had no idea!
Well, here is the last panic. Since messing around with things, I think I may have narrowed it down to the RAM chip. We'll see.
From /Library/Logs:
Fri Jan 24 18:46:36 2003
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000020 PC=0x0008d92c
Latest crash info for cpu 0:
Exception state (sv=0x26AE8000)
PC=0x0008D92C; MSR=0x00001030; DAR=0x00000020; DSISR=0x40000000; LR=0x0002E764; R1=0x16D2B5B0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00040A54 0x0008D51C 0x0006E504 0x00066378 0x000665CC 0x00038D6C 0x001DB43C 0x001E5398
0x0002706C 0x00092B14 0x00028C58 0x0008FDD0 0x0008FB8C 0x00092698
Proceeding back via exception chain:
Exception state (sv=0x26AE8000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2B4E3000)
PC=0x9015BB24; MSR=0x0000D030; DAR=0xA100C1EB; DSISR=0x40000000; LR=0x9015BB08; R1=0xBFFFF6B0; XCP=0x00000003 (Unknown)
Kernel version:
Darwin Kernel Version 6.3:
Sat Dec 14 03:11:25 PST 2002; root:xnu/xnu-344.23.obj~4/RELEASE_PPC
panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000856CC 0x00085AFC 0x000287A8 0x0008F588 0x00092698
Proceeding back via exception chain:
Exception state (sv=0x26AE8000)
PC=0x0008D92C; MSR=0x00001030; DAR=0x00000020; DSISR=0x40000000; LR=0x0002E764; R1=0x16D2B5B0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00040A54 0x0008D51C 0x0006E504 0x00066378 0x000665CC 0x00038D6C 0x001DB43C 0x001E5398
0x0002706C 0x00092B14 0x00028C58 0x0008FDD0 0x0008FB8C 0x00092698
Exception state (sv=0x2B4E3000)
PC=0x9015BB24; MSR=0x0000D030; DAR=0xA100C1EB; DSISR=0x40000000; LR=0x9015BB08; R1=0xBFFFF6B0; XCP=0x00000003 (Unknown)
Kernel version:
Darwin Kernel Version 6.3:
Sat Dec 14 03:11:25 PST 2002; root:xnu/xnu-344.23.obj~4/RELEASE_PPC