From owner-freebsd-current@FreeBSD.ORG Mon Apr 9 10:04:29 2012 Return-Path: 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 EF925106566B; Mon, 9 Apr 2012 10:04:29 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id A19068FC14; Mon, 9 Apr 2012 10:04:29 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1SHBSW-0006Ru-Ft>; Mon, 09 Apr 2012 12:04:28 +0200 Received: from e178034252.adsl.alicedsl.de ([85.178.34.252] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1SHBSW-0005xp-AU>; Mon, 09 Apr 2012 12:04:28 +0200 Message-ID: <4F82B42B.1050900@zedat.fu-berlin.de> Date: Mon, 09 Apr 2012 12:04:27 +0200 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.3) Gecko/20120314 Thunderbird/10.0.3 MIME-Version: 1.0 To: Miroslav Lachman <000.fbsd@quip.cz> References: <4F7ED7F4.5060509@zedat.fu-berlin.de> <687BFFD7-1456-4D7B-AFB2-356EE9B0D1DD@gmail.com> <4F818A3B.5040904@quip.cz> In-Reply-To: <4F818A3B.5040904@quip.cz> X-Enigmail-Version: 1.4 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig910C6AD7A324B09C21B3649A" X-Originating-IP: 85.178.34.252 Cc: Nikolay Denev , freebsd-performance@freebsd.org, Current FreeBSD 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 10:04:30 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig910C6AD7A324B09C21B3649A Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 04/08/12 14:53, schrieb Miroslav Lachman: > 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 error= s >>> 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 itsel= f >>> to me, yet. >=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=20 >> one with failing RAM module, and >> it reported the corrected ECC errors in dmesg. >=20 > 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. >=20 > Miroslav Lachman Seems that I have been blessed with non-faulty memory over tha past three or four years. Last time I saw errors was around 2000. All of our 24/7 servers do have ECC RAM. So, your replies all implies if I log the system's messages via syslog properly (as we do remotely on a centralized server), then ECC errors should be reported by FreeBSD/kernel in a canonical way as the UEFI/BIOS reports them? Without special drivers/tools, scripts which scans for those errors should report occurences? Since my (FreeBSD) boxes didn't show up errors of that kind - Linux boxes of a colleague did once! - doesn't imply missing capabilities. This is nice to hear/read. Thanks a lot, Oliver --------------enig910C6AD7A324B09C21B3649A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJPgrQrAAoJEOgBcD7A/5N8cF8H/1nYRUFkgGBpmOaMyS5ED1ij 7wqM4s0OiCsW7bzFxTj3/C3dushNefBcesdTSDmU/I8nks0197J8PPy7PSldqffB OvlpxxNKEJwO+kp8+iO3oAdu0QNKK8pLhoAaDeXPq8N/e0M2DpcjE6j2rnC0td/l sppKb9cKZKEoWBZ/3dc5DjyzO3oVxTrnxSwIFolF7EINHkADb80ka8vtjOHSqXIP M0CkQZA+hJPL+iHRK1Ab5Kw4Wq6/7tljPlo560U/nr9gW7XoPGH0lTXzcjGOMVuX FepjT6D7r1kf+k0zrmi/AyJy6NuLEqKXWprmEoYTXQZBqv6NdM+zcHImiwJNvds= =UYjv -----END PGP SIGNATURE----- --------------enig910C6AD7A324B09C21B3649A--