Date: Tue, 18 Oct 2011 21:34:43 +0200 From: Thomas Zander <thomas.e.zander@googlemail.com> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Interpreting MCA error output Message-ID: <CAFU734xxiOetgG-fkMv6tEH9xSV-86WA%2Biz3MZJ8s7uyHL5C7Q@mail.gmail.com> In-Reply-To: <20111018071941.GA9482@icarus.home.lan> References: <CAFU734y3WsVFTpnGoGfbPH4vVBnoz8f=qGvYS4c%2BLya8PFQP_A@mail.gmail.com> <20111001102327.GA37434@icarus.home.lan> <CAFU734xHMugfW%2BZcO93OPqUEhJshYn-k%2B%2B3aGmcDVvGZVQ=s%2BQ@mail.gmail.com> <20111018071941.GA9482@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 18, 2011 at 09:19, Jeremy Chadwick <freebsd@jdc.parodius.com> w= rote: >> 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. =A0There 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. Awesome! Thanks, I will install and wait for the next mce to happen! Best regards Riggs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFU734xxiOetgG-fkMv6tEH9xSV-86WA%2Biz3MZJ8s7uyHL5C7Q>