From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 25 13:40:12 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 5093416A4CE for ; Thu, 25 Mar 2004 13:40:12 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 1C87F43D3F for ; Thu, 25 Mar 2004 13:40:12 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 50958 invoked by uid 1002); 25 Mar 2004 21:40:11 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 25 Mar 2004 21:40:11 -0000 Message-ID: <406350DD.9060104@freebsd.org> Date: Thu, 25 Mar 2004 14:36:29 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug Ambrisko References: <200403252118.i2PLIUS7086364@ambrisko.com> In-Reply-To: <200403252118.i2PLIUS7086364@ambrisko.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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:40:12 -0000 Doug Ambrisko wrote: > 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. > In reading the code, it appears that it is indeed an ICHx service and not limited to just i8xx chipsets. I have a few issues with how the probe and attach are done, and I'm addressing these in a private mail right now. It's funny that I was reading the Intel ICH5 docs last night and didn't come across this feature at all. I'm not sure if I like the idea of auto-reboot on second expire, unless it is configurable (i.e. you can turn that feature off depending on the situation). I understand it's purpose though. > 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. > Talking with PHK about this now. There seems to be a growing need for a mechanism that can inform registered listeners that DDB is about to be entered. It's just a random thought in my brain right now, need more time to flesh it out. > 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. More support it wonderful! I don't have any hardware to test it on, though. Scott