From owner-freebsd-performance@FreeBSD.ORG  Fri Apr  6 13:11:12 2012
Return-Path: <owner-freebsd-performance@FreeBSD.ORG>
Delivered-To: freebsd-performance@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 7D7721065673;
	Fri,  6 Apr 2012 13:11:12 +0000 (UTC)
	(envelope-from bruce@cran.org.uk)
Received: from muon.cran.org.uk (muon.cran.org.uk
	[IPv6:2a01:348:0:15:5d59:5c40:0:1])
	by mx1.freebsd.org (Postfix) with ESMTP id 09EF28FC12;
	Fri,  6 Apr 2012 13:11:12 +0000 (UTC)
Received: from muon.cran.org.uk (localhost [127.0.0.1])
	by muon.cran.org.uk (Postfix) with ESMTP id B2299E6475;
	Fri,  6 Apr 2012 14:11:03 +0100 (BST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=references
	:in-reply-to:mime-version:content-transfer-encoding:content-type
	:message-id:cc:from:subject:date:to; s=mail; bh=E79OtnrIbh7ecTgw
	ZZqquqpro18=; b=ggElfuWaCRhVwqf/NeGHaZ0naMzQZi2PUgnMYXB7mwV9sbiQ
	jsK6Cf8qosiAgEaSZjjLTVtToPbB63FBOm1QEelcw+NNYy4G0DroQ8CI93xEynmb
	Cy/rtBbKNnlIMXYVwfHFuzv1lxQtIFelRZ1XEHQxSKL67bWrsmOXr4+CvG8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=references
	:in-reply-to:mime-version:content-transfer-encoding:content-type
	:message-id:cc:from:subject:date:to; q=dns; s=mail; b=EU8MrIAsPc
	dima1zDAcuElxLwVYaXESlQggxX6A0cdTSUEPKlx6mUN1imBzq6ilnz81WwwH8Yx
	GZVBvMY6sAuteu4e1AlSaBnyrqkBTj+TGBF1hEwTTAf+EyavQixg/F9adzI0aGeV
	lfM0FdtwonFMQvG8SOBRoEdVMtUOarPUs=
Received: from [192.168.1.208] (188-220-36-32.zone11.bethere.co.uk
	[188.220.36.32]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by muon.cran.org.uk (Postfix) with ESMTPSA id 9AF03E6448;
	Fri,  6 Apr 2012 14:11:03 +0100 (BST)
References: <4F7ED7F4.5060509@zedat.fu-berlin.de>
In-Reply-To: <4F7ED7F4.5060509@zedat.fu-berlin.de>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <2355FE22-6725-4B7D-A56C-4FC0712022A7@cran.org.uk>
X-Mailer: iPad Mail (9B176)
From: Bruce Cran <bruce@cran.org.uk>
Date: Fri, 6 Apr 2012 14:11:03 +0100
To: "O. Hartmann" <ohartman@zedat.fu-berlin.de>
Cc: "freebsd-performance@freebsd.org" <freebsd-performance@freebsd.org>,
	Current FreeBSD <freebsd-current@freebsd.org>
Subject: Re: ECC memory driver in FreeBSD 10?
X-BeenThere: freebsd-performance@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Performance/tuning <freebsd-performance.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-performance>,
	<mailto:freebsd-performance-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-performance>
List-Post: <mailto:freebsd-performance@freebsd.org>
List-Help: <mailto:freebsd-performance-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-performance>,
	<mailto:freebsd-performance-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Apr 2012 13:11:12 -0000

On 6 Apr 2012, at 12:48, "O. Hartmann" <ohartman@zedat.fu-berlin.de> wrote:

> I'm looking for a way to force FreeBSD 10 to maintain/watch ECC errors
> reported by UEFI (or BIOS).
> Since ECC is said to be essential for server systems both in buisness
> and science and I do not question this, I was wondering if I can not
> report ECC errors via a watchdog or UEFI (ACPI?) report to syslog
> facility on FreeBSD.
> FreeBSD is supposed to be a server operating system, as far as I know,
> so I believe there must be something which didn't have revealed itself
> to me, yet.

FreeBSD logs ECC errors it finds (I don't know how but I doubt it's via the B=
IOS) by default: I had some RAM go bad a few months ago and messages appeare=
d in dmesg. Is there something in addition you need?

--=20
Bruce Cran=