Date: Fri, 05 Dec 2008 11:04:56 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Andriy Gapon <avg@icyb.net.ua> Cc: freebsd-hackers@freebsd.org, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: ichwd problem: watchdog doesn't "bark" Message-ID: <86wsefgcon.fsf@ds4.des.no> In-Reply-To: <49382449.80002@icyb.net.ua> (Andriy Gapon's message of "Thu, 04 Dec 2008 20:41:13 %2B0200") References: <49300020.6060603@icyb.net.ua> <49382449.80002@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Andriy Gapon <avg@icyb.net.ua> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86wsefgcon.fsf>