| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20100913224952.442d7a24@basil.nowhere.org> Date: Mon, 13 Sep 2010 22:49:52 +0200 From: Andi Kleen <andi@...stfloor.org> To: Don Zickus <dzickus@...hat.com> Cc: Huang Ying <ying.huang@...el.com>, Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [RFC 5/6] x86, NMI, Add support to notify hardware error with unknown NMI On Mon, 13 Sep 2010 15:36:55 -0400 Don Zickus <dzickus@...hat.com> wrote: > 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. Practically every PC has a small amount of NVRAM. -Andi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists