Kernal panic

I am experiencing panics in 10.2, (on original H.D.) and also in 10.5 (on a sata drive) I would appreciate any help in deciphering latest log:


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000010
PC=0x0008d5a4
Latest crash info for cpu 0:
Exception state (sv=0x1E84EA00)
PC=0x0008D5A4; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000;
LR=0x0006ECF4; R1=0x171A3460; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0006ECCC 0x0006E7B0 0x0006F168 0x001F76B0 0x000B6034
0x000B31C0 0x001B53F4 0x001B5044
0x001B829C 0x001B86F8 0x000B13B0 0x000B0D84 0x000B91EC
0x0020FF8C 0x00092950 0x5F524553
Proceeding back via exception chain:
Exception state (sv=0x1E84EA00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x1C2F9500)
PC=0x9000FD6C; MSR=0x0200F030; DAR=0xE01AF000; DSISR=0x42000000;
LR=0x9100D134; R1=0xBFFFDCD0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.8:
Wed Sep 10 15:20:55 PDT 2003; root:xnu/xnu-344.49.obj~2/RELEASE_PPC


panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000857F4 0x00085C24 0x000287B4 0x0008F6A8 0x000927B8
Proceeding back via exception chain:
Exception state (sv=0x1E84EA00)
PC=0x0008D5A4; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000;
LR=0x0006ECF4; R1=0x171A3460; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0006ECCC 0x0006E7B0 0x0006F168 0x001F76B0 0x000B6034
0x000B31C0 0x001B53F4 0x001B5044
0x001B829C 0x001B86F8 0x000B13B0 0x000B0D84 0x000B91EC
0x0020FF8C 0x00092950 0x5F524553
Exception state (sv=0x1C2F9500)
PC=0x9000FD6C; MSR=0x0200F030; DAR=0xE01AF000; DSISR=0x42000000;
LR=0x9100D134; R1=0xBFFFDCD0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.8:
Wed Sep 10 15:20:55 PDT 2003; root:xnu/xnu-344.49.obj~2/RELEASE_PPC

any dependencies listed in your logs?

Without that I have no chance of figuring out the panic.. even on systems I work on a lot I use tools to format them

if not, I would boot with the CD and run hardware diagnostics.

advice appreciated

Thanks for the reply, Dysfunction. I tried to boot from the disk, but that even sent it into panic. A little background, I have 10.2 installed on the original hard drive, and 10.5 installed on a newer sata drive running off a controller card.(newer 1.2 gig processor, and video card also) I had been using the 10.5 for a year with no problems, then last week, all h#@! broke loose. I think it started with acrobat reader freezing, then firefox, then kernel panic, then more kernel panic, then not able to boot to the sata drive at all (apple logo screen, with no spinning cog) so I tried booting to original drive(with 10.2 on it) and was able to use that for a few days, until I started getting panics on that too. I can still boot to it, and use it, so I ran first aid, and it panic again. panics in safe mode and normal boot. Tried to boot from original disk, as you suggested, and more panic. do you have any suggestions before I trash everything on both drives and clean install everything? even if I do that (I have backup) I fear there is some hardware issue, and it could happen again. I realize I'm running a DeSoto with a corvette engine here, but its been so solid for so long, I'd like to see if I can hang on to it for a little longer. Thanks in advance.

If you're having panics without booting, that would suggest hardware. (I'm assuming that you had panics booted off the CD). Try pulling a stick of RAM, booting and running, and reversing. That'd be a good start

ram test

to help test the ram, I ran Memtest, with all sticks installed and got this:

MacOS X (Darwin) running in multi-user mode
POSIX version 198808
Pagesize is 4096
Pagesizemask is 0xtx
Requested memory: 774MB (811597824 bytes)
Available memory: 774MB (812634112 bytes)
Allocated memory: 774MB (811597824 bytes)
Attempting to lock allocated physical memory....memory locked
successfully

Running 1 test sequence...

Test sequence 1 of 1:
Stuck Address : FAILURE: possible bad address line
at offset 0x0001c198.
Skipping to next test...
Random Value :
\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/
-\|/-\|/ FAILURE: 0xffff9fbe != 0xffff9fb6 at offset
0x0001c198.
FAILURE: 0xff7f014a != 0xff7f0142 at offset 0x0001c19a.
FAILURE: 0xdd5f294a != 0xdd5f2942 at offset 0x0006bd9a.

followed by many many more failure lines.
So I shut down, pulled all but one stick, ran memtest again, all tests were OK, so I repeated this, with each stick by itself, and they all checked out OK, followed this by putting 2 in, checked out OK, then three, OK then all four, and all tests now showing OK. now I'm baffled, can you make any sense of this? help very much appreciated.

Could have been corrosion on the contacts, reseating may have cleared that. Could have also been knocked a tad loose.