linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Dave Young <dyoung@redhat.com>
Cc: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
	wim@iguana.be, dzickus@redhat.com, bhe@redhat.com,
	linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] watchdog: add a parameter for stop wdt before register
Date: Wed, 15 Jan 2014 11:46:09 -0500	[thread overview]
Message-ID: <20140115164609.GC3180@redhat.com> (raw)
In-Reply-To: <20140115011142.GC23767@dhcp-16-126.nay.redhat.com>

On Wed, Jan 15, 2014 at 09:11:42AM +0800, Dave Young wrote:

[..]
> > I thought this problem was resolved (atleast conceptually) last time
> > when Don Zickus brought it up.
> > 
> > He mentioned that it was concluded that keep watchdog interval long
> > enough, say 60 seconds and keep on kicking it fast enough, say every
> > 10-20 seconds. That would ensure that after the crash, there is atleast
> > 60 - 20 = 40 seconds left before watchdog expires. And in that duration
> > we should try to boot into second kernel load watchdog driver early enough
> > from initramfs which can start kicking watchdog again.
> 
> Some drivers did stop the watchdog while module loading such as iTCO_wdt.

Instead of stopping why not keep on kicking it till user space takes
over this job. This will also make sure that if kdump kernel hangs,
watchdog wil do the job it is supposed to do?

Thanks
Vivek

  reply	other threads:[~2014-01-15 16:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  8:23 [PATCH] watchdog: add a parameter for stop wdt before register Dave Young
2014-01-14  8:26 ` Wim Van Sebroeck
2014-01-14  8:41   ` Dave Young
2014-01-14  9:44     ` Dave Young
2014-01-14 12:16 ` One Thousand Gnomes
2014-01-14 16:24   ` Vivek Goyal
2014-01-15  1:11     ` Dave Young
2014-01-15 16:46       ` Vivek Goyal [this message]
2014-01-16  1:50         ` Dave Young
2014-01-15  0:59   ` Dave Young
2014-01-15 12:15     ` One Thousand Gnomes
2014-01-15 16:55       ` Vivek Goyal
2014-01-16  1:52         ` Dave Young

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=20140115164609.GC3180@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=bhe@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=dzickus@redhat.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).