Prev: RFC: Regulator Framework Voltage Setting
Next: [ANNOUNCE] Cworthy Libraries for Linux Kernel Utils
From: Vitaly Mayatskikh on 2 Jun 2010 05:50
Mention unknown_nmi_dump_log in sysctl documentation.

Signed-off-by: Vitaly Mayatskikh <v.mayatskih(a)gmail.com>
---
Documentation/sysctl/kernel.txt | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)

diff --git a/Documentation/sysctl/kernel.txt b/Documentation/sysctl/kernel.txt
index 3894eaa..b554838 100644
--- a/Documentation/sysctl/kernel.txt
+++ b/Documentation/sysctl/kernel.txt
@@ -65,6 +65,7 @@ show up in /proc/sys/kernel:
- tainted
- threads-max
- unknown_nmi_panic
+- unknown_nmi_dump_log
- version

==============================================================
@@ -515,6 +516,15 @@ If a system hangs up, try pressing the NMI switch.

==============================================================

+unknown_nmi_dump_log:
+
+The value in this file affects behavior of handling NMI. When dump
+capture kernel is loaded, the value is non-zero and unknown NMI is
+trapped, then vmcore's log buffer and CPU registers are extracted and
+displayed on console.
+
+==============================================================
+
panic_on_unrecovered_nmi:

The default Linux behaviour on an NMI of either memory or unknown is to continue
--
1.7.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: RFC: Regulator Framework Voltage Setting
Next: [ANNOUNCE] Cworthy Libraries for Linux Kernel Utils