Date: Fri, 10 Feb 2012 15:30:24 -0800 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Ian Lepore <freebsd@damnhippie.dyndns.org> Cc: stable@freebsd.org Subject: Re: Reducing the need to compile a custom kernel Message-ID: <20120210233024.GA26774@icarus.home.lan> In-Reply-To: <1328916321.6341.5.camel@revolution.hippie.lan> References: <20120210145604.Horde.ewjpSpjmRSRPNSH0YRHxgAk@webmail.leidinger.net> <20120210231059.GA25777@icarus.home.lan> <1328916321.6341.5.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
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 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120210233024.GA26774>