From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 10:04:57 2008 Return-Path: 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 ABB001065672; Fri, 5 Dec 2008 10:04:57 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 6D8828FC1A; Fri, 5 Dec 2008 10:04:57 +0000 (UTC) (envelope-from des@des.no) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id B8EC56D44E; Fri, 5 Dec 2008 10:04:56 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 9D6648448C; Fri, 5 Dec 2008 11:04:56 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Andriy Gapon References: <49300020.6060603@icyb.net.ua> <49382449.80002@icyb.net.ua> Date: Fri, 05 Dec 2008 11:04:56 +0100 In-Reply-To: <49382449.80002@icyb.net.ua> (Andriy Gapon's message of "Thu, 04 Dec 2008 20:41:13 +0200") Message-ID: <86wsefgcon.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, FreeBSD Stable 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2008 10:04:57 -0000 Andriy Gapon writes: > When I start watchdogd I see the following messages: > timer enabled > timeout set to 28 ticks > and then a flow of messages: > timer reloaded >=20 > Then I kill -9 watchdogd. > "timer reloded" messages are no longer produced. > And there are no other messages. >=20 > But nothing happens for many minutes that I waited. The watchdog may be disabled, either in hardware or by the BIOS at boot time, but the driver should have detected that. It is also possible that the BIOS catches the SMI but ignores it. > BTW, can someone knowledgeable tell me if watchdog better be firing SMI > or NMI when it runs down? It should fire SMI, IIRC. Read the comments at the top of the code for references to the relevant Intel documentation, which you can download for free. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no