Date: Tue, 18 Oct 2011 00:19:41 -0700 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Thomas Zander <thomas.e.zander@googlemail.com> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Interpreting MCA error output Message-ID: <20111018071941.GA9482@icarus.home.lan> In-Reply-To: <CAFU734xHMugfW%2BZcO93OPqUEhJshYn-k%2B%2B3aGmcDVvGZVQ=s%2BQ@mail.gmail.com> References: <CAFU734y3WsVFTpnGoGfbPH4vVBnoz8f=qGvYS4c%2BLya8PFQP_A@mail.gmail.com> <20111001102327.GA37434@icarus.home.lan> <CAFU734xHMugfW%2BZcO93OPqUEhJshYn-k%2B%2B3aGmcDVvGZVQ=s%2BQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111018071941.GA9482>