[generationfourt]

I've had this G5 at work for quite some time and occasionally it's has been freezing and requiring a hard restart. Lately it's been happening a lot more often especially upon startup. I copy/pasted the problem report below, hopefully you guys can give me some insight.

It's a older 2004/05 G5 PPC 1.8 running 10.5.8

Interval Since Last Panic Report: 21480 sec
Panics Since Last Report: 1
Anonymous UUID: 694435A0-DBA9-466A-AA16-59E72E934625

Fri Oct 9 08:03:12 2009


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000000002A6 PC=0x00000000000A259C
Latest crash info for cpu 0:
Exception state (sv=0x60cc9000)
PC=0x000A259C; MSR=0x00009030; DAR=0x000002A6; DSISR=0x42000000; LR=0x000A0408; R1=0x604A2DA0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x000A03A8 0x00068710 0x0006BCFC 0x0006D2A4 0x000697A0 0x000DF180
0x00273DC8 0x00273FF4 0x00259808 0x0010C81C 0x000FF2E4 0x003100AC 0x000B4448 0xFEFFB6DF
backtrace terminated - frame not mapped or invalid: 0xF0080970

Proceeding back via exception chain:
Exception state (sv=0x60cc9000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x60c74000)
PC=0x913A6834; MSR=0x0000D030; DAR=0x60C7CFFE; DSISR=0x40000000; LR=0x0000F608; R1=0xF0080970; XCP=0x00000030 (0xC00 - System call)

BSD process name corresponding to current thread: mdworker

Mac OS version:
9L31a

Kernel version:
Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC
System model name: PowerMac7,3

System uptime in nanoseconds: 147598082960
unloaded kexts:
(none)
loaded kexts:
arcana.PRAM 1.0.4
com.apple.filesystems.autofs 2.0.2 - last loaded 1573417301
com.apple.driver.AudioIPCDriver 1.0.6
com.apple.driver.AppleTopazAudio 2.5.8f1
com.apple.driver.AppleTAS3004Audio 2.5.8f1
com.apple.driver.AppleTexasAudio 2.5.8f1
com.apple.driver.AppleTexas2Audio 2.5.8f1
com.apple.driver.AppleDACAAudio 2.5.8f1
com.apple.driver.AppleFCU 1.3.2b0
com.apple.driver.AppleK2Fan 1.0.10f1
com.apple.driver.AppleFan 1.0.10f1
com.apple.driver.AppleADT746x 1.0.10f1
com.apple.driver.AppleHWSensor 1.9d0
com.apple.driver.AppleLM7x 1.9d0
com.apple.driver.AppleUSBOpticalMouse 3.2.0
com.apple.driver.AppleSCCSerial 1.3.2
com.apple.driver.AppleCPUVoltage 1.5.2d0
com.apple.iokit.IOFireWireIP 1.7.7
com.apple.ATIRadeon9700 5.4.8
com.apple.driver.AppleVSP 2.2.2
com.apple.driver.AppleThermal 1.0.1f2
com.apple.driver.AppleSEP 1.3.0
com.apple.driver.AppleK2Driver 1.7.2f1
com.apple.driver.AppleSlewClock 1.5.2d0
com.apple.driver.AppleHWClock 1.5.2d0
com.apple.driver.AppleADM103x 1.0.10f1
com.apple.driver.PowerMac7_2_PlatformPlugin 3.4.0d0
com.apple.driver.InternalModemSupport 2.4.0
com.apple.driver.AppleMaxim6690 1.9d0
com.apple.driver.AppleI2S 1.0.1f1
com.apple.driver.AppleAD741x 1.9d0
com.apple.driver.AppleFileSystemDriver 1.1.0
com.apple.driver.AppleHIDKeyboard 1.0.9b4
com.apple.driver.AppleUSBMergeNub 3.4.6
com.apple.iokit.IOSCSIReducedBlockCommandsDevice 2.1.1
com.apple.driver.XsanFilter 2.7.91
com.apple.iokit.IOATABlockStorage 2.0.6
com.apple.driver.LSI_FW_500 2.0.9
com.apple.driver.Oxford_Semi 2.0.9
com.apple.driver.initioFWBridge 2.0.9
com.apple.driver.IOFireWireSerialBusProtocolSansPh ysicalUnit 2.0.9
com.apple.driver.StorageLynx 2.0.9
com.apple.driver.PioneerSuperDrive 2.0.9
com.apple.iokit.SCSITaskUserClient 2.1.1
com.apple.driver.AppleUSBHub 3.4.9
com.apple.iokit.IOUSBUserClient 3.4.9
com.apple.iokit.IOATAPIProtocolTransport 1.5.3
com.apple.driver.ApplePMU 2.5.6d2
com.apple.driver.AppleK2SATA 1.0.4f2
com.apple.driver.AppleVIA 1.5.1d1
com.apple.driver.AppleGPIO 1.3.0d0
com.apple.driver.MacIOGPIO 1.3.0d0
com.apple.driver.AppleMPIC 1.5.3
com.apple.driver.AppleCPUThermo 2.0.0a0
com.apple.driver.AppleI2C 4.0.0d2
com.apple.driver.Apple@

[reader50]

The process that hit the KP was mdworker, which is part of the search indexer. That suggests hard drive, RAM, or CPU. The CPU isn't likely since crashes happen most often on startup when the CPU would be cool.

Open Disk Utility, click on the hard drive icon, read the SMART status at bottom of pane. Anything other than "verified" would be interesting.

Launch the Apple Hardware Test and let it run. Watch the memory test especially, and use the long test version if possible. I'd let it check everything else it can while you have the AHT running.

[jmiddel]

I am pretty sure it's a hardware problem. To rule out software, do an archive+install. If this does not solve the problem, you either have a memory issue, hopefully, or a logic board failure. Try taking out the memory sticks in couples, I assume you have all slots filled if you are running Leopard on a G5 1.8. If that solves the problem, great, if not, replace them and remove the other pair. If non of this works, it's almost surely the logic board, which runs about $280-$375. Then there the installation and shipping, unless you can install it yourself, not complicated, but tedious.

[generationfourt]

Ok I can't find the AHT disk anywhere (computer was handed down from another dept.). I had a feeling it could be hardware related and I'm curious to see what the AHT would come up with.

I brought up disk utility and everything seemed fine. Repaired permissions on the hard disk.

any alternatives to the AHT?

[reader50]

AHT is often hidden on the original install DVD. Put the DVD in, reboot with the Option key held down. The extra disk session will appear as a bootable option "Hardware Test".

There is also the command-line utility memtest. You can run it from the GUI using Rember.

[generationfourt]

reader,

I can't find the original install DVD.

I ran rember (pretty cool!) and all the ram passed...


hmmm

[reader50]

Rember can only test the RAM that isn't in use, so run it right after booting up. And RAM can be sneaky, so I'd run the test a few times. Or leave it looped overnight.

Do you have an alternate hard drive available? You could clone to it, and boot from it for a time. The built-in SMART diagnostics spot problems before failure only about half the time. Running from a different hard drive for a week or three is a more definitive test. See if the problems go away.

[generationfourt]

yeah I plan on running the test again. I ran it right after boot with nothing running. The problem is the test takes a few hours so it's hard to not have it during work hours. I can try to leave it looped over night but I'm sure it'll KP overnight...

I'm going to get an alternate HD and clone it. I just need to find where my damn workplace put the OSX 10.5 disk on monday so I can clone– can I clone with out the osx disk??

[reader50]

If you can find the Install disc, you'll be able to run the official Apple Hardware Test.

You can clone from Disk Utility running on the volume to be cloned. It's safer to clone when booted from something else, but it will usually work anyway. A clean install on an alternate disk would be a better test, but may not be feasible at work. Because of all the extra work time to reinstall apps, etc.

For the Rember test. You could safe-boot (hold down Shift key) to prevent non-Apple system files from loading. That will make more memory available for the overnight test.

[Back up 15 and punt]

I have the same problem but my machine also will not sleep. What I have discovered is that if I put my machine to sleep, manually, and then wake it up my machine suffers from kernel panics. In addition, my machine will also suffer from kernel panics if I shutdown every night. However, if I leave my machine up and running 24/7 then the kernel panics go away. This points clearly in Apples direction but if is unfortunate that Apple probably does not plan to fix it either.

[Big Mac]

The Hardware Test on that generation of G5s was found on an Extra Software disc that was given along with the Restore disc.

[Back up 15 and punt]

Originally Posted by Big Mac 

The Hardware Test on that generation of G5s was found on an Extra Software disc that was given along with the Restore disc.

I already ran this test and everything came out ok.