Date: Mon, 29 Jun 1998 01:49:20 -0400 From: "Louis A. Mamakos" <louie@TransSys.COM> To: Tom <tom@uniserve.com> Cc: "Michael R. Gile" <gilem@wsg.net>, freebsd-stable@FreeBSD.ORG Subject: Re: determining ecc errors on freebsd-stable Message-ID: <199806290549.BAA02456@whizzo.transsys.com> In-Reply-To: Your message of "Sun, 28 Jun 1998 19:57:26 PDT." <Pine.BSF.3.96.980628195504.22006A-100000@shell.uniserve.ca> References: <Pine.BSF.3.96.980628195504.22006A-100000@shell.uniserve.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
> > On Sun, 28 Jun 1998, Michael R. Gile wrote: > > > > There is no way to log ECC corrections are they are done > > >transparently in the hardware, and currently there is no mechanism for the > > >hardware to make available that kind of info. > > > > there must be some status register that records these errors. Otherwise what > > good is ECC? If it doesn't tell you that something is wrong, then it is useless > > Either ECC fixes the error, or if the error is unfixable, the hardware > generates a NMI which will cause a panic and reboot. > > Basically, if a fixable error occurs, you won't know about it. If an > unfixable error occurs, you'll know real fast. Well, geez, it would be nice to know that you had bum memory in the machine so you could replace it at some time of your choosing. ECC memory ought to be better than just having your system crash later rather than sooner. This is the kind of thing that seperates toy computers from robust, has to be up no matter what mission critical computers. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806290549.BAA02456>