From: Chris Friesen <chris.friesen@genband.com>
To: Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>,
Wim Van Sebroeck <wim@iguana.be>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RFC: generic support for two-stage watchdogs?
Date: Thu, 28 Jul 2011 11:08:17 -0600 [thread overview]
Message-ID: <4E319781.9000405@genband.com> (raw)
When using kdump to store crash recovery information, it is frustrating
when the watchdog timer fires and reboots the system under our feet.
Many hardware watchdogs support a two-stage operation where the initial
stage expires and sends an NMI or other interrupt to the CPU. Only once
the second stage fires does it actually reboot the hardware.
Has anyone considered adding support for this sort of hardware to the
/dev/watchdog API? It seems like it would make sense to reset the
watchdog timeout to some suitable period and trigger kdump. This would
let us preserve the crash information.
If the system is really fubared then the second stage will fire and
reboot the machine.
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com
reply other threads:[~2011-07-28 17:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E319781.9000405@genband.com \
--to=chris.friesen@genband.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--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