From owner-freebsd-stable@FreeBSD.ORG Mon Aug 23 14:15:04 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27E60106566C for ; Mon, 23 Aug 2010 14:15:04 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp03.sth.basefarm.net (ch-smtp03.sth.basefarm.net [80.76.149.214]) by mx1.freebsd.org (Postfix) with ESMTP id D6A418FC16 for ; Mon, 23 Aug 2010 14:15:03 +0000 (UTC) Received: from c83-255-61-120.bredband.comhem.se ([83.255.61.120]:50503 helo=falcon.midgard.homeip.net) by ch-smtp03.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1OnXYM-000349-Ci for freebsd-stable@freebsd.org; Mon, 23 Aug 2010 15:59:13 +0200 Received: (qmail 42105 invoked from network); 23 Aug 2010 15:59:08 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 23 Aug 2010 15:59:08 +0200 Received: (qmail 5834 invoked by uid 1001); 23 Aug 2010 15:59:08 +0200 Date: Mon, 23 Aug 2010 15:59:08 +0200 From: Erik Trulsson To: Xin LI Message-ID: <20100823135908.GA5538@owl.midgard.homeip.net> References: <20100823103412.GA21044@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Originating-IP: 83.255.61.120 X-Scan-Result: No virus found in message 1OnXYM-000349-Ci. X-Scan-Signature: ch-smtp03.sth.basefarm.net 1OnXYM-000349-Ci ab9100a4502a87ee407473d247eeaf99 Cc: freebsd-stable@freebsd.org, phk@freebsd.org, Jeremy Chadwick Subject: Re: Watchdog not being disabled while dumping core X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Aug 2010 14:15:04 -0000 On Mon, Aug 23, 2010 at 04:07:47AM -0700, Xin LI wrote: > On Mon, Aug 23, 2010 at 3:34 AM, Jeremy Chadwick > wrote: > > PR bin/145183, opened in 2010 (not sure if this is the same): > > http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/145183 > > Speaking for this I think we can do it by issuing an explicit > watchdog(8) command on shutdown (like, set the timeout to several > minutes) in /etc/rc.d/watchdog's shutdown section. This would be > trivial to implement. No, it would not be trivial to implement (at least not if you want it to actually work correctly.) The reason for that is that at least some (perhaps even most) hardware watchdog devices do not support so long timeouts. I know for example that the watchdog in the ixp425 CPU has a maximum timeout of 65 seconds. Reading the manpage for ichwd(4) it seems that it has maximum timeout of about 37 seconds. I suspect that other hardware watchdogs have similar limits, which leads to the conclusion that one should not assume watchdog timeouts longer than maybe 30 seconds to be supported. -- Erik Trulsson ertr1013@student.uu.se