Help decipher this kernel panick log?

Question

Hope someone can give me an insight on this message. Much appreciated.
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000004CB04E3 PC=0x00000000000E47B4
Latest crash info for cpu 0:
Exception state (sv=0x2EA80C80)
PC=0x000E47B4; MSR=0x00009030; DAR=0x04CB04E3; DSISR=0x42000000; LR=0x000E48B8; R1=0x1783BC60; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x000E489C 0x00230818 0x000F92F0 0x000EC7AC 0x000E8F74 0x000EC7F8
0x002AA304 0x000ABEB0 0x00000000
Proceeding back via exception chain:
Exception state (sv=0x2EA80C80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2E0F3000)
PC=0x9003B0EC; MSR=0x0200F030; DAR=0xE0006000; DSISR=0x42000000; LR=0x00002FEC; R1=0xBFFFFD80; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.4.0: Tue Jan 3 18:22:10 PST 2006; root:xnu-792.6.56.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095718 0x00095C30 0x0002683C 0x000A8384 0x000ABD00
Proceeding back via exception chain:
Exception state (sv=0x2EA80C80)
PC=0x000E47B4; MSR=0x00009030; DAR=0x04CB04E3; DSISR=0x42000000; LR=0x000E48B8; R1=0x1783BC60; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x000E489C 0x00230818 0x000F92F0 0x000EC7AC 0x000E8F74 0x000EC7F8
0x002AA304 0x000ABEB0 0x00000000
Exception state (sv=0x2E0F3000)
PC=0x9003B0EC; MSR=0x0200F030; DAR=0xE0006000; DSISR=0x42000000; LR=0x00002FEC; R1=0xBFFFFD80; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.4.0: Tue Jan 3 18:22:10 PST 2006; root:xnu-792.6.56.obj~1/RELEASE_PPCModel: PowerBook5,8, BootROM 4.9.5f3, 1 processors, PowerPC G4 (1.5), 1.67 GHz, 1 GB
Graphics: ATI Mobility Radeon 9700, ATY,RV360M11, AGP, 128 MB
Memory Module: SODIMM0/J20STANDARD, 512 MB, DDR2 SDRAM, PC2-4200S-444
Memory Module: SODIMM1/J23REVERSED, 512 MB, DDR2 SDRAM, PC2-4200S-444
AirPort: AirPort Extreme, 404.2 (3.90.34.0.p16)
Modem: Jump, , V.92, Version 1.0,
Bluetooth: Version 1.7.0f18, 2 service, 0 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
PCI Card: pci106b,4318, sppci_othernetwork, SLOT-A
PCI Card: TXN,PCIXXXX-00, cardbus, PC Card
PCI Card: usb, usb, USB20
PCI Card: usb, usb, USB20
PCI Card: usb, ehci, USB20
Parallel ATA Device: TOSHIBA MK8026GAX, 74.53 GB
Parallel ATA Device: MATSHITADVD-R UJ-846,
USB Device: Bluetooth HCI, , Up to 12 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
USB Device: Microsoft IntelliMouse® Explorer, Microsoft, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA

Answer 1

Hi, SSI.
Your panic logs reveal an 0x300 trap:
Unresolved kernel trap(cpu 0): 0x300 - Data access
and
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
The 0x300 (data access) exception indicates the processor could not perform a data memory access. Potential causes, in general terms, include RAM problems, hard disk corruption, and programming errors. "Programming errors" in this case can include invalid instructions and violations of protected memory, however it is often difficult to differentiate a programming error from a RAM or hard disk problem since the latter two issues can cause a valid instruction to appear invalid.
Unfortunately, no kernel-loadable modules are cited in the Backtrace, so this panic log yields little else in the way of clues. More information on changes you made to your system before the panics arose might help shed more light.
As to troubleshooting, see my "Resolving Kernel Panics" FAQ. This FAQ includes step-by-step instructions for identifying and resolving some of the most common causes of kernel panics.
My FAQ is a roadmap: start at the beginning and work through to the end, following the instruction in the order specified, including the "If all else fails..." section if a cause or resolution is not found in an earlier troubleshooting step therein.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.