From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 07:57:03 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFBC51065672 for ; Tue, 18 Oct 2011 07:57:03 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 42BC98FC16 for ; Tue, 18 Oct 2011 07:57:02 +0000 (UTC) Received: from ur.gsoft.com.au (Ur.gsoft.com.au [203.31.81.44]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id p9I7unqH056262 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Oct 2011 18:26:55 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=us-ascii From: "Daniel O'Connor" In-Reply-To: <20111018071941.GA9482@icarus.home.lan> Date: Tue, 18 Oct 2011 18:26:49 +1030 Content-Transfer-Encoding: quoted-printable Message-Id: <087BDDD7-0B16-4415-8D98-11FA617E03F5@gsoft.com.au> References: <20111001102327.GA37434@icarus.home.lan> <20111018071941.GA9482@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1244.3) X-Spam-Score: -4.391 () ALL_TRUSTED,BAYES_00,RP_MATCHES_RCVD X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: Thomas Zander , freebsd-stable Subject: Re: Interpreting MCA error output X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2011 07:57:03 -0000 On 18/10/2011, at 17:49, Jeremy Chadwick wrote: >> That would be absolutely helpful! After all, FreeBSD is primarily a >> server OS, and where would one have ECC if not on servers. Being able >> to determine what's wrong with memory would be certainly very = valuable >> for many admins. >=20 > This has been done, and it was committed a couple days ago as > sysutils/mcelog. There are a couple thing about the port which bother > me[1], and there is one warning which can be safely ignored (I'm a > strong advocate of -Werror) but I do have a fix for that, but = otherwise > it's functional. Do MCA log events cause anything in devd? It would be _super_ neat if the mcelog port installed a devd rule which = emailed root@ with the human readable version of an MCA exception :) I suspect this wouldn't be too difficult to do for a JKH. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C