From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 5 08:20:42 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E53BF1065670 for ; Fri, 5 Dec 2008 08:20:42 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id C46D58FC08 for ; Fri, 5 Dec 2008 08:20:42 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id mB58Kf0V080782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 5 Dec 2008 00:20:41 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id mB58Kfad080781; Fri, 5 Dec 2008 00:20:41 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA18469; Fri, 5 Dec 08 00:07:30 PST Date: Fri, 05 Dec 2008 00:10:52 -0800 From: perryh@pluto.rain.com To: avg@icyb.net.ua Message-Id: <4938e20c.nP8q+JgDZ0gKUsAU%perryh@pluto.rain.com> References: <49300020.6060603@icyb.net.ua> <49382449.80002@icyb.net.ua> In-Reply-To: <49382449.80002@icyb.net.ua> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: ichwd problem: watchdog doesn't "bark" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2008 08:20:43 -0000 [dropped stable@ since I'm not on it and I suspect it may not accept non-member posts] > BTW, can someone knowledgeable tell me if watchdog better > be firing SMI or NMI when it runs down? > My bet is on NMI, but who knows. It may depend on whether you want the BIOS, or FreeBSD, handling the interrupt. Unless you are running *very* old h/w, there's a good chance the BIOS intercepts SMI, even with a protected-mode OS running, and I wouldn't be surprised if the BIOS' response to a watchdog timeout were an immediate reboot. It might be good to check the motherboard and/or BIOS manuals. > Or maybe I am trying to ask a different question. > I see that NMI2SMI_EN bit of TCO1_CNT is set 1 on my machine and > our watchdog driver is careful to preserve this bit unmodified. > This means that watchdog would try to cause SMI instead of NMI. > On the other hand I see that bit GBL_SMI_EN of SMI_EN is set to > zero, which means that chipset would never generate an SMI. > So I think this is why I don't see anything happening. > > Now, would should try first - reset NMI2SMI_EN to zero or set > GBL_SMI_EN to 1? If you want to handle the interrupt in FreeBSD, I'd try resetting NMI2SMI_EN to zero.