From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 13:45:43 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 96EA4106566C for ; Tue, 18 Oct 2011 13:45:43 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id 7909A8FC18 for ; Tue, 18 Oct 2011 13:45:43 +0000 (UTC) Received: from omta19.emeryville.ca.mail.comcast.net ([76.96.30.76]) by qmta06.emeryville.ca.mail.comcast.net with comcast id mDWP1h0051eYJf8A6DlcPY; Tue, 18 Oct 2011 13:45:36 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta19.emeryville.ca.mail.comcast.net with comcast id mDUA1h00C1t3BNj01DUAXn; Tue, 18 Oct 2011 13:28:12 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id A514D102C1C; Tue, 18 Oct 2011 06:45:37 -0700 (PDT) Date: Tue, 18 Oct 2011 06:45:37 -0700 From: Jeremy Chadwick To: Daniel O'Connor Message-ID: <20111018134537.GA16543@icarus.home.lan> References: <20111001102327.GA37434@icarus.home.lan> <20111018071941.GA9482@icarus.home.lan> <087BDDD7-0B16-4415-8D98-11FA617E03F5@gsoft.com.au> <20111018113302.GA14363@icarus.home.lan> <59140016-4530-4343-9C30-CA9B16E9EEBD@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <59140016-4530-4343-9C30-CA9B16E9EEBD@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 13:45:43 -0000 On Tue, Oct 18, 2011 at 11:31:37PM +1030, Daniel O'Connor wrote: > > On 18/10/2011, at 22:03, Jeremy Chadwick wrote: > >> 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. > > If you see an MCA in your log file it didn't panic your machine, I think they're not uncommon. But that's already logged in /var/log/messages. So I guess we're at a standstill? > > 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. > > I always thought devd was a fairly general event notification thing. Possibly you should read devd(8), and after that, definitely look at devctl(4). The latter specifically is for devices. MCA is not a device (or rather, it is not implemented as a device framework on FreeBSD). Truly what you're looking for is Solaris fmd(1m). It's a "generic event notification thing" that handles all sorts of events, ranging from physical device additions/removals, to ZFS pool failures, to MCEs -- and it doesn't stop there. Porting fmd(1m) to FreeBSD would be a wonderful, yet fairly intensive, GSoC project. Note that just blindly porting fmd(1m) wouldn't add all the necessary shims in other pieces to notify fmd of an event, that would have to be coded (added) over time. -- | 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 |