From owner-freebsd-current@FreeBSD.ORG  Sun Apr  8 13:00:33 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 22F671065677;
	Sun,  8 Apr 2012 13:00:32 +0000 (UTC)
	(envelope-from 000.fbsd@quip.cz)
Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4])
	by mx1.freebsd.org (Postfix) with ESMTP id D73C48FC08;
	Sun,  8 Apr 2012 13:00:22 +0000 (UTC)
Received: from elsa.codelab.cz (localhost [127.0.0.1])
	by elsa.codelab.cz (Postfix) with ESMTP id 9219A2842D;
	Sun,  8 Apr 2012 14:53:16 +0200 (CEST)
Received: from [192.168.1.2] (static-84-242-120-26.net.upcbroadband.cz
	[84.242.120.26])
	(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
	(No client certificate requested)
	by elsa.codelab.cz (Postfix) with ESMTPSA id B8A8028426;
	Sun,  8 Apr 2012 14:53:15 +0200 (CEST)
Message-ID: <4F818A3B.5040904@quip.cz>
Date: Sun, 08 Apr 2012 14:53:15 +0200
From: Miroslav Lachman <000.fbsd@quip.cz>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14
MIME-Version: 1.0
To: Nikolay Denev <ndenev@gmail.com>
References: <4F7ED7F4.5060509@zedat.fu-berlin.de>
	<687BFFD7-1456-4D7B-AFB2-356EE9B0D1DD@gmail.com>
In-Reply-To: <687BFFD7-1456-4D7B-AFB2-356EE9B0D1DD@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-performance@freebsd.org,
	Current FreeBSD <freebsd-current@freebsd.org>,
	"O. Hartmann" <ohartman@zedat.fu-berlin.de>
Subject: Re: ECC memory driver in FreeBSD 10?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Apr 2012 13:00:33 -0000

Nikolay Denev wrote:
> On Apr 6, 2012, at 2:48 PM, O. Hartmann 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.

>
> If the hardware supports it, such errors should be logged as MCEs (Machine Check Exceptions).
> I can say for sure it works pretty well with Dell servers, as I had  one with failing RAM module, and
> it reported the corrected ECC errors in dmesg.

Memory ECC errors are logged in to messages and you can decode it by 
sysutils/mcelog. I did it in the past on one of our Sun Fire X2100 M2 
with FreeBSD 8.x.

Miroslav Lachman