From owner-freebsd-stable  Mon Jun 29 22:33:33 1998
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA03492
          for freebsd-stable-outgoing; Mon, 29 Jun 1998 22:33:33 -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 WAA03466
          for <stable@freebsd.org>; Mon, 29 Jun 1998 22:33:18 -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 0yqt2W-0005Mb-00; Mon, 29 Jun 1998 22:33:12 -0700
Date: Mon, 29 Jun 1998 22:33:08 -0700 (PDT)
From: Tom <tom@uniserve.com>
X-Sender: tom@shell.uniserve.ca
To: Leo Papandreou <leo@talcom.net>
cc: stable@FreeBSD.ORG
Subject: Re: determining ecc errors on freebsd-stable
In-Reply-To: <19980629184220.15472@supersex.com>
Message-ID: <Pine.BSF.3.96.980629223112.1069B-100000@shell.uniserve.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Mon, 29 Jun 1998, Leo Papandreou wrote:

> On Mon, Jun 29, 1998 at 08:42:31AM -0700, Tom wrote:
> > 
> >   Summary:
> > 
> > - ECC is MUCH better than non-ECC
> 
> Will ECC on the cache trap RAM errors even if the RAM doesnt
> have ECC?

  No.  ECC on cache only protects the data that has made it the cache.

  Hopefully your internal bus between cache and CPU also support ECC!
Basically all data paths need protection to cover all the bases.

Tom


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message