Re: Interpreting MCA error output

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

_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"