From owner-freebsd-current@FreeBSD.ORG Tue Mar 17 19:33:27 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB4951065673 for ; Tue, 17 Mar 2009 19:33:27 +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 028338FC1E for ; Tue, 17 Mar 2009 19:33:26 +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 VAA03600; Tue, 17 Mar 2009 21:31:46 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <49BFFAA2.3000603@icyb.net.ua> Date: Tue, 17 Mar 2009 21:31:46 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.19 (X11/20090110) MIME-Version: 1.0 To: Harald Schmalzbauer References: <200810011405.m91E5ugg028685@lava.sentex.ca> <200810011121.21908.jhb@freebsd.org> <49BD0943.3000400@OmniLAN.de> <200903161501.n2GF1bNw090788@lava.sentex.ca> <49BE81DB.6040208@icyb.net.ua> <49BFAEB1.1010800@freebsd.org> <49BFE933.9040706@omnilan.de> In-Reply-To: <49BFE933.9040706@omnilan.de> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Mike Tancsa Subject: Re: ichwd on ich9 attach failing ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2009 19:33:28 -0000 on 17/03/2009 20:17 Harald Schmalzbauer said the following: > One thing which is also new to me is an attached IPMI wtachdog. No idea > about IPMI (yet) but maybe the wd-timer is just occupated by BMC/IPMI?! > > ipmi0: IPMI device rev. 1, firmware rev. 0.2, version 2.0 > ipmi0: Number of channels 2 > ipmi0: Attached watchdog I think that this is unlikely. There can definitely be other agents that could reload watchdog's timer, of course. It is even possible to do that via SMBus interface (where ICH acts as slave). But I don't think that micro-controllers typically do that. It's possible to monitor TCO_RLD value and see if it gets reloaded to TCO_TMR value even after watchdogd dies a violent death. -- Andriy Gapon