On Sun, Dec 08, 2013 at 03:43:12PM +0100, Borislav Petkov wrote:
> On Sun, Dec 08, 2013 at 12:17:53PM +0800, Rui Wang wrote:
> > There's inconsistency between dmesg and the trace event output.
> > When dmesg says "severity=Corrected", the trace event says
> > "severity=Fatal". What happens is that HW_EVENT_ERR_CORRECTED is
> > defined in edac.h:
> >
> > enum hw_event_mc_err_type {
> > HW_EVENT_ERR_CORRECTED,
> > HW_EVENT_ERR_UNCORRECTED,
> > HW_EVENT_ERR_FATAL,
> > HW_EVENT_ERR_INFO,
> > };
> >
> > while aer_print_error() uses aer_error_severity_string[] defined as:
> >
> > static const char *aer_error_severity_string[] = {
> > "Uncorrected (Non-Fatal)",
> > "Uncorrected (Fatal)",
> > "Corrected"
> > };
> >
> > In this case dmesg is correct because info->severity is assigned in
> > aer_isr_one_error() using the definitions in include/linux/ras.h:
> >
> > Signed-off-by: Rui Wang <rui.y.wang@xxxxxxxxx>
>
> Applied, thanks.
I said "Applied" but this is Bjorn's area: Bjorn, wanna take this one or
are you fine with it going over the RAS tree?
Btw, I have a 2 trivial cleanups for aerdrv_errprint.c which are
following...
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
