Date: Sun, 08 Apr 2012 14:53:15 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> To: Nikolay Denev <ndenev@gmail.com> 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? Message-ID: <4F818A3B.5040904@quip.cz> In-Reply-To: <687BFFD7-1456-4D7B-AFB2-356EE9B0D1DD@gmail.com> References: <4F7ED7F4.5060509@zedat.fu-berlin.de> <687BFFD7-1456-4D7B-AFB2-356EE9B0D1DD@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F818A3B.5040904>