Machine-check exception

From ArchWiki
Revision as of 03:58, 16 November 2013 by Jstjohn (talk | contribs) (Running mcelog as a daemon: better use of templates)
Jump to: navigation, search

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: mentions rc.conf (Discuss in Talk:Machine-check exception#)

This article aims to help users implement services to actively monitor, log, and report hardware errors. A machine check exception (MCE) is an error generated by the CPU when the CPU detects that a hardware error or failure has occurred.


Machine check exceptions (MCEs) can occur for a variety of reasons ranging from undesired or out-of-spec voltages from the power supply, from cosmic radiation flipping bits in memory DIMMs or the CPU, or from other miscellaneous faults, including faulty software triggering hardware errors.

Installing mcelog

The mcelog daemon written by Andi Kleen is one of the tools one can use to gather MCE information.

Install the mcelog package from the official repositories.

Configuring mcelog

mcelog's configuration file is located at /etc/mcelog/mcelog.conf.

Running mcelog as a daemon

It is recommended by upstream to always run mcelog as a daemon, so edit /etc/mcelog/mcelog.conf and set daemon = yes.

Finally, use the /etc/rc.d/mcelog script to start mcelog at boot via /etc/rc.conf.

Note: If running mcelog via the rc.d command or via /etc/rc.conf, it is unnecessary to set daemon = yes in /etc/mcelog/mcelog.conf because /etc/rc.d/mcelog starts mcelog in daemon mode by default.

Additional configuration options

The following option is probably recommended:

syslog = yes

Hardware documentation from CPU manufacturers

See Also