RE: new utility for decoding salinfo records

From: Luck, Tony <tony.luck_at_intel.com>
Date: 2005-01-12 17:08:56
>The design of salinfo_decode2 is completely unacceptable for SGI
>hardware, and probably for HP as well.  You have removed all processing
>of the oemdata.
>
>SGI hardware decodes the oemdata in SAL records using prom code.  This
>decode _must_ be done while the record is still in the prom's memory
>space.  The callback into the prom (via the kernel) must be done after
>the main part of the record is printed and before the record is cleared
>from SAL.  For some error types such as CPE, the SGI oemdata provides
>critical information about which DIMM is failing, including its node
>and serial number.

I think that Ben was just plugging the "salinfo_decode2" program that is
included in his alternate salinfo package (though this would perhaps have
been more clear if he'd just posted the program, rather than the whole
package).  The text of his e-mail only talked about salinfo_decode2.

The salinfo_decode2 program just takes the 'raw' images of error records
that have been saved by any daemon, and creates summary reports.

Thanks for clarifying why his daemon won't work for SGI.

-Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Wed Jan 12 01:09:23 2005

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:34 EST