Difference between revisions of "mcelog"

From Noah.org
Jump to navigationJump to search
m
m
Line 1: Line 1:
 
[[Category:Engineering]]
 
[[Category:Engineering]]
  
Note that the '''mcelog''' is poorly supported in many distros. An alternative is the [http://sourceforge.net/projects/bluesmoke/ EDAC] project.
+
Note that the '''mcelog''' is poorly supported in many distros. An alternative is the [http://sourceforge.net/projects/bluesmoke/ EDAC] project, which is part of the mainstream Linux kernel, and [http://sourceforge.net/projects/edac-utils/ edac-utils]. See also [[EDAC]].
  
 
Machine Checked Exceptions (MCE) are errors raised by the CPU to notify problems such as CPU cache faults, bus errors, and ECC parity errors in RAM memory modules. By default, MCE errors are not actually logged anywhere by the kernel. The Linux kernel makes these errors visible in userspace through a character device. For this to be useful a daemon is needed to log exceptions reported through this device. The '''mcelog''' package performs the task of copying any MCE errors to a log file.
 
Machine Checked Exceptions (MCE) are errors raised by the CPU to notify problems such as CPU cache faults, bus errors, and ECC parity errors in RAM memory modules. By default, MCE errors are not actually logged anywhere by the kernel. The Linux kernel makes these errors visible in userspace through a character device. For this to be useful a daemon is needed to log exceptions reported through this device. The '''mcelog''' package performs the task of copying any MCE errors to a log file.

Revision as of 06:10, 11 January 2014


Note that the mcelog is poorly supported in many distros. An alternative is the EDAC project, which is part of the mainstream Linux kernel, and edac-utils. See also EDAC.

Machine Checked Exceptions (MCE) are errors raised by the CPU to notify problems such as CPU cache faults, bus errors, and ECC parity errors in RAM memory modules. By default, MCE errors are not actually logged anywhere by the kernel. The Linux kernel makes these errors visible in userspace through a character device. For this to be useful a daemon is needed to log exceptions reported through this device. The mcelog package performs the task of copying any MCE errors to a log file.

If you install the mcelog package and see this message, /dev/mcelog not active, it means that you did not create the device. In some systems this is done automatically by udev, but in other systems you must create it manually.

mknod /dev/mcelog c 10 227

See also http://en.wikipedia.org/wiki/Machine_Check_Exception