Difference between revisions of "Machine-check exception"

From ArchWiki
Jump to: navigation, search
(Installing mcelog: reworded first sentence; improved formatting of "official repositories")
(Hardware documentation from CPU manufacturers: fixed broken link to the APM, Volume 2; removed link rot tag)
Line 29: Line 29:
==Hardware documentation from CPU manufacturers==
==Hardware documentation from CPU manufacturers==
* [http://support.amd.com/us/Processor_TechDocs/24593.pdf AMD64 Architecture Programmer's Manual, Volume 2: System Programming]{{Linkrot|2011|10|14}}
* [http://support.amd.com/us/Processor_TechDocs/APM_v2_24593.pdf AMD64 Architecture Programmer's Manual, Volume 2: System Programming]
* [http://support.amd.com/us/Processor_TechDocs/26094.pdf BIOS and Kernel Developer's Guide for AMD Athlon™ 64 and AMD Opteron™ Processors]
* [http://support.amd.com/us/Processor_TechDocs/26094.PDF BIOS and Kernel Developer's Guide for AMD Athlon™ 64 and AMD Opteron™ Processors]
==See Also==
==See Also==

Revision as of 04:21, 24 October 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.


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 tools one can use to gather MCE information.

You can install Template:Package Official from the official repositories.

Configuring mcelog

mcelog's configuration file is located at Template:Filename.

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.

Note: If running mcelog via the Template:Codeline command or the Template:Codeline array in Template:Filename, it is unnecessary to set Template:Codeline in Template:Filename because Template:Filename starts mcelog in daemon mode by default.

Additional configuration options

The following options are probably recommended:

syslog = yes

Hardware documentation from CPU manufacturers

See Also