Kernel Panic 9.5 - Can You Tell By This Report if It's 3rd Party Software?

[mnolan1960]

Have a Power Mac G5, PowerMac 9,1 that has been crashing with increasing frequency. Have tested RAM (1.25 G of DDR SDRAM) repeatedly using a variety of Apple and 3rd party programs (most recently Rember).

Running a 3 month old 500 G external drive (problems started before), also external Firewire audio hardware with latest software and drivers from manufacturer (MOTU).

If someone could tell me whether third party software is the problem, or give me any help at all, I would really, really, really appreciate it.

Here's are two reports - starting with the latest (today) and a previous one from months ago Again, thanks!

Today's report:

Sat Oct 4 08:40:20 2008
panic(cpu 0 caller 0x00E2C288): "AppleDART::mapAddr(0x0012c000) not mapped for I/O\n"@AppleDART.cpp:603
Latest stack backtrace for cpu 0:
Backtrace:
0x0009B518 0x0009BEBC 0x00029DD8 0x00E2C288 0x00360294 0x0080AB48 0x00809344 0x0080965C
0x004F3D84 0x0035A914 0x0003F94C 0x000B0654
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleUSBOHCI(3.1.0)@0x801000->0x80dfff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x7a8000
dependency: com.apple.iokit.IOUSBFamily(3.1.5)@0x4f2000
com.apple.iokit.IOUSBFamily(3.1.5)@0x4f2000->0x526fff
com.apple.driver.AppleMacRiscPCI(3.4.0)@0xe26000->0xe2ffff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x7a8000
Proceeding back via exception chain:
Exception state (sv=0x36f5d280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9F33

Kernel version:
Darwin Kernel Version 9.5.0: Wed Sep 3 11:31:44 PDT 2008; root:xnu-1228.7.58~1/RELEASE_PPC
System model name: PowerMac9,1

Earlier Report

Sat Aug 16 16:26:09 2008


Unresolved kernel trap(cpu 0): 0x700 - Program DAR=0x00000000115B9001 PC=0x0000000002FBD000
Latest crash info for cpu 0:
Exception state (sv=0x37d3ac80)
PC=0x02FBD000; MSR=0x00089030; DAR=0x115B9001; DSISR=0x42000000; LR=0x02FBD000; R1=0x24A2A320; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x02FBD000 0x0072999C 0x0072D6E8 0x0072E40C 0x0072E6B8 0x0072E7EC
0x0072E940 0x007301C8 0x00733F20 0x0096B948 0x0096CEFC 0x0096D150 0x00958740 0x00959DF4
0x00959628 0x009597DC 0x0034806C 0x003860B0 0x00386254 0x00356248 0x00384340 0x0038190C
0x00379584 0x0037BC74 0x00378F2C 0x00093FA4 0x0002C1C8 0x00024C94 0x000B2DCC 0x00000000
backtrace terminated - frame not mapped or invalid: 0xF007ED00

Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.SMU_Neo2_PlatformPlugin(3.1.6d0)@0x963000->0x971fff
dependency: com.apple.driver.IOPlatformPluginFamily(3.1.6d0)@0x950000
com.apple.driver.IOPlatformPluginFamily(3.1.6d0)@0x950000->0x962fff
com.apple.driver.AppleSMU(1.2.1d1)@0x728000->0x73bfff
Proceeding back via exception chain:
Exception state (sv=0x37d3ac80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2cfa5280)
PC=0x945D0438; MSR=0x0000F030; DAR=0x115B9001; DSISR=0x42000000; LR=0x945D7360; R1=0xF007ED00; XCP=0x00000030 (0xC00 - System call)

BSD process name corresponding to current thread: configd

Mac OS version:
9E17

Kernel version:
Darwin Kernel Version 9.4.0: Mon Jun 9 19:36:17 PDT 2008; root:xnu-1228.5.20~1/RELEASE_PPC
System model name: PowerMac9,1
panic(cpu 0 caller 0xFFFF0007): 0x700 - Program
Latest stack backtrace for cpu 0:
Backtrace:
0x0009B498 0x0009BE3C 0x00029DD8 0x000AF090 0x000B2A78
Proceeding back via exception chain:
Exception state (sv=0x37d3ac80)
PC=0x02FBD000; MSR=0x00089030; DAR=0x115B9001; DSISR=0x42000000; LR=0x02FBD000; R1=0x24A2A320; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x02FBD000 0x0072999C 0x0072D6E8 0x0072E40C 0x0072E6B8 0x0072E7EC
0x0072E940 0x007301C8 0x00733F20 0x0096B948 0x0096CEFC 0x0096D150 0x00958740 0x00959DF4
0x00959628 0x009597DC 0x0034806C 0x003860B0 0x00386254 0x00356248 0x00384340

 

[Toniola]

Try a test by creating a new User account. Then see if you crash during some usual process. Could give a hint as to whether there's a software conflict within your primary user account.
Have you tried erasing your drive and rebuilding?