From owner-freebsd-hackers Thu Sep 12 6:15:36 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 5CFA637B400 for ; Thu, 12 Sep 2002 06:15:35 -0700 (PDT) Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEB4E43E75 for ; Thu, 12 Sep 2002 06:15:34 -0700 (PDT) (envelope-from tinguely@web.cs.ndsu.nodak.edu) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id g8CDFVJ55830; Thu, 12 Sep 2002 08:15:31 -0500 (CDT) (envelope-from tinguely) Date: Thu, 12 Sep 2002 08:15:31 -0500 (CDT) From: mark tinguely Message-Id: <200209121315.g8CDFVJ55830@web.cs.ndsu.nodak.edu> To: bms@spc.org, hackers@FreeBSD.ORG Subject: Re: Supporting HW_WDOG? 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 > 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. 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. --mark tinguely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message