Date: Sat, 7 Apr 2012 09:00:51 +0300 From: Nikolay Denev <ndenev@gmail.com> To: O. Hartmann <ohartman@zedat.fu-berlin.de> Cc: freebsd-performance@freebsd.org, Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: ECC memory driver in FreeBSD 10? Message-ID: <687BFFD7-1456-4D7B-AFB2-356EE9B0D1DD@gmail.com> In-Reply-To: <4F7ED7F4.5060509@zedat.fu-berlin.de> References: <4F7ED7F4.5060509@zedat.fu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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. >=20 > Thanks in advance, > Oliver >=20 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?687BFFD7-1456-4D7B-AFB2-356EE9B0D1DD>