From owner-freebsd-performance@FreeBSD.ORG Sat Apr 7 06:00:56 2012 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CE2A8106567C; Sat, 7 Apr 2012 06:00:56 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 2F1958FC12; Sat, 7 Apr 2012 06:00:56 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so2673042wgb.31 for ; Fri, 06 Apr 2012 23:00:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=xYYzQckSuIme8bCQ/iDHIJoD8CJu2Ab/Zfe+4F2C+Lg=; b=m/EuCTO+cXpS/cd1rqtcIMupRLGaE4azPXanhT5lqUUXxJVRW1wOinYeySjDwdotg9 q0uZJFLAs5pSIUarTg02PM2fk+V8+VOQXNk04QVBGjnHr5sR8HKyBD+8uzJ/bTji6J0A wp5idFmRKEZUFcYiPIiOD/gkdizztd7SfQ7KnINZTW3tWNkCt+D+lBt3Uu1aFgj6G9mB 3H2y8lxkDzmV+xMMlLDj4Woxj+zC0jhivTMw9Q8/phpURxDQbUGMLr5Qd6j15R5Iwv0R glUGlKUwlnwLj6T+lllYIZS9gliURzOGew1omplmRACeLzmnCxo3n/kORbM9LYcTKTd1 KtyQ== Received: by 10.216.134.136 with SMTP id s8mr309358wei.6.1333778455324; Fri, 06 Apr 2012 23:00:55 -0700 (PDT) Received: from imba-brutale.totalterror.net ([93.152.152.135]) by mx.google.com with ESMTPS id ff2sm19747422wib.9.2012.04.06.23.00.53 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 06 Apr 2012 23:00:54 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=us-ascii From: Nikolay Denev In-Reply-To: <4F7ED7F4.5060509@zedat.fu-berlin.de> Date: Sat, 7 Apr 2012 09:00:51 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <687BFFD7-1456-4D7B-AFB2-356EE9B0D1DD@gmail.com> References: <4F7ED7F4.5060509@zedat.fu-berlin.de> To: O. Hartmann X-Mailer: Apple Mail (2.1257) X-Mailman-Approved-At: Sat, 07 Apr 2012 10:54:53 +0000 Cc: freebsd-performance@freebsd.org, Current FreeBSD Subject: Re: ECC memory driver in FreeBSD 10? X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Apr 2012 06:00:56 -0000 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.