diff options
| author | Paul Bolle <pebolle@tiscali.nl> | 2014-07-12 09:54:52 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2014-07-12 11:30:36 -0700 |
| commit | c8c3f7d621c1dd803e92d4cdd59e2f730be71a2b (patch) | |
| tree | d508955460606ca43e090a241455b1fc455ff54b /Documentation/Changes | |
| parent | 47ea8dd8710ba32391b729c95bea005b6fd86243 (diff) | |
| download | linux-0-day-c8c3f7d621c1dd803e92d4cdd59e2f730be71a2b.tar.gz linux-0-day-c8c3f7d621c1dd803e92d4cdd59e2f730be71a2b.tar.xz | |
Documentation/Changes: clean up mcelog paragraph
The paragraph on mcelog currently describes kernel v2.6.31. In that
kernel the mce code (for i386, that is) was in transition. Ever since
v2.6.32 the situation is much simpler (eg, mcelog is now needed to
process events on almost all x86 machines, i386 and x86-64). Since this
"document is designed to provide a list of the minimum levels of
software necessary to run the 3.0 kernels" let's just describe that
situation.
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Acked-by: Andi Kleen <ak@linux.intel.com>
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/Changes')
| -rw-r--r-- | Documentation/Changes | 9 |
1 files changed, 3 insertions, 6 deletions
diff --git a/Documentation/Changes b/Documentation/Changes index 2254db0f00a52..227bec88021e5 100644 --- a/Documentation/Changes +++ b/Documentation/Changes @@ -280,12 +280,9 @@ that is possible. mcelog ------ -In Linux 2.6.31+ the i386 kernel needs to run the mcelog utility -as a regular cronjob similar to the x86-64 kernel to process and log -machine check events when CONFIG_X86_NEW_MCE is enabled. Machine check -events are errors reported by the CPU. Processing them is strongly encouraged. -All x86-64 kernels since 2.6.4 require the mcelog utility to -process machine checks. +On x86 kernels the mcelog utility is needed to process and log machine check +events when CONFIG_X86_MCE is enabled. Machine check events are errors reported +by the CPU. Processing them is strongly encouraged. Getting updated software ======================== |