From owner-freebsd-stable Sun Jun 28 19:57:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22242 for freebsd-stable-outgoing; Sun, 28 Jun 1998 19:57:35 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA22237 for ; Sun, 28 Jun 1998 19:57:32 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yqU8H-0004Dq-00; Sun, 28 Jun 1998 19:57:29 -0700 Date: Sun, 28 Jun 1998 19:57:26 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "Michael R. Gile" cc: freebsd-stable@FreeBSD.ORG Subject: Re: determining ecc errors on freebsd-stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message