Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Jul 2003 13:43:11 -0700 (PDT)
From:      Doug Ambrisko <ambrisko@ambrisko.com>
To:        Julian Elischer <julian@elischer.org>
Cc:        Sean Kelly <smkelly@freebsd.org>
Subject:   Re: Remove "options HW_WDOG"?
Message-ID:  <200307292043.h6TKhBIh078195@www.ambrisko.com>
In-Reply-To: <Pine.BSF.4.21.0307231734360.60197-100000@InterJet.elischer.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer writes:
| this code WAS used in the interjet.
| We had modules that linked in and just needed somewhere to hook into..
| the hardware watchdog was held off by our software, but we needed to add
| code to the core-dump routines to routinely call the watchdog hold-off
| or we could never get a coredump because the watchdog would always go 
| off before the dump was completed.
| 
| I doubt it is used by anyone any more but It's good that you asked..
| I did notice some people were working on the watchdog support for the
| chipsets that have a watchdog in them so I guess they wil have all their
| own entrypoints.

Most sane watchdogs let you disable them.  The ones I've implemented
allow this.  I then added code to the panic/debugger code to disable
consmute and disable the watchdog. 

I know the Whistle one didn't let you do this so we had to tickle it
during panics etc.

Doug A.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200307292043.h6TKhBIh078195>