Date: Tue, 9 Jan 2001 12:18:14 -0600 (CST) From: Chris Dillon <cdillon@wolves.k12.mo.us> To: John Baldwin <jhb@FreeBSD.org> Cc: "Daniel O'Connor" <doconnor@gsoft.com.au>, 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.0101091210590.15567-100000@mail.wolves.k12.mo.us> In-Reply-To: <XFMail.010109094832.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 9 Jan 2001, John Baldwin wrote: > > So, if I understand what is in isa_nmi() correctly, it should be > > possible to find out which NMIs a particular chipset is going to throw > > when a correctable ECC error has ocurred, and when a non-correctable > > error has ocurred. I also assume there is no "standard" for this, or > > we would have already done it. :-) > > This is correct. :) There does not seem to be a standard > unfortunately, though I do think that Paul Saab (ps@FreeBSD.org) > has been working on this some. It LOOKS simple enough, but looks are always deceiving. I'll take a shot at it if someone can point me at some documentation for the Intel 440BX and the RCC ServerWorks chipsets (hopefully NOT under NDA), which are the two chipsets I use in most of my FreeBSD boxen. I'll nose around on Intel's developer site and on the ServerWorks site to see if they have any info. I can already forsee one problem, though... How would I TEST it? I don't have any flaky ECC memory lying around. :-) -- 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.0101091210590.15567-100000>