From: Andrew Morton <akpm@linux-foundation.org>
To: youquan_song@linux.intel.com
Cc: linux-kernel@vger.kernel.org, Corey Minyard <minyard@acm.org>,
Wim Van Sebroeck <wim@iguana.be>
Subject: Re: ipmi_watchdog can not reset the kernel panic machine
Date: Sat, 24 Nov 2007 22:39:20 -0800 [thread overview]
Message-ID: <20071124223920.212b36e3.akpm@linux-foundation.org> (raw)
In-Reply-To: <2097.172.16.96.111.1195878521.squirrel@linux.intel.com>
(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;
> }
next prev parent reply other threads:[~2007-11-25 6:40 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 [this message]
2007-11-25 23:26 ` Corey Minyard
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=20071124223920.212b36e3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.