From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: "Pádraig Brady" <P@draigBrady.com>
Cc: linux-kernel@vger.kernel.org, wim@iguana.be, seth.heasley@intel.com
Subject: Re: [PATCH] iTCO_wdt: Don't stop on shutdown with nowayout
Date: Wed, 24 Feb 2010 07:25:42 +0100 [thread overview]
Message-ID: <20100224072542.03e5ae08@marrow.netinsight.se> (raw)
In-Reply-To: <4B840154.1010501@draigBrady.com>
On Tue, 23 Feb 2010 16:24:52 +0000
> > + if (!nowayout)
> > + iTCO_wdt_stop();
> > }
> >
> > #define iTCO_wdt_suspend NULL
>
> I see the issue, however what happens if you're
> rebooting into a system that doesn't then renable the watchdog.
> I've seen systems where the hardware watchdog is not reset
> during the reboot process, in which case you'll get a
> reboot while running the other system.
Well, in that case I would run without nowayout. I just think the
behavior is a bit strange if the watchdog is turned off at all if we
have nowayout set.
Thanks for your suggestion though!
// Simon
next prev parent reply other threads:[~2010-02-24 6:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 15:40 Simon Kagstrom
2010-02-23 16:24 ` Pádraig Brady
2010-02-23 17:09 ` [PATCH] iTCO_wdt: Don't double the requested timeout Pádraig Brady
2010-02-24 9:16 ` Simon Kagstrom
2010-02-24 16:18 ` Pádraig Brady
2010-04-07 16:20 ` Pádraig Brady
[not found] ` <4B84FD15.9020803@draigBrady.com>
[not found] ` <20100224124730.6958b2c0@marrow.netinsight.se>
[not found] ` <4B8545D1.8000302@draigBrady.com>
[not found] ` <20100224165526.61cdd169@marrow.netinsight.se>
[not found] ` <4B854F58.4050907@draigBrady.com>
2010-02-25 7:45 ` Simon Kagstrom
2010-02-24 6:25 ` Simon Kagstrom [this message]
2010-03-07 15:16 ` [PATCH] iTCO_wdt: Don't stop on shutdown with nowayout Wim Van Sebroeck
2010-03-08 7:51 ` Simon Kagstrom
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=20100224072542.03e5ae08@marrow.netinsight.se \
--to=simon.kagstrom@netinsight.net \
--cc=P@draigBrady.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seth.heasley@intel.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
Powered by JetHome