Difference between revisions of "Machine-check exception"

From ArchWiki
Jump to: navigation, search
(added example /etc/mcelog.conf; added basic config information; added mcelog references link)
(moved daemon config stuff to its own section; added info on /etc/rc.conf; moved extra config options to its own sub-section)
Line 10: Line 10:
  
 
==Installing mcelog==
 
==Installing mcelog==
The [http://www.mcelog.org/ mcelog] daemon written by Andi Kleen is one of the methods in which one can handle MCEs. The {{Package Official|mcelog}} daemon can be found in the {{Codeline|[community]}} repository and be installed with [[pacman]].
+
The [http://www.mcelog.org/ mcelog] daemon written by Andi Kleen is one of the methods in which one can handle MCEs. The {{Package Official|mcelog}} daemon can be found in the {{Codeline|[community]}} repository and can be installed with [[pacman]].
 
  pacman -S mcelog
 
  pacman -S mcelog
  
Line 21: Line 21:
 
  chown root:root /etc/mcelog.conf
 
  chown root:root /etc/mcelog.conf
  
 +
===Running mcelog as a daemon===
 
It is recommended by upstream to always run mcelog as a daemon, so edit {{Filename|/etc/mcelog.conf}} and set {{Codeline|daemon <nowiki>=</nowiki> yes}}.
 
It is recommended by upstream to always run mcelog as a daemon, so edit {{Filename|/etc/mcelog.conf}} and set {{Codeline|daemon <nowiki>=</nowiki> yes}}.
  
Additionally, the following options are probably recommended:
+
Finally, {{Codeline|mcelog}} needs to be added to the {{Codeline|DAEMONS}} array in {{Filename|/etc/rc.conf}}.
 +
 
 +
===Additional configuration options===
 +
The following options are probably recommended:
 
  syslog = yes
 
  syslog = yes
 
  syslog-error = yes
 
  syslog-error = yes

Revision as of 04:38, 30 September 2011


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.

Introduction

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 from other miscellaneous faults, including faulty software triggering hardware errors.

Installing mcelog

The mcelog daemon written by Andi Kleen is one of the methods in which one can handle MCEs. The Template:Package Official daemon can be found in the Template:Codeline repository and can be installed with pacman.

pacman -S mcelog

Configuring mcelog

mcelog's configuration file is supposed to be located at Template:Filename, but as of 2011-09-29, that file is not created after running Template:Codeline.

Copy the example Template:Filename file from here: [#Example /etc/mcelog.conf].

Make sure the file is owned by root:root.

chown root:root /etc/mcelog.conf

Running mcelog as a daemon

It is recommended by upstream to always run mcelog as a daemon, so edit Template:Filename and set Template:Codeline.

Finally, Template:Codeline needs to be added to the Template:Codeline array in Template:Filename.

Additional configuration options

The following options are probably recommended:

syslog = yes
syslog-error = yes
socket-path = /var/run/mcelog-client

Example /etc/mcelog.conf

As of 2011-09-29, the Template:Package Official package from Template:Codeline does not generate a default/example configuration file at Template:Filename. The example configuration file from upstream (as of 2011-09-29) can be found below for reference:

Template:File

Hardware documentation from CPU manufacturers

See Also