Commit 9f318e3f authored by Hidehiro Kawai's avatar Hidehiro Kawai Committed by Thomas Gleixner

Documentation: Document kernel.panic_on_io_nmi sysctl

kernel.panic_on_io_nmi sysctl was introduced by commit

  5211a242 ("x86: Add sysctl to allow panic on IOCK NMI error")

but its documentation is missing. So, add it.
Signed-off-by: default avatarHidehiro Kawai <>
Requested-by: default avatarBorislav Petkov <>
Cc: Andrew Morton <>
Cc: Baoquan He <>
Cc: Chris Metcalf <>
Cc: Don Zickus <>
Cc: "Eric W. Biederman" <>
Cc: Heinrich Schuchardt <>
Cc: "H. Peter Anvin" <>
Cc: Ingo Molnar <>
Cc: Jiri Kosina <>
Cc: Jonathan Corbet <>
Cc: Manfred Spraul <>
Cc: Masami Hiramatsu <>
Cc: Michal Hocko <>
Cc: Nicolas Iooss <>
Cc: Peter Zijlstra <>
Cc: Seth Jennings <>
Cc: Steven Rostedt <>
Cc: Thomas Gleixner <>
Cc: Ulrich Obergfell <>
Cc: Vivek Goyal <>
Cc: x86-ml <>
Link: default avatarBorislav Petkov <>
Signed-off-by: default avatarThomas Gleixner <>
parent b279d67d
......@@ -551,6 +551,21 @@ the recommended setting is 60.
Controls the kernel's behavior when a CPU receives an NMI caused by
an IO error.
0: try to continue operation (default)
1: panic immediately. The IO error triggered an NMI. This indicates a
serious system condition which could result in IO data corruption.
Rather than continuing, panicking might be a better choice. Some
servers issue this sort of NMI when the dump button is pushed,
and you can use this option to take a crash dump.
Controls the kernel's behaviour when an oops or BUG is encountered.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment