From owner-freebsd-stable@FreeBSD.ORG Fri Feb 10 23:30:25 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4C5E106566B for ; Fri, 10 Feb 2012 23:30:25 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [76.96.30.48]) by mx1.freebsd.org (Postfix) with ESMTP id 9B0418FC0A for ; Fri, 10 Feb 2012 23:30:25 +0000 (UTC) Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by qmta05.emeryville.ca.mail.comcast.net with comcast id YPWP1i0061smiN4A5PWRJu; Fri, 10 Feb 2012 23:30:25 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta20.emeryville.ca.mail.comcast.net with comcast id YPWQ1i01R1t3BNj8gPWQNo; Fri, 10 Feb 2012 23:30:25 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 60EC5102C1E; Fri, 10 Feb 2012 15:30:24 -0800 (PST) Date: Fri, 10 Feb 2012 15:30:24 -0800 From: Jeremy Chadwick To: Ian Lepore Message-ID: <20120210233024.GA26774@icarus.home.lan> References: <20120210145604.Horde.ewjpSpjmRSRPNSH0YRHxgAk@webmail.leidinger.net> <20120210231059.GA25777@icarus.home.lan> <1328916321.6341.5.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1328916321.6341.5.camel@revolution.hippie.lan> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: stable@freebsd.org Subject: Re: Reducing the need to compile a custom kernel 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: Fri, 10 Feb 2012 23:30:25 -0000 On Fri, Feb 10, 2012 at 04:25:21PM -0700, Ian Lepore wrote: > On Fri, 2012-02-10 at 15:10 -0800, Jeremy Chadwick wrote: > > * Addition: device ichwd > > - Note: We do not use features of this driver given known problems > > with the watchdog firing during ddb> and similar environments. I > > have no idea if this has been fixed, but I do remember it being > > confirmed as a problem. > > It used to be that "watchdog 0" in ddb disabled the watchdog, then when > we upgraded to 8.2 that stopped working. One day I discovered (via > typo) that now just "watchdog" without a numeric parm disables it. I'm > not positive that applies to the ichwd but it works that way for the > hardware watchdog on our arm platforms. This won't work for us. This requires manual intervention. When we have a machine that panic's, we want it sitting at a ddb> prompt indefinitely until an admin gets to it to find out what happened. There may be some way to automatically run ddb commands when ddb is induced, but I haven't dug into it yet. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |