Date: Fri, 6 Apr 2012 14:11:03 +0100 From: Bruce Cran <bruce@cran.org.uk> 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? Message-ID: <2355FE22-6725-4B7D-A56C-4FC0712022A7@cran.org.uk> 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 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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2355FE22-6725-4B7D-A56C-4FC0712022A7>