From: Bernhard Walle <bwalle@suse.de>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
wim@iguana.be, stable@kernel.org, Thomas.Mingarelli@hp.com
Subject: Re: [PATCH] [WATCHDOG] Fix kdump when using hpwdt
Date: Tue, 25 Nov 2008 15:32:07 +0100 [thread overview]
Message-ID: <20081125153207.4f5ea2ac@hale.suse.de> (raw)
In-Reply-To: <20081125142751.GD341@redhat.com>
* Vivek Goyal [2008-11-25 09:27]:
>
> On Sun, Nov 23, 2008 at 02:15:24PM +0100, Bernhard Walle wrote:
> > When the "hpwdt" module is loaded (even if the /dev/watchdog device is not
> > opened), then kdump does not work. The panic kernel either does not start at
> > all or crash in various places.
> >
> > The problem is that hpwdt_pretimeout is registered with register_die_notifier()
> > with the highest possible priority. Because it returns NOTIFY_STOP, the
> > crash_nmi_callback which is also registered with register_die_notifier() is
> > never executed. This causes the shutdown of other CPUs to fail.
> >
> > Reverting the order is no option: The crash_nmi_callback executes HLT and so
> > never returns normally. Because of that, it must be executed as last notifier,
> > which currently is done.
> >
> > So, that patch returns NOTIFY_OK to keep the crash_nmi_callback executed.
>
> Hi Bernhard,
>
> Why does this handler need to run after a crash? IOW, even if kdump NMI
> handler halts the cpu, and this handler never gets a chance to run, is
> that an issue.
Hi Vivek,
Because otherwise the crashkernel receives NMIs and crashes ... it just
doesn't work. The watchdog guys should be able to provide technical
details here.
Regards,
Bernhard
next prev parent reply other threads:[~2008-11-25 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 13:15 [PATCH] [WATCHDOG] Fix kdump when using hpwdt Bernhard Walle
2008-11-25 14:27 ` Vivek Goyal
2008-11-25 14:32 ` Bernhard Walle [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-26 14:59 Bernhard Walle
2008-10-27 19:30 ` Wim Van Sebroeck
2008-10-27 21:52 ` Bernhard Walle
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=20081125153207.4f5ea2ac@hale.suse.de \
--to=bwalle@suse.de \
--cc=Thomas.Mingarelli@hp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=vgoyal@redhat.com \
--cc=wim@iguana.be \
/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