From owner-freebsd-stable Sun Jun 28 17:05:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00825 for freebsd-stable-outgoing; Sun, 28 Jun 1998 17:05:03 -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 RAA00803 for ; Sun, 28 Jun 1998 17:04:51 -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 0yqRR6-0001VO-00; Sun, 28 Jun 1998 17:04:44 -0700 Date: Sun, 28 Jun 1998 17:04:41 -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: <199806282216.PAA16981@hub.freebsd.org> 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 have been some suggestions to my previous post about signal 10 errors > that it could be a memory problem. If this is the case, i would think that > the ecc controller would be correcting at least some of these problems. > Is there a way freebsd can be set to log the ecc corrections, like a sun > box does? If not, can someone point me to the necessary docs to add this? Most systems do not have ECC capable memory. All off the shelf consumer level computers certainly don't, though most can be upgraded by replaced the memory. 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. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message