Date: Wed, 12 Mar 2008 13:00:36 +0100
To: =?iso-8859-1?Q?P=E1draig?= Brady <P@draigBrady.com>
Cc: Wim Van Sebroeck <wim@iguana.be>, junker@anduras.de,
       LKML <linux-kernel@vger.kernel.org>
Subject: Re: w83697hf_wdt.c stops watchdog on load
References: <47D564CA.1040507@draigBrady.com> <2008-03-10-18-48-16+trackit+sam@rfc1149.net> <47D5C1DC.6080808@draigBrady.com> <20080311202214.GA7505@infomag.infomag.iguana.be> <2008-03-11-21-28-21+trackit+sam@rfc1149.net> <47D7C464.7060909@draigBrady.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <47D7C464.7060909@draigBrady.com>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)
From: Samuel Tardieu <sam@rfc1149.net>
Organization: RFC 1149 (see http://www.rfc1149.net/)
Message-Id: <2008-03-12-13-00-36+trackit+sam@rfc1149.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 977
Lines: 26

On 12/03, P?draig Brady wrote:

| When doing this it would be useful to print a warning iif the watchdog
| was running.

Agreed.

| p.s. I'm still not sure it should default to turning off.
| It would be unusual for userspace to take over 60s to _start_
| If that was the case then the user shouldn't enable the watchdog in the
| BIOS at all.

Most users I know using this watchdog are using it on an hosted
dedicated server, for which the boot messages are not available.
Aborting because of the watchdog triggering during fsck would not be
easily spottable. I prefer to err on the safe side from the user point
of view, even though I guess what you see as being "on the safe side"
would be to keep the watchdog enabled :)

  Sam

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/