From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Josh Boyer <jwboyer@gmail.com>
Cc: Stefan Roese <stefan.roese@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Bootup support for watchdog with short timeout (touch_nmi_watchdog()?)
Date: Tue, 30 Oct 2007 08:51:08 -0400 [thread overview]
Message-ID: <20071030125108.GC27643@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20071029215454.0d644ca7@vader.jdub.homelinux.org>
On Mon, Oct 29, 2007 at 09:54:54PM -0500, Josh Boyer wrote:
> To some degree, it's configurable. But the generic question still
> stands. It seems like a decent idea to me. Making touch_watchdog (or
> whatever it winds up being called) nice across arches might be fun.
It always seemed to me that it was userspace that should poke the
watchdog as an indication user space still works on the system. That's
how my watchdogs are managed. I do initialize them in the boot loader
with a 3 minute timeout which is more than long enough for the system to
boot, load the driver and change the timeout to 60 seconds or whatever
I want at runtime and start the watchdog daemon.
If the kernel hangs at initializing some driver, I do NOT want the
kernel to automatically be poking the watchdog. I want it to time out
so to me the kernel should not be able to kick the watchdog at all by
itself.
--
Len Sorensen
prev parent reply other threads:[~2007-10-30 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 14:22 Bootup support for watchdog with short timeout (touch_nmi_watchdog()?) Stefan Roese
2007-10-29 19:45 ` Lennart Sorensen
2007-10-30 2:54 ` Josh Boyer
2007-10-30 11:16 ` Stefan Roese
2007-10-30 21:23 ` Wolfgang Denk
2007-10-30 12:51 ` Lennart Sorensen [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=20071030125108.GC27643@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan.roese@gmail.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