From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 07:37:57 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 840E5106564A; Wed, 4 Jan 2012 07:37:57 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 94DE51501FC; Wed, 4 Jan 2012 07:37:56 +0000 (UTC) Message-ID: <4F0401D3.9040903@FreeBSD.org> Date: Tue, 03 Jan 2012 23:37:55 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: John Baldwin References: <4E23EE49.5040801@FreeBSD.org> <201108021806.04759.jhb@freebsd.org> <4E38FEE5.4080300@FreeBSD.org> <201201031714.40777.jhb@freebsd.org> In-Reply-To: <201201031714.40777.jhb@freebsd.org> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Andriy Gapon Subject: Re: ichwd0: unable to reserve GCS registers 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: Wed, 04 Jan 2012 07:37:57 -0000 On 01/03/2012 14:14, John Baldwin wrote: > On Wednesday, August 03, 2011 3:55:17 am Doug Barton wrote: >> On 08/02/2011 15:06, John Baldwin wrote: >>> On Saturday, July 30, 2011 2:49:52 am Andriy Gapon wrote: >>>> on 19/07/2011 18:16 John Baldwin said the following: >>>>> Hmm, can you get devinfo -r output from a working kernel with ichwd loaded? >>>>> You might be able to just build the kernel with 'nooptions NEW_PCIB'. >>>> >>>> I believe that I've got a similar problem with amdsbwd(4). >>>> It needs some resources (I/O ports) that belong to ACPI. >>>> The problem is that the driver attaches to isa bus which is under >>>> isab->pci->pcib and those particular resources are not assigned to the Host-PCI >>>> bridge. >>>> >>>> I think that you already made a suggestion that perhaps isa bus should directly >>>> attach to acpi bus when acpi is available. Not sure if there are any >>>> alternative approaches. >>> >>> Can you try this: >> >> Not so much. :) the first and last patches I can apply to HEAD by hand, >> but /sys/dev/acpica/acpi_pcib_acpi.c is only 387 lines long, so I'm not >> even sure where to start. >> >> Any chance you could diff against HEAD? > > I believe this should be fixed (well, worked-around) by my most recent commit > to sys/dev/acpica/acpi_pcib_acpi.c in HEAD. Funny you should ask. :) I saw that, and took a look. I'm getting the following error, from a verbose dmesg: isab0: found ICH10 or equivalent chipset: Intel ICH10DO watchdog timer ichwd0: on isa0 isab0: found ICH10 or equivalent chipset: Intel ICH10DO watchdog timer pcib0: allocated type 4 (0x830-0x837) for rid 0 of ichwd0 pcib0: allocated type 4 (0x860-0x87f) for rid 1 of ichwd0 ichwd0: ICH WDT present but disabled in BIOS or hardware device_attach: ichwd0 attach returned 6 That's different than the error message I got before, but watchdogd still fails. I didn't have a chance to check the BIOS settings until today, and there is no entry for anything even closely resembling this. The only things I actually have disabled are the parallel port, and the "Dell Trusted Platform Module," neither of which I can imagine would be relevant. I'm happy to provide more info. Doug -- You can observe a lot just by watching. -- Yogi Berra Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/