From owner-freebsd-current@FreeBSD.ORG Mon Mar 16 16:45:52 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 D04E7106564A; Mon, 16 Mar 2009 16:45:52 +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 D39CA8FC1D; Mon, 16 Mar 2009 16:45:51 +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 SAA21240; Mon, 16 Mar 2009 18:44:11 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <49BE81DB.6040208@icyb.net.ua> Date: Mon, 16 Mar 2009 18:44:11 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.19 (X11/20090110) MIME-Version: 1.0 To: Mike Tancsa References: <200810011405.m91E5ugg028685@lava.sentex.ca> <200810011121.21908.jhb@freebsd.org> <49BD0943.3000400@OmniLAN.de> <200903161501.n2GF1bNw090788@lava.sentex.ca> In-Reply-To: <200903161501.n2GF1bNw090788@lava.sentex.ca> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Harald Schmalzbauer , freebsd-current@freebsd.org 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: Mon, 16 Mar 2009 16:45:53 -0000 on 16/03/2009 17:01 Mike Tancsa said the following: > > Hi, > No luck. I have a X58 board that also does not work, but in a > different way > > ichwd module loaded > ichwd0: on isa0 > ichwd0: Intel ICH10R watchdog timer (ICH10 or equivalent) > ppc0: parallel port not found. > > watchdogd starts up fine, but a kill -9 to it does not result in the box > resetting. I think that we have tough luck here unless somebody from Intel would be willing to help us. Linux is in the same boat, BTW. You can try it and see. My findings here: http://lists.freebsd.org/pipermail/freebsd-acpi/2009-January/005419.html Harald's issue might also be related to this, but I think that he has something else going on as well. Inability to change that means two things - either we don't access that register correctly (something is messed up on the bigger scale or BIOS took all control and we can't set that bit, period. Things to experiment with (for Harald): 1. try to disable whatever watchdog-related you have enabled in BIOS; 2. try to disable that block of code that checks the bit and see if watchdog can work despite that bit having the unwanted value; -- Andriy Gapon