From owner-freebsd-hackers Thu Sep 12 6:45:33 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50C5F37B401 for ; Thu, 12 Sep 2002 06:45:24 -0700 (PDT) Received: from insomnia.spc.org (insomnia.spc.org [195.224.94.183]) by mx1.FreeBSD.org (Postfix) with SMTP id 4B9F743E65 for ; Thu, 12 Sep 2002 06:45:23 -0700 (PDT) (envelope-from bms@insomnia.spc.org) Received: (qmail 20303 invoked by uid 1031); 12 Sep 2002 13:43:02 -0000 Date: Thu, 12 Sep 2002 14:43:02 +0100 From: Bruce M Simpson To: Terry Lambert Cc: mark tinguely , hackers@FreeBSD.ORG Subject: Re: Supporting HW_WDOG? Message-ID: <20020912134302.GJ2420@spc.org> References: <200209121315.g8CDFVJ55830@web.cs.ndsu.nodak.edu> <3D809770.6E6CA1FD@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D809770.6E6CA1FD@mindspring.com> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Sep 12, 2002 at 06:32:32AM -0700, Terry Lambert wrote: > mark tinguely wrote: > > > Is there any documentation, or source code, demonstrating how to implement > > > a hardware watchdog for FreeBSD using the HW_WDOG kernel option? > > > > the HW_WDOG option attempts to keep the watchdog from expiring while > > the core memory is being dumped to a IDE drive. The SCSI dadump() > > does not use wdog_tickler. > > By this, you mean that it does not support preventing the > watchdog rest from being triggered while a dump is in progress? If it were monitoring bus activity, then it probably doesn't need to (assuming bus activity is its sole criterion for resetting or not resetting the box). > > your hardware watchdog driver will have to set the varible wdog_tickler > > to your watch dog tickler routine, or a generic routine if multiple watchdog > > timers could be supported in one machine. > > And modify the SCSI dadump() to call the routine at intervals > during a dump, right? Same would appear to go for ad_dump() and atapi_dump(), too, not to mention the RAID drivers. Mainly interested in exploring this with a view to implementing capabilities a bit like the LOM chip found in Sun Netras on an i386 box. What I'd like to do is modify a Soekris net4501 for this. The Sun LOM chip handles things like serial console capabilities, environmentals, and provides a means of executing memory tests, etc; it's able to issue notifications to the OS running on the machine, I believe using traps or an NMI mechanism. Come to think of it, has anybody seen anything like this in the Intel IPMI specification? Just a thought. BMS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message