From: "Pádraig Brady" <P@draigBrady.com>
To: Valdis.Kletnieks@vt.edu
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Wim Van Sebroeck <wim@iguana.be>,
linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 1/2] watchdog: iTCO_wdt: optionally leave watchdog enabled during restart
Date: Thu, 07 Jul 2011 16:53:31 +0100 [thread overview]
Message-ID: <4E15D67B.2080405@draigBrady.com> (raw)
In-Reply-To: <12164.1310053141@turing-police.cc.vt.edu>
On 07/07/11 16:39, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 06 Jul 2011 10:09:36 MDT, Bjorn Helgaas said:
>
>> If we reboot via BIOS, BIOS should disable the watchdog itself, so this
>> shouldn't cause unintended resets, even if the user interrupts the boot.
>
> Yes, but didn't Linus say something about BIOS code authors being
> crack-addicted monkeys? :)
Yes as I said in a round about way in another mail,
one can't depend on that at all.
Some reset, some don't, some behave weirdly,
iTCO is unusual as kernel resets early at boot, ...
If using this, one would have to set the timeout large enough,
to encompass a full reboot
next prev parent reply other threads:[~2011-07-07 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 16:09 [PATCH 0/2] [RFC] watchdog reboot timeout Bjorn Helgaas
2011-07-06 16:09 ` [PATCH 1/2] watchdog: iTCO_wdt: optionally leave watchdog enabled during restart Bjorn Helgaas
2011-07-07 15:39 ` Valdis.Kletnieks
2011-07-07 15:53 ` Pádraig Brady [this message]
2011-07-12 17:22 ` Bjorn Helgaas
2011-07-06 16:09 ` [PATCH 2/2] watchdog: nv_tco: " Bjorn Helgaas
2011-07-07 13:51 ` [PATCH 0/2] [RFC] watchdog reboot timeout Pádraig Brady
2011-07-12 16:25 ` Bjorn Helgaas
2011-07-12 21:36 ` Pádraig Brady
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=4E15D67B.2080405@draigBrady.com \
--to=p@draigbrady.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=bhelgaas@google.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