From owner-freebsd-stable@FreeBSD.ORG Fri Feb 10 23:38:34 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 592AF106564A for ; Fri, 10 Feb 2012 23:38:34 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by mx1.freebsd.org (Postfix) with ESMTP id 406D28FC13 for ; Fri, 10 Feb 2012 23:38:34 +0000 (UTC) Received: from omta05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by qmta12.emeryville.ca.mail.comcast.net with comcast id YPRE1i0080vp7WLACPRQJH; Fri, 10 Feb 2012 23:25:24 +0000 Received: from damnhippie.dyndns.org ([24.8.232.202]) by omta05.emeryville.ca.mail.comcast.net with comcast id YPRN1i00p4NgCEG8RPRP5k; Fri, 10 Feb 2012 23:25:23 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q1ANPLrf034019; Fri, 10 Feb 2012 16:25:21 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) From: Ian Lepore To: Jeremy Chadwick In-Reply-To: <20120210231059.GA25777@icarus.home.lan> References: <20120210145604.Horde.ewjpSpjmRSRPNSH0YRHxgAk@webmail.leidinger.net> <20120210231059.GA25777@icarus.home.lan> Content-Type: text/plain Date: Fri, 10 Feb 2012 16:25:21 -0700 Message-Id: <1328916321.6341.5.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.26.0 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit 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:38:34 -0000 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. -- Ian