Kernel panic on G5: reason for concern?

[barracuda156]

Got this out of the blue on 10.5.8 booted from HDD.

Interval Since Last Panic Report:  1303834 sec
Panics Since Last Report:          1
Anonymous UUID:                    E9887EFC-0063-4725-ABFB-06A0FAF2EAB4

Wed Feb  9 11:43:19 2022


Unresolved kernel trap(cpu 2): 0x300 - Data access DAR=0x0000000000000008 PC=0x000000000006EF10
Latest crash info for cpu 2:
   Exception state (sv=0x6e65e500)
      PC=0x0006EF10; MSR=0x00001030; DAR=0x00000008; DSISR=0x40000000; LR=0x000672D0; R1=0x6E9379B0; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
0x15FA3880 0x000672D0 0x000A3EE4 0x000A3260 0x000A052C 0x00064DCC 
         0x0006775C 0x000B110C 0x000B4278 
         backtrace terminated - frame not mapped or invalid: 0xBFFFC570

Proceeding back via exception chain:
   Exception state (sv=0x6e65e500)
      previously dumped as "Latest" state. skipping...
   Exception state (sv=0x6e62d780)
      PC=0x8FE16554; MSR=0x0000D030; DAR=0xBFFFB920; DSISR=0x42000000; LR=0x8FE164E8; R1=0xBFFFC570; XCP=0x0000000C (0x300 - Data access)

BSD process name corresponding to current thread: ReportCrash

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: PowerMac11,2

System uptime in nanoseconds: 916195357243
unloaded kexts:
com.apple.driver.Apple02DBDMAAudio    2.5.8f1 - last unloaded 5823913551
loaded kexts:
com.apple.filesystems.autofs    2.0.2 - last loaded 1209047059
com.apple.driver.AppleTopazAudio    2.5.8f1
com.apple.driver.AppleOnyxAudio    2.5.8f1
com.apple.GeForcePPC    5.4.8
com.apple.iokit.CHUDUtils    201
com.apple.iokit.CHUDProf    211
com.apple.nvidia.nv40halppc    5.4.8
com.apple.driver.AudioIPCDriver    1.0.6
com.apple.driver.AppleTexasAudio    2.5.8f1
com.apple.driver.AppleTexas2Audio    2.5.8f1
com.apple.driver.PowerMac11_2_ThermalProfile    3.4.0d0
com.apple.driver.AppleDACAAudio    2.5.8f1
com.apple.driver.AppleSCCSerial    1.3.2
com.apple.driver.AppleHWSensor    1.9d0
com.apple.driver.IOI2CSMUSat    1.9d0
com.apple.driver.IOI2CLM7x    1.9d0
com.apple.iokit.IOFireWireIP    1.7.7
com.apple.driver.AppleK2Driver    1.7.2f1
com.apple.driver.Apple_iSight    1.1.4
com.apple.driver.IOI2CMaxim6690    1.9d0
com.apple.driver.AppleSMUMonitor    1.9d0
com.apple.driver.IOI2CMaxim1631    1.9d0
com.apple.driver.AppleI2S    1.0.1f1
com.apple.driver.IOI2CPulsar    1.5.2d0
com.apple.driver.IOI2CControllerSMU    1.1.1d2
com.apple.driver.AppleFileSystemDriver    1.1.0
com.apple.iokit.IOUSBHIDDriver    3.4.6
com.apple.driver.AppleUSBComposite    3.2.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice    2.1.1
com.apple.iokit.SCSITaskUserClient    2.1.1
com.apple.driver.XsanFilter    2.7.91
com.apple.iokit.IOATABlockStorage    2.0.6
com.apple.driver.AppleUSBHub    3.4.9
com.apple.iokit.IOATAPIProtocolTransport    1.5.3
com.apple.iokit.IOUSBUserClient    3.5.2
com.apple.driver.AppleK2SATA    1.0.4f2
com.apple.driver.AppleGPIO    1.3.0d0
com.apple.driver.MacIOGPIO    1.3.0d0
com.apple.iokit.AppleBCM5701Ethernet    2.2.3b1
com.apple.driver.AppleFWOHCI    3.9.7
com.apple.driver.AppleKauaiATA    1.2.1f4
com.apple.driver.AppleK2SATARoot    1.0.5b1
com.apple.driver.AppleMPIC    1.5.3
com.apple.driver.AppleI2C    4.0.0d2
com.apple.driver.IOI2CControllerPPC    1.1.1d2
com.apple.driver.AppleUSBEHCI    3.4.6
com.apple.driver.AppleUSBOHCI    3.4.6
com.apple.driver.AppleK2    1.7.2f1
com.apple.driver.AppleSMU    1.2.1d1
com.apple.driver.AppleMacRiscPCI    3.4.0
com.apple.driver.AppleCore99NVRAM    1.1.1
com.apple.driver.AppleFlashNVRAM    1.0.5
com.apple.security.seatbelt    107.12
com.apple.nke.applicationfirewall    1.8.77
com.apple.security.TMSafetyNet    3
com.apple.BootCache    30.4
com.apple.driver.DiskImages    199
com.apple.driver.AppleM`

 

[barracuda156]

 

[B S Magnet]

“Corrupt stack” might hint at a stick of RAM going faulty. Other mentions of similar online hint at either RAM failing or, less likely, an L2/L3 cache going bad.

To be sure, it may require using a minimum two paired sticks of RAM (amounting to less memory than what you’re usually accustomed to working with) to find whether the kernel panic repeats itself.

 

[barracuda156]

“Corrupt stack” might hint at a stick of RAM going faulty. Other mentions of similar online hint at either RAM failing or, less likely, an L2/L3 cache going bad.

To be sure, it may require using a minimum two paired sticks of RAM (amounting to less memory than what you’re usually accustomed to working with) to find whether the kernel panic repeats itself.

Hopefully it's RAM, since that won't be a big trouble: I got spare 4 GB.

Will running AHT or Diagnostic reveal the problem? Taking RAM out is an annoyance, and also it's unclear how to figure out which stick is at fault.

 

[B S Magnet]

Hopefully it's RAM, since that won't be a big trouble: I got spare 4 GB.

Will running AHT or Diagnostic reveal the problem? Taking RAM out is an annoyance, and also it's unclear how to figure out which stick is at fault.

You might try running memtest from a single user boot mode. That’s what I’d start with.

 

[Certificate of Excellence]

In regards to the ram, assuming that is the cause, I would test each pair until you find the offending set. Then swap one dimm out with a new known good dimm (I'd mark it to prevent confusion - maybe a piece of tape). If stability is regained, you know the bad dimm is the stick that was left out. If results are the other way round, its the other dimm. If both fail, then the pair is bad.

Truth be told, most OSX KP instability I've experienced was due to heat and faulty hardware (in my case gpus), but I have seen faulty/finicky ram make computers of all flavors be very grumpy and uncooperative. Most recently for me rebuilding a retro P2 Dell tower. Best of luck to you.

 

[barracuda156]

In regards to the ram, assuming that is the cause, I would test each pair until you find the offending set. Then swap one dimm out with a new known good dimm (I'd mark it to prevent confusion - maybe a piece of tape). If stability is regained, you know the bad dimm is the stick that was left out. If results are the other way round, its the other dimm. If both fail, then the pair is bad.

Truth be told, most OSX KP instability I've experienced was due to heat and faulty hardware (in my case gpus), but I have seen faulty/finicky ram make computers of all flavors be very grumpy and uncooperative. Most recently for me rebuilding a retro P2 Dell tower. Best of luck to you.

I am actually in a process of replacing the video card, so that isn’t an issue too. I only hope it is not CPU problem, as that will be irreplaceable.

 

[Certificate of Excellence]

I think AHT is a good tool to use. 4MEM & 4PRC are the error codes thrown for memory or cpu fault that you suspect. Here's a full list.

4AIR	AirPort wireless card
4ETH	Ethernet
4HDD	Hard disk (includes SSD)
4IRP	Logic board
4MEM	Memory module (RAM)
4MHD	External disk
4MLB	Logic board controller
4MOT	Fans
4PRC	Processor
4SNS	Failed sensor
4YDC	Video/Graphics card

If it turns out that it is the CPU & they're getting old n grumpy, it just might be time to give the LCS a flush, & seal rebuild and cpu, a clean & repaste.

 

[barracuda156]

I am still to use the test tools, but safe to assume it is indeed RAM. I have just noticed that it got down to 12 GB on its own. There are still 16 GB sticks installed.

 

[barracuda156]

Oh, I actually know which pair is faulty from System Profiler:

 

[DeltaMac]

Looks like you have quite a mix of memory... !
Try moving the pair of PC2-4200 sticks to the "empty" slots. Don't reinsert the sticks that you take out of the "Empty" slots for now.
Boot to check that it sees all the existing memory. Then, insert the memory that you removed, into the now-empty slots.
Are the other pairs that show as PC2-3200 actually PC2-4200? Or are they labeled as PC2-3200?
If they are actually labeled as PC2-4200, remove and reseat each pair.
(Be sure to reseat all the memory sticks anyway, if you have not done this recently)

 

[barracuda156]

Looks like you have quite a mix of memory... !
Try moving the pair of PC2-4200 sticks to the "empty" slots. Don't reinsert the sticks that you take out of the "Empty" slots for now.
Boot to check that it sees all the existing memory. Then, insert the memory that you removed, into the now-empty slots.
Are the other pairs that show as PC2-3200 actually PC2-4200? Or are they labeled as PC2-3200?
If they are actually labeled as PC2-4200, remove and reseat each pair.
(Be sure to reseat all the memory sticks anyway, if you have not done this recently)

Thank you. For now I just removed a faulty pair (probably just one stick is faulty, but w/e) and replaced it with a backup pair I had. RAM is back to 16 GB and so far no KP and no weird freezes, thankfully.