Messages in this thread Patch in this message | | | From | Vitaly Mayatskikh <> | Subject | [PATCH 5/5] Document unknown_nmi_dump_log variable | Date | Wed, 2 Jun 2010 09:39:19 +0200 |
| |
Mention unknown_nmi_dump_log in sysctl documentation.
Signed-off-by: Vitaly Mayatskikh <v.mayatskih@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
| |