From owner-freebsd-current@FreeBSD.ORG Fri Jan 27 18:36:04 2012 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 44BB21065678; Fri, 27 Jan 2012 18:36:04 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id D196C8FC20; Fri, 27 Jan 2012 18:36:03 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 8850546B32; Fri, 27 Jan 2012 13:36:03 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 1E803B96F; Fri, 27 Jan 2012 13:36:03 -0500 (EST) From: John Baldwin To: Doug Barton Date: Fri, 27 Jan 2012 13:21:39 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <4E23EE49.5040801@FreeBSD.org> <201201031714.40777.jhb@freebsd.org> <4F0401D3.9040903@FreeBSD.org> In-Reply-To: <4F0401D3.9040903@FreeBSD.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201201271321.39632.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 27 Jan 2012 13:36:03 -0500 (EST) 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: Fri, 27 Jan 2012 18:36:04 -0000 On Wednesday, January 04, 2012 2:37:55 am Doug Barton wrote: > 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. Does it operate fully with NEW_PCIB disabled entirely, or do you get this same message in that case? -- John Baldwin