Re: ichwd0: unable to reserve GCS registers

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: <Intel ICH10DO watchdog timer> 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