Date: Sun, 10 Nov 2002 19:13:29 -0800 (PST) From: Doug Ambrisko <ambrisko@ambrisko.com> To: Don Bowman <don@sandvine.com> Cc: "'freebsd-stable@freebsd.org'" <freebsd-stable@FreeBSD.ORG> Subject: Re: Any support for Intel ICH Watchdog ? Message-ID: <200211110313.gAB3DUdq057683@www.ambrisko.com> In-Reply-To: <FE045D4D9F7AED4CBFF1B3B813C8533701022EA0@mail.sandvine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Don Bowman writes: | http://www.intel.com/design/chipsets/applnots/29227301.pdf | describes what is needed to support the watchdog (so that | stuck servers get unstuck :) I have some code at: http://www.ambrisko.com/doug/watchdog/ The implements SW & HW watch dogs. If HW exists it links in via syctl patches that lets the SW watch dog control HW watch dogs if they are in the system. This was done to permit better watch dog timeouts then HW since some hardware is very limited on the time duration so it is used to "enforce" the SW watch dog is still running. If the SW watch dog stops updated the HW watch dog then the machine reboots. The other advantage is that if the SW can provide the main watch dog service then it can cause a panic to figure out what went wrong. It has support for the Intel TCO watchdog and SIS630 chipset. This is prototype code that works. A scheme to add in sub drivers needs to be added. When FreeBSD decides how this should work then I'll probably redo in that sense. Caveat is no real HW bounds checks are done for valid timeout. The sysctl interface is nice in that you can kld{load,unload} the HW part and leave the SW part working. It also allows the watch dogs to be disabled when you enter the debugger etc. | Is there any support for this in freebsd stable? Yes it runs on -stable. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211110313.gAB3DUdq057683>