Date: Mon, 8 Jan 2001 18:34:39 -0600 (CST) From: Chris Dillon <cdillon@wolves.k12.mo.us> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: David Kelly <dkelly@hiwaay.net>, FreeBSD Chat List <freebsd-chat@FreeBSD.ORG>, Francisco Reyes <fran@reyes.somos.net> Subject: Re: ECC worth the extra cost for SOHO server? Message-ID: <Pine.BSF.4.21.0101081828020.4671-100000@mail.wolves.k12.mo.us> In-Reply-To: <XFMail.010109103623.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 9 Jan 2001, Daniel O'Connor wrote: > > On 08-Jan-01 Chris Dillon wrote: > > thing" and halt. AFAIK, FreeBSD will always panic whenever it > > receives an NMI (unless possibly you specify the NMI_POWERFAIL option > > in your kernel config), so I simply turn off NMIs for correctable > > errors and leave the NMI on for non-correctable errors. That way > > FreeBSD will not panic when a correction has happened and it can carry > > on its merry business, but it will take the proper action by panicing > > when a non-correctable error has happened. > > I think 4.x doesn't panic on ECC NMI's anymore but I'm not sure. Out of curiosity, how does the OS know exactly what event triggered the NMI? I know what an NMI can mean, but I don't know what it REALLY IS, you know what I mean? The technical answer for exactly what an NMI is and what it consists of is welcome. :-) -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0101081828020.4671-100000>