From owner-freebsd-stable@FreeBSD.ORG  Thu Dec  4 18:41:18 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0CD831065670;
	Thu,  4 Dec 2008 18:41:18 +0000 (UTC) (envelope-from avg@icyb.net.ua)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.freebsd.org (Postfix) with ESMTP id 00BF28FC0A;
	Thu,  4 Dec 2008 18:41:16 +0000 (UTC) (envelope-from avg@icyb.net.ua)
Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua
	[212.40.38.101])
	by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA03603;
	Thu, 04 Dec 2008 20:41:14 +0200 (EET) (envelope-from avg@icyb.net.ua)
Message-ID: <49382449.80002@icyb.net.ua>
Date: Thu, 04 Dec 2008 20:41:13 +0200
From: Andriy Gapon <avg@icyb.net.ua>
User-Agent: Thunderbird 2.0.0.18 (X11/20081124)
MIME-Version: 1.0
To: FreeBSD Stable <freebsd-stable@freebsd.org>, freebsd-hackers@freebsd.org
References: <49300020.6060603@icyb.net.ua>
In-Reply-To: <49300020.6060603@icyb.net.ua>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 
Subject: Re: ichwd problem: watchdog doesn't "bark"
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2008 18:41:18 -0000

on 28/11/2008 16:28 Andriy Gapon said the following:
> uname:
> FreeBSD 7.1-PRERELEASE r185311 amd64
> 
> dmesg:
> ichwd0: <Intel ICH9R watchdog timer> on isa0
> ichwd0: Intel ICH9R watchdog timer (ICH9 or equivalent)
> ichwd0: timer disabled
> 
> pciconf:
> isab0@pci0:0:31:0:      class=0x060100 card=0x50448086 chip=0x29168086
> rev=0x02 hdr=0x00
>     vendor     = 'Intel Corporation'
>     device     = '82801IR (ICH9R) LPC Interface Controller'
>     class      = bridge
>     subclass   = PCI-ISA
> 
> 
> When I start watchdogd I see the following messages:
> timer enabled
> timeout set to 28 ticks
> and then a flow of messages:
> timer reloaded
> 
> Then I kill -9 watchdogd.
> "timer reloded" messages are no longer produced.
> And there are no other messages.
> 
> But nothing happens for many minutes that I waited.
> 

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.
Thanks!

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?

As additional data points: I see that TCO_EN bit of SMI_EN is 1 and it
is locked to that value because TCO_LOCK bit of TCO1_CNT is 1.
SMI_LOCK in PCI config register GEN_PMCON_1 is not set.

-- 
Andriy Gapon