Linas Vepstas wrote: > 3:mon> d c0000000077b21e0 > c0000000077b21e0 e00000008004b224 0674100900000080 |.......$.t......| > > Well, howdy doody, there's the value that should have been in r3 .... > > c0000000077b21f0 c4008e0000000000 0000000049424d00 |............IBM.| > > IBM ??? > > c0000000077b2200 5048003006000000 0000000000000000 |PH.0............| > c0000000077b2210 0000000000000000 4800000300000000 |........H.......| > c0000000077b2220 0000000000000000 0000000000000000 |................| > c0000000077b2230 5548001806000000 1000400000000000 |[EMAIL PROTECTED]| > c0000000077b2240 0000200000000000 4d43002806000000 |.. .....MC.(....| > c0000000077b2250 0000000000000001 00c3000000000000 |................| > c0000000077b2260 e00000008004b224 0000000000000000 |.......$........| > c0000000077b2270 d0000000000d32c0 8000000000101032 |......2........2| > > hey .. wait .. d0000000000d32c0 is the faulting adddress; whats it doing here > ??? > ... and 8000000000101032 is the value of the MSR ... why is that here ??
That looks like part of an RTAS event. PH indicates a "Main A" section, UH a "Main B" section, and, probably of most interest to you, MC indicates a "Failing Memory Address" section. The "Error and Event Notification" chapter of the PAPR will be useful here. You can use rtas_dump (in either powerpc-utils or ppc64-utils, depending on the distro) to decode the event in its entirety. A quick hand-decode of the MC section yields (might be wrong, you'll want to double-check): Unrecoverable memory error (UE); transient UE, 64-bit effective address provided by the log (located at c0000000077b2260), 64-bit logical address of logical page is not provided by the log; error detected by load/store unit of the processor. Mike _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
