From owner-freebsd-stable Sun Jun 28 22:49:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11042 for freebsd-stable-outgoing; Sun, 28 Jun 1998 22:49:29 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11036 for ; Sun, 28 Jun 1998 22:49:24 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.8/8.7.3) with ESMTP id BAA02456; Mon, 29 Jun 1998 01:49:20 -0400 (EDT) Message-Id: <199806290549.BAA02456@whizzo.transsys.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Tom cc: "Michael R. Gile" , freebsd-stable@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: determining ecc errors on freebsd-stable References: In-reply-to: Your message of "Sun, 28 Jun 1998 19:57:26 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Jun 1998 01:49:20 -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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