From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 25 13:18:31 2004 Return-Path: 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 0CA1616A4CE; Thu, 25 Mar 2004 13:18:31 -0800 (PST) Received: from www.ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id C969C43D2F; Thu, 25 Mar 2004 13:18:30 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.9p2/8.12.9) with ESMTP id i2PLIUCf086365; Thu, 25 Mar 2004 13:18:30 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.12.9p2/8.12.9/Submit) id i2PLIUS7086364; Thu, 25 Mar 2004 13:18:30 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200403252118.i2PLIUS7086364@ambrisko.com> In-Reply-To: <406344E4.6030207@freebsd.org> To: Scott Long Date: Thu, 25 Mar 2004 13:18:30 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: "Wm. Daryl Hawkins" Subject: Re: Intel i8xx watchdog driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Mar 2004 21:18:31 -0000 Scott Long writes: | Wm. Daryl Hawkins wrote: | > I've written a driver for the Intel i8xx TCO watchdog timer for both | > FreeBSD-CURRENT and FreeBSD-STABLE. | | This is wonderful. I'd be happy to test it and shepherd it in. Does it | support the intel 750x chips also? All ICH chips that I've touched support this with the device ID updated as needed. FYI there is a new watchdog device in the 6300ESB. Not sure if it is in prior ICH chips. It is interesting in that during the first expire it will generate and interrupt then it will reboot on the next expire. So if you have an ICH then you can use it. A nice concept would be to have a SW watchdog based on the clock tickle the HW watchdog. If the SW watchdog goes off you get a panic. Interesting caveats are having the watchdogs going off while in kgdb/ddb. Caveat to the ICH TCO timer is that if the speaker output out of the ICH has a pull up resistor on it then the TCO reset is disabled and will not reset the system. I ran into this on a motherboard at a prior company. You cannot via SW disable this feature :-( I have code for the SIS 630 chipset that I can give to anyone interested. Doug A.