Interpreting MCA error output

Daniel O'Connor doconnor at gsoft.com.au
Tue Oct 18 13:01:50 UTC 2011


On 18/10/2011, at 22:03, Jeremy Chadwick wrote:
>> 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.
> 
> Why?  Most MCEs on FreeBSD will panic the machine.  I would need to go
> through the MCA code to see what all gets handled elegantly, but I
> imagine there isn't much.

If you see an MCA in your log file it didn't panic your machine, I think they're not uncommon.

> Also, isn't devd for device removal/insertions?  This would be using
> devd for something it isn't intended for.  I guess I have "moral
> objections" to it.  What you're really wanting is Solaris's fmd(1m)
> daemon, which I believe is also tied heavily into Solaris's smf(5)
> architecture.

I always thought devd was a fairly general event notification thing.

--
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








More information about the freebsd-stable mailing list