From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 11:33:05 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 58B8E1065672 for ; Tue, 18 Oct 2011 11:33:05 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by mx1.freebsd.org (Postfix) with ESMTP id 031688FC12 for ; Tue, 18 Oct 2011 11:33:04 +0000 (UTC) Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta09.westchester.pa.mail.comcast.net with comcast id mBGE1h0041vXlb859BZ5Nv; Tue, 18 Oct 2011 11:33:05 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta17.westchester.pa.mail.comcast.net with comcast id mBZ31h00q1t3BNj3dBZ463; Tue, 18 Oct 2011 11:33:05 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 67635102C1C; Tue, 18 Oct 2011 04:33:02 -0700 (PDT) Date: Tue, 18 Oct 2011 04:33:02 -0700 From: Jeremy Chadwick To: Daniel O'Connor Message-ID: <20111018113302.GA14363@icarus.home.lan> References: <20111001102327.GA37434@icarus.home.lan> <20111018071941.GA9482@icarus.home.lan> <087BDDD7-0B16-4415-8D98-11FA617E03F5@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <087BDDD7-0B16-4415-8D98-11FA617E03F5@gsoft.com.au> User-Agent: Mutt/1.5.21 (2010-09-15) 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 11:33:05 -0000 On Tue, Oct 18, 2011 at 06:26:49PM +1030, Daniel O'Connor wrote: > 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. > > > > 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. Why? Most MCEs on FreeBSD will panic the machine. I would need to go through the MCA code to see what all gets handled elegantly, but I imagine there isn't much. Also, isn't devd for device removal/insertions? This would be using devd for something it isn't intended for. I guess I have "moral objections" to it. What you're really wanting is Solaris's fmd(1m) daemon, which I believe is also tied heavily into Solaris's smf(5) architecture. http://download.oracle.com/docs/cd/E19963-01/html/821-1462/fmd-1m.html -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |