[Hash]

I get kernel panics ONLY on cold boot. If i switch from OS 9 after using mac for a while, then X boots fine..

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): 0x400 - Inst access
Latest stack backtrace for cpu 0:
Backtrace:
0x0008593C 0x00085D6C 0x00028B8C 0x0008F648 0x000926B8
Proceeding back via exception chain:
Exception state (sv=0x14E05C80)
PC=0x00000000; MSR=0x40009030; DAR=0x00008000; DSISR=0x42000000; LR=0x00000000; R1=0x0DA33C90; XCP=0x00000010 (0x400 - Inst access)
Backtrace:
0x00021040 0x000263C0 0x0002628C 0x0004A448 0x0002AE70 0x000257E4 0x00025BE0 0x00092A38
0x00640050
Exception state (sv=0x1507E280)
PC=0x90074328; MSR=0x0200F030; DAR=0x00008000; DSISR=0x42000000; LR=0x90006670; R1=0xBFFFFB80; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.0:
Sat Jul 27 13:18:52 PDT 2002; root:xnu/xnu-344.obj~1/RELEASE_PPC



*********

Fri Jan 10 16:16:36 2003




Unresolved kernel trap(cpu 0): 0x400 - Inst access DAR=0xa0007338 PC=0x00000000
Latest crash info for cpu 0:
Exception state (sv=0x1507CC80)
PC=0x00000000; MSR=0x40009030; DAR=0xA0007338; DSISR=0x42000000; LR=0x00000001; R1=0x0DA33DC0; XCP=0x00000010 (0x400 - Inst access)
Backtrace:
0x00000001 0x00000000
backtrace terminated - unaligned frame address: 0x0000000A

Proceeding back via exception chain:
Exception state (sv=0x1507CC80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x1502D780)
PC=0x900074B8; MSR=0x0000D030; DAR=0xA0007338; DSISR=0x42000000; LR=0x90007490; R1=0xBFFFFDF0; XCP=0x0000000C (0x300 - Data access)

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): 0x400 - Inst access
Latest stack backtrace for cpu 0:
Backtrace:
0x0008593C 0x00085D6C 0x00028B8C 0x0008F648 0x000926B8
Proceeding back via exception chain:
Exception state (sv=0x1507CC80)
PC=0x00000000; MSR=0x40009030; DAR=0xA0007338; DSISR=0x42000000; LR=0x00000001; R1=0x0DA33DC0; XCP=0x00000010 (0x400 - Inst access)
Backtrace:
0x00000001 0x00000000
backtrace terminated - unaligned frame address: 0x0000000A

Exception state (sv=0x1502D780)
PC=0x900074B8; MSR=0x0000D030; DAR=0xA0007338; DSISR=0x42000000; LR=0x90007490; R1=0xBFFFFDF0; XCP=0x0000000C (0x300 - Data access)

Kernel version:
Darwin Kernel Version 6.0:
Sat Jul 27 13:18:52 PDT 2002; root:xnu/xnu-344.obj~1/RELEASE_PPC

[tobli]

You should send this to Apple if you haven't done so already.

[Gul Banana]

If you want, you can go to http://homepage.mac.com/castiglione/...decode-0.1.dmg and use the command-line tool therein to attempt to decipher it; I can't do it for you because you need to be running the same kernel version as when the panic occurred for kpdecode to work.

[BTP]

Gul, thanks for that link! I have been wondering if something like that was around.

FWIW, I had some mysterious KP's that I could not figure out, but it turned out to be a bad 256MB RAM. Rreplaced that and haven't seen a KP since. Of course, it would never panic/crash in 9. OS X has tighter demands placed upon memory specs I guess.

[snerdini]

Originally posted by BTP:
OS X has tighter demands placed upon memory specs I guess.

Unix-based OSes do in general.

[K++]

Originally posted by BTP:
Gul, thanks for that link! I have been wondering if something like that was around.

FWIW, I had some mysterious KP's that I could not figure out, but it turned out to be a bad 256MB RAM. Rreplaced that and haven't seen a KP since. Of course, it would never panic/crash in 9. OS X has tighter demands placed upon memory specs I guess.

Yes it would have, programs would frequently crash and yoru computer would frequently need to eb restarted due to a crash.

I know this because when i bought my mac i got a free 256 that was BAD and my apps all crashed within 30 minutes of use for absolutely no reason. And I realized it was the memory when I called Apple and explained that use of PhotoShop or Fireworks greatly sped up the speed in which I would get these crashes.