From owner-freebsd-stable@FreeBSD.ORG  Mon Jun 26 23:44:01 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 156DD16A410
	for <freebsd-stable@freebsd.org>; Mon, 26 Jun 2006 23:44:01 +0000 (UTC)
	(envelope-from petefrench@ticketswitch.com)
Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1E6CF446BD
	for <freebsd-stable@freebsd.org>; Mon, 26 Jun 2006 23:26:27 +0000 (GMT)
	(envelope-from petefrench@ticketswitch.com)
Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk)
	by mail.ticketswitch.com with esmtp (Exim 4.60 (FreeBSD))
	(envelope-from <petefrench@ticketswitch.com>)
	id 1Fv0TK-000EjR-7S; Tue, 27 Jun 2006 00:26:26 +0100
Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim
	4.61 (FreeBSD)) (envelope-from <petefrench@ticketswitch.com>)
	id 1Fv0TK-000Pee-3t; Tue, 27 Jun 2006 00:26:26 +0100
To: M.Hirsch@gmx.de, M.Hirsch@hirsch.it
In-Reply-To: <44A0650C.7020806@gmx.de>
Message-Id: <E1Fv0TK-000Pee-3t@dilbert.firstcallgroup.co.uk>
From: Pete French <petefrench@ticketswitch.com>
Date: Tue, 27 Jun 2006 00:26:26 +0100
Cc: freebsd-stable@freebsd.org
Subject: Re: FreeBSD 6.x CVSUP today crashes with zero load ...
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jun 2006 23:44:01 -0000

> I am not looking for workarounds, like ECC. I want the box to break 
> immediately once any single component goes wrong...

Uh, that *is* what ECC does (or can do). Without ECC your broken hardware
continues to run un-noticed. With ECC you can either make it break
immediatley, or log an error or continue to run.

Stop thinking of ECC as error correction and start thinking of it as
error detection. No ECC gives you no way to detect failing memory.

-pete.