This content has been marked as final. Show 3 replies
My suspicion is with RAM.
AFT0's and AFT2's are informational log entries.
They note circumstances that may or may not evolve.
Only AFT1's are worth immediate examination.
Admittedly, your excerpt was only a few lines, but I'd rarely seen a MESSAGES file pointedly mention <u>parity</u> unless something was happening with DIMMs.
I suggest you run Explorer, open a service case with Sun, and have them pore over the Explorer file.
IPE is Instruction Cache Parity Error for the CPU... so yes the reporting CPU is at fault.... rightly pointed out by Nilesh.
CPU I$/D$ Parity Error
. DPE D$ parity error
. DDSPE D$ data parity error
. DTSPE D$ physical tag parity error
. IPE I$ parity error
. IDSPE I$ data parity error
. ITSPE I$ physical tag parity error