Date: Tue, 18 Oct 2011 18:26:49 +1030 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: Thomas Zander <thomas.e.zander@googlemail.com>, freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Interpreting MCA error output Message-ID: <087BDDD7-0B16-4415-8D98-11FA617E03F5@gsoft.com.au> 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 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. >=20 > 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. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?087BDDD7-0B16-4415-8D98-11FA617E03F5>