diff options
author | Jean-Yves Faye <jean-yves.faye@c-s.fr> | 2015-09-29 05:39:19 -0400 |
---|---|---|
committer | Corey Minyard <cminyard@mvista.com> | 2015-11-16 07:28:43 -0500 |
commit | c7f42c63901b964833eb23a9bda873b799e7f308 (patch) | |
tree | 6ceaa67dae7e317c83c2b4434c9c75bc68d1e55f /Documentation/IPMI.txt | |
parent | 66f44018300c5e6f53c9d30d6920332cf0e6a8f9 (diff) |
ipmi watchdog : add panic_wdt_timeout parameter
In order to allow panic actions to be processed, the ipmi watchdog
driver sets a new timeout value on panic. The 255s timeout
was designed to allow kdump and others actions on panic, as in
http://lkml.iu.edu/hypermail/linux/kernel/0711.3/0258.html
This is counter-intuitive for a end-user who sets watchdog timeout
value to something like 30s and who expects BMC to reset the system
within 30s of a panic.
This commit allows user to configure the timeout on panic.
Signed-off-by: Jean-Yves Faye <jean-yves.faye@c-s.fr>
Signed-off-by: Corey Minyard <cminyard@mvista.com>
Diffstat (limited to 'Documentation/IPMI.txt')
-rw-r--r-- | Documentation/IPMI.txt | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/Documentation/IPMI.txt b/Documentation/IPMI.txt index 31d1d658827f..c0d8788e75d3 100644 --- a/Documentation/IPMI.txt +++ b/Documentation/IPMI.txt | |||
@@ -587,7 +587,7 @@ used to control it: | |||
587 | 587 | ||
588 | modprobe ipmi_watchdog timeout=<t> pretimeout=<t> action=<action type> | 588 | modprobe ipmi_watchdog timeout=<t> pretimeout=<t> action=<action type> |
589 | preaction=<preaction type> preop=<preop type> start_now=x | 589 | preaction=<preaction type> preop=<preop type> start_now=x |
590 | nowayout=x ifnum_to_use=n | 590 | nowayout=x ifnum_to_use=n panic_wdt_timeout=<t> |
591 | 591 | ||
592 | ifnum_to_use specifies which interface the watchdog timer should use. | 592 | ifnum_to_use specifies which interface the watchdog timer should use. |
593 | The default is -1, which means to pick the first one registered. | 593 | The default is -1, which means to pick the first one registered. |
@@ -597,7 +597,9 @@ is the amount of seconds before the reset that the pre-timeout panic will | |||
597 | occur (if pretimeout is zero, then pretimeout will not be enabled). Note | 597 | occur (if pretimeout is zero, then pretimeout will not be enabled). Note |
598 | that the pretimeout is the time before the final timeout. So if the | 598 | that the pretimeout is the time before the final timeout. So if the |
599 | timeout is 50 seconds and the pretimeout is 10 seconds, then the pretimeout | 599 | timeout is 50 seconds and the pretimeout is 10 seconds, then the pretimeout |
600 | will occur in 40 second (10 seconds before the timeout). | 600 | will occur in 40 second (10 seconds before the timeout). The panic_wdt_timeout |
601 | is the value of timeout which is set on kernel panic, in order to let actions | ||
602 | such as kdump to occur during panic. | ||
601 | 603 | ||
602 | The action may be "reset", "power_cycle", or "power_off", and | 604 | The action may be "reset", "power_cycle", or "power_off", and |
603 | specifies what to do when the timer times out, and defaults to | 605 | specifies what to do when the timer times out, and defaults to |
@@ -634,6 +636,7 @@ for configuring the watchdog: | |||
634 | ipmi_watchdog.preop=<preop type> | 636 | ipmi_watchdog.preop=<preop type> |
635 | ipmi_watchdog.start_now=x | 637 | ipmi_watchdog.start_now=x |
636 | ipmi_watchdog.nowayout=x | 638 | ipmi_watchdog.nowayout=x |
639 | ipmi_watchdog.panic_wdt_timeout=<t> | ||
637 | 640 | ||
638 | The options are the same as the module parameter options. | 641 | The options are the same as the module parameter options. |
639 | 642 | ||