I bought an extra 1gb of RAM for my iBook a few days back - From crucial, using the system selector tool so its guarenteed to be compatible. System picks up the RAM fine, and it goes a lot faster! However, yesterday and today since putting the ram in I have had kernel panics. I have taken a look at the logs, and they look similar, but I'm hoping someone here can look at them and confirm my suspicions that the RAM is faulty. Alternatively, does anyone know of an equivalent to memtest86 for a PPC mac? Cheers for any help, logs are posted below: Code: Sat Dec 30 01:50:16 2006 Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000000 PC=0x00000000000DA560 Latest crash info for cpu 0: Exception state (sv=0x381A5500) PC=0x000DA560; MSR=0x00009030; DAR=0x00000000; DSISR=0x42000000; LR=0x000DA6BC; R1=0x220FBAB0; XCP=0x0000000C (0x300 - Data access) Backtrace: 0x000761E8 0x000DA6BC 0x000E5ACC 0x000E5ECC 0x000E8328 0x000E58D4 0x000EBE44 0x000E6AA4 0x0026F5B0 0x0027C084 0x002AAE28 0x000AB930 0x30342220 Proceeding back via exception chain: Exception state (sv=0x381A5500) previously dumped as "Latest" state. skipping... Exception state (sv=0x3C8ED500) PC=0x900C72A0; MSR=0x0000D030; DAR=0x901FBB76; DSISR=0x40000000; LR=0x0000292C; R1=0xBFFFFE80; XCP=0x00000030 (0xC00 - System call) Kernel version: Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access Latest stack backtrace for cpu 0: Backtrace: 0x00095138 0x00095650 0x00026898 0x000A7E04 0x000AB780 Proceeding back via exception chain: Exception state (sv=0x381A5500) PC=0x000DA560; MSR=0x00009030; DAR=0x00000000; DSISR=0x42000000; LR=0x000DA6BC; R1=0x220FBAB0; XCP=0x0000000C (0x300 - Data access) Backtrace: 0x000761E8 0x000DA6BC 0x000E5ACC 0x000E5ECC 0x000E8328 0x000E58D4 0x000EBE44 0x000E6AA4 0x0026F5B0 0x0027C084 0x002AAE28 0x000AB930 0x30342220 Exception state (sv=0x3C8ED500) PC=0x900C72A0; MSR=0x0000D030; DAR=0x901FBB76; DSISR=0x40000000; LR=0x0000292C; R1=0xBFFFFE80; XCP=0x00000030 (0xC00 - System call) Kernel version: Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC ********* Sun Dec 31 00:39:07 2006 Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000004597025A PC=0x00000000000DA560 Latest crash info for cpu 0: Exception state (sv=0x38021A00) PC=0x000DA560; MSR=0x00009030; DAR=0x4597025A; DSISR=0x42000000; LR=0x000DA6BC; R1=0x220CB400; XCP=0x0000000C (0x300 - Data access) Backtrace: 0x00000000 0x000DA6BC 0x000E5ACC 0x000E5ECC 0x000E8328 0x000E7C04 0x000E84AC 0x00222704 0x00228048 0x002282E4 0x000FB124 0x000E1EE8 0x000E1A7C 0x000EE74C 0x000EEB04 0x000EEBA4 0x002AAE28 0x000AB930 0x38222073 Proceeding back via exception chain: Exception state (sv=0x38021A00) previously dumped as "Latest" state. skipping... Exception state (sv=0x38590280) PC=0x90021A0C; MSR=0x0000D030; DAR=0x38FA2FBE; DSISR=0x40000000; LR=0x9003D7B4; R1=0xBFFFFA30; XCP=0x00000030 (0xC00 - System call) Kernel version: Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access Latest stack backtrace for cpu 0: Backtrace: 0x00095138 0x00095650 0x00026898 0x000A7E04 0x000AB780 Proceeding back via exception chain: Exception state (sv=0x38021A00) PC=0x000DA560; MSR=0x00009030; DAR=0x4597025A; DSISR=0x42000000; LR=0x000DA6BC; R1=0x220CB400; XCP=0x0000000C (0x300 - Data access) Backtrace: 0x00000000 0x000DA6BC 0x000E5ACC 0x000E5ECC 0x000E8328 0x000E7C04 0x000E84AC 0x00222704 0x00228048 0x002282E4 0x000FB124 0x000E1EE8 0x000E1A7C 0x000EE74C 0x000EEB04 0x000EEBA4 0x002AAE28 0x000AB930 0x38222073 Exception state (sv=0x38590280) PC=0x90021A0C; MSR=0x0000D030; DAR=0x38FA2FBE; DSISR=0x40000000; LR=0x9003D7B4; R1=0xBFFFFA30; XCP=0x00000030 (0xC00 - System call) Kernel version: Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC *********
Try using the Hardware Test disc that came with your OS package. It'll boot the iBook into OS9 and run various hardware checks. If the RAM stick is bad, it'll pick it up. Alternatively, try removing and re-seating the stick.
Realised that afterwards - It picked up the new RAM as the problem, so crucial will be getting a call from me tomorrow. Thanks for the tip anyway!
Rule #1 when a computer dies: The last change made to it is probably what fucked it up. It's amazing how well this rule works. I think one we had a fluke where 7 year old code broke, but it's extremely rare... like anal sex on the first date.
Look for a program called Super Pi. I'm sure it will work on a PPC architecture. It stresses the CPU and system RAM.