Help With Kernel Panic Analysis

[Earendil]

My parents G4 1ghz tower is kernel panicing up to 3 times a day. Started 8 months ago, panicking once a month, and in the last 6 week has picked up dramatically, now 3 times a day.

So, I'm aware that RAM is a common problem when it comes to kernel panicking, and that in most cases it is a hardware problem in some form, correct? I can eliminate most of the "junk" from this report that the G4 gives, however it was emailed to me, so I can't speak for the formatting/completeness of the report. Throwing money at this problem isn't really an option for my parents, so finding out the problem and the cost with as much trouble shooting as possible would be great.

Thanks for the help guys!

Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000001D96D005 PC=0x0000000021448890
Latest crash info for cpu 0:
Exception state (sv=0x212A9500)
PC=0x21448890; MSR=0x00009030; DAR=0x1D96D005; DSISR=0x40000000; LR=0x2144888C; R1=0x0CEA39A0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x80000097 0x214481A8 0x0011C644 0x00154398 0x001415F0 0x0028DB08
0x00292D10 0x00292EE4 0x002A7A94 0x000ABCB0 0x0909093C
Kernel loadable modules in backtrace (with dependencies):
com.apple.nke.ppp(1.4)@0x21444000
Proceeding back via exception chain:
Exception state (sv=0x212A9500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x20EC6780)
PC=0x9001FD20; MSR=0x0000F030; DAR=0x17091044; DSISR=0x40000000; LR=0x00002EC4; R1=0xBFFFFAD0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu-792.2.4.obj~3/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095544 0x00095A5C 0x0002683C 0x000A819C 0x000ABB00
Proceeding back via exception chain:
Exception state (sv=0x212A9500)
PC=0x21448890; MSR=0x00009030; DAR=0x1D96D005; DSISR=0x40000000; LR=0x2144888C; R1=0x0CEA39A0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x80000097 0x214481A8 0x0011C644 0x00154398 0x001415F0 0x0028DB08
0x00292D10 0x00292EE4 0x002A7A94 0x000ABCB0 0x0909093C
Kernel loadable modules in backtrace (with dependencies):
com.apple.nke.ppp(1.4)@0x21444000
Exception state (sv=0x20EC6780)
PC=0x9001FD20; MSR=0x0000F030; DAR=0x17091044; DSISR=0x40000000; LR=0x00002EC4; R1=0xBFFFFAD0; XCP=0x00000030 (0xC00 - System call)


The Little I know seems like it's trying to access a memory location that is returning incredibly bad results, and causing the OS to make the call to just quit out instead of risk losing data?

~Earendil


edit: Parents computer isn't actually "Kernel pacing" as much as kernel panicking

 

[mad jew]

Okay, I'm not very good at this but it mentions NKE or Network Kernel Extensions. Is it Tiger or an earlier OS?

In Tiger at least, NKE allows for the following:

Adding support for new, non-ethernet interface types.
Designing custom routing technologies.
Creating link-layer encryption technologies.

In other words, it may be something to do with a device such as a modem (or really anything ). Tell your parents to unplug everything and see if the problem persists. Do they have a USB modem? OSX prefers ethernet modems, if you have a choice.

Also, as you say these things are often RAM related. Maybe take all but the standard RAM out for a while too.

I don't suppose you know what changes eight months ago could have caused this?

Sorry for not being more helpful.




Oh, and that's a really cool 'tar by the way.

 

[yenko]

Disk Warrior.

 

[slooksterPSV]

Okay, I'm not very good at this but it mentions NKE or Network Kernel Extensions. Is it Tiger or an earlier OS?

In Tiger at least, NKE allows for the following:





In other words, it may be something to do with a device such as a modem (or really anything ). Tell your parents to unplug everything and see if the problem persists. Do they have a USB modem? OSX prefers ethernet modems, if you have a choice.

Also, as you say these things are often RAM related. Maybe take all but the standard RAM out for a while too.

I don't suppose you know what changes eight months ago could have caused this?

Sorry for not being more helpful.




Oh, and that's a really cool 'tar by the way.

I agree with this, it could be like if you have a USB DSL Modem or that. Use Ethernet it eliminates most problems.

 

[Earendil]

Ok, additional information that I should have mentioned, as I rag on people for not telling me the first time around when I help them with problems

Tiger, with recent updates.
No connection through Ethernet, in fact the network to that room recently failed, so it is off the network, but may still be plugged in. It could be some weird feedback on the CAT5 cable that killed the network up there, and is getting worse so as to cause feedback into the computer? I'll make sure that is unplugged.

Internet is acquired through an internal 56K modem, and a phone jack. Another possibility. AFAIK, the internet still works as good as new. Two other Macs are also using internet modems on phone lines in the house, and don't get kernel panics, but it could be a failing modem I suppose.

No new ram in the computer. It is all stock, and has been for 2.5 years now. Nothing new has been added except for maybe a keyboard. A scanner was added a few weeks ago, but that didn't effect the frequency of kernel panics.

My parents don't have Disk Warrior. Any other utils that might diagnose RAM/HD or peripheral failures on a deep level? I did a search over at versiontracker.com but hit nil.