[lkml]   [2010]   [Sep]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC 5/6] x86, NMI, Add support to notify hardware error with unknown NMI
On Mon, Sep 13, 2010 at 08:36:54PM +0200, Andi Kleen wrote:
> > >
> > > But if it's generic if not on the screen it should
> > > be at least in the error serialization data and logged after boot.
> >
> > I guess I don't know what that is, 'error serialization data'. Is
> > there somewhere I can read more about it?
> That's already supported in MCE -- saving the error record to NVRAM
> and logging it after reboot. NMI should probably do the same.
> It's much nicer than getting it from a console.

Hmm, that assumes these boxes have NVRAM. I am not sure if many of the
boxes I see with problems have NVRAM on them.

> > >
> > > At least on PCI-E it may be enough to simply dump all recent AER
> > > data.
> >
> > This assumes AER is supported on the bridge? Which for newer chips is
> > probably true, but I wasn't sure about older ones.
> Today's servers should usually have AER at least.
> For old systems you only can get the few bits in PCI space.
> > How would I dump AER data from within the kernel?
> Would need a buffer that is dumped for past events and
> reading the registers for not yet reported. Right now some
> infrastructure is needed.

Oh ok.


 \ /
  Last update: 2010-09-13 21:41    [W:0.166 / U:2.824 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site