From owner-freebsd-stable@FreeBSD.ORG Tue Oct 18 07:19: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 D8BF6106564A for ; Tue, 18 Oct 2011 07:19:43 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by mx1.freebsd.org (Postfix) with ESMTP id 819568FC0A for ; Tue, 18 Oct 2011 07:19:43 +0000 (UTC) Received: from omta10.westchester.pa.mail.comcast.net ([76.96.62.28]) by qmta14.westchester.pa.mail.comcast.net with comcast id m7JQ1h0020cZkys5E7Kj1e; Tue, 18 Oct 2011 07:19:43 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta10.westchester.pa.mail.comcast.net with comcast id m7Ki1h00G1t3BNj3W7Kj26; Tue, 18 Oct 2011 07:19:43 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 8AB2D102C1C; Tue, 18 Oct 2011 00:19:41 -0700 (PDT) Date: Tue, 18 Oct 2011 00:19:41 -0700 From: Jeremy Chadwick To: Thomas Zander Message-ID: <20111018071941.GA9482@icarus.home.lan> References: <20111001102327.GA37434@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: 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:19:43 -0000 On Sun, Oct 02, 2011 at 09:37:43AM +0200, Thomas Zander wrote: > > I should really work with John to make mcelog a FreeBSD port and just > > regularly update it with patches, etc. to work on FreeBSD. ?DMI support > > and so on I don't think can be added (at least not by me), but simple > > ASCII decoding? ?Very possible. > > 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. Give it a try for yourself and see if it suffices. [1]: The committer changed a bunch of things which were labelled "minor" yet bother me enough that I'm forcing the OCD part of me to let them slide. -- | 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 |