From: Corey Minyard <minyard@acm.org>
To: youquan_song@linux.intel.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Wim Van Sebroeck <wim@iguana.be>
Subject: Re: ipmi_watchdog can not reset the kernel panic machine
Date: Sun, 25 Nov 2007 17:26:27 -0600 [thread overview]
Message-ID: <474A04A3.8030702@acm.org> (raw)
In-Reply-To: <20071124223920.212b36e3.akpm@linux-foundation.org>
The watchdog is "off" by default, meaning that you have to have
something actually start resetting the watchdog before it will start
running. That's why you are seeing this behavior.
There is a start_now option that will start the watchdog when it is
loaded, but then it will reset the system unless something resets the
watchdog periodically, and you have a limited time to start this operation.
On a panic, the IPMI driver attempts to preserve the state of the
watchdog and (if running) increase the timeout time to allow a kdump or
something like that to occur. That's the purpose of the code you
reference. It is not to start a reset operation on any panic. It used
to start a reset on every panic, but that cause problems for many users.
-corey
Andrew Morton wrote:
> (cc's added)
>
> On Fri, 23 Nov 2007 20:28:41 -0800 (PST) youquan_song@linux.intel.com wrote:
>
>
>> Build kernel-2.6.24-rc3. pmi_watchdog can not reset the kernel panic
>> machine. The watchdog can never to record panic information to IPMI SEL.
>>
>> 1. I disable auto reset when kernel panic by echo "0" >
>> /proc/sys/kernel/panic
>>
>> 2. modprobe ipmi_watchdog timeout=120 action=reset
>>
>> 3. Load a driver, the driver will call panic() when ioctl to call into
>> the driver.
>>
>> 4. By ioctl call into the driver, panic the system.
>>
>> in wdog_panic_handler, I printk "ipmi_watchdog_state=WDOG_TIMEOUT_NONE"
>> so, the watchdog can never to record panic information to IPMI SEL.
>>
>>
>> static int wdog_panic_handler(struct notifier_block *this,
>> unsigned long event,
>> void *unused)
>> {
>> static int panic_event_handled = 0;
>>
>> /* On a panic, if we have a panic timeout, make sure to extend
>> the watchdog timer to a reasonable value to complete the
>> panic, if the watchdog timer is running. Plus the
>> pretimeout is meaningless at panic time. */
>> if (watchdog_user && !panic_event_handled &&
>> ipmi_watchdog_state != WDOG_TIMEOUT_NONE) {
>> /* Make sure we do this only once. */
>> panic_event_handled = 1;
>>
>> timeout = 255;
>> pretimeout = 0;
>> panic_halt_ipmi_set_timeout();
>> }
>>
>> return NOTIFY_OK;
>> }
>>
prev parent reply other threads:[~2007-11-26 0:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 4:28 ipmi_watchdog can not reset the kernel panic machine youquan_song
2007-11-25 6:39 ` Andrew Morton
2007-11-25 23:26 ` Corey Minyard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=474A04A3.8030702@acm.org \
--to=minyard@acm.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wim@iguana.be \
--cc=youquan_song@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox