 |
 |
reading error code from kernel panic
|
|
|
|
|
Junior Member
Join Date: Dec 1999
Status:
Offline
|
|
Hi,
I've got what I believe to be some bad memory. Let me rephrase that: one of three DIMMs in a machine at work is most definitely bad, causing kernel panics every few days. I think I nailed which DIMM in particular, but before I call the manufacturer I would like something substantial to say to them.
Does anyone know how to dicipher the error messages spewed onto the screen after a memory access exception error causing a kernel panic? I can read the obvious stuff -- 'unresolved kernel trap' is pretty self explanatory -- but I would love to be able to find out which DIMM is bad just by reading the hex and other text on the screen. I've got things like PC=... MSR=... DAR...DSISR...LR...R1...XCP, exception states, etc.
Anyone know how to go about doing this? Forgive me, as I have never been good at low level programming. Assembly and machine code make me shudder in fear and run for safety behind a pile of fortan books. <img border="0" title="" alt="[Wink]" src="wink.gif" />
tia!
Ben
|
|
|
| |
|
|
|
|
|
|
|
Senior User
Join Date: Sep 2000
Location: Boston, MA
Status:
Offline
|
|
I'm not sure how much that is really going to help you.
DAR = Data Access Register
DSISR = Data Storage Interrupt Source Register
etc, etc.
You need to get your hands on a PPC microprocessor reference
manual.
You'd be better off just removing the suspect DIMM and stress testing
the machine.
|
|
|
| |
|
|
|
|
|
|
|
Mac Enthusiast
Join Date: Jul 2002
Location: Leiden, Netherlands
Status:
Offline
|
|
</font><blockquote><font size="1" face="Geneva, Verdana, Arial, sans-serif">quote:</font><hr /><font size="1" face="Geneva, Verdana, Arial, sans-serif">Originally posted by zeller:
<strong>Hi,
Does anyone know how to dicipher the error messages spewed onto the screen after a memory access exception error causing a kernel panic? I can read the obvious stuff -- 'unresolved kernel trap' is pretty self explanatory -- but I would love to be able to find out which DIMM is bad just by reading the hex and other text on the screen. I've got things like PC=... MSR=... DAR...DSISR...LR...R1...XCP, exception states, etc.
Anyone know how to go about doing this? Forgive me, as I have never been good at low level programming. Assembly and machine code make me shudder in fear and run for safety behind a pile of fortan books. <img border="0" title="" alt="[Wink]" src="wink.gif" />
tia!
Ben</strong></font><hr /></blockquote><font size="1" face="Geneva, Verdana, Arial, sans-serif">Read <a href="http://www.opensource.apple.com/projects/documentation/howto/html/KEXT_Tutorials/HelloDebugger.html" target="_blank">this</a>
|
|
|
| |
|
|
|
|
|
|
|
Junior Member
Join Date: Dec 1999
Status:
Offline
|
|
</font><blockquote><font size="1" face="Geneva, Verdana, Arial, sans-serif">quote:</font><hr /><font size="1" face="Geneva, Verdana, Arial, sans-serif">Originally posted by Ludovic Hirlimann:
<strong>
Read <a href="http://www.opensource.apple.com/projects/documentation/howto/html/KEXT_Tutorials/HelloDebugger.html" target="_blank">this</a></strong></font><hr /></blockquote><font size="1" face="Geneva, Verdana, Arial, sans-serif">Cool, I'll peruse the file when I have some more time. It looks interesting, albeit extremely dense. But the name cracks me up. "Hello Debugger" and it links to a helpful article called "Hello Kernel".
I think I came to the bottom of the problem anyway -- one of the DIMMs appeared to be improperly seated. Even if that's not the problem, ram is cheap and easily replaced. 
take care all,
Ben
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
Top