Re: Fixed: ichwd failure to attach

On Friday, October 14, 2011 3:03:00 pm Xin LI wrote:
> On 10/14/11 10:58, John Baldwin wrote:
> > On Friday, October 14, 2011 1:35:19 pm Xin LI wrote:
> >> On 10/14/11 04:35, John Baldwin wrote:
> >>> On Thursday, October 13, 2011 6:26:26 pm Doug Barton wrote:
> >>>> On 10/12/2011 08:20, Michael Butler wrote:
> >>>>> SVN r226302 solves the ichwd failure to attach issue ..
> >>>>
> >>>> Still failing for me:
> >>>>
> >>>> ichwd0: <Intel ICH10DO watchdog timer> on isa0 ichwd0: unable
> >>>> to reserve GCS registers device_attach: ichwd0 attach
> >>>> returned 6
> >>>
> >>> Yes, it can only fix it if the BIOS decides to list it as a
> >>> system resource in ACPI.  However, using
> >>> 'debug.acpi.disabled=hostres' should still be working as a
> >>> workaround for lying BIOSes yes?
> >>
> >> I do have debug.acpi.disabled=hostres but it doesn't seem help in
> >> my case (Dell Latitude D630):
> >>
> >> ichwd0: <Intel ICH8M watchdog timer> on isa0 ichwd0: unable to
> >> reserve GCS registers device_attach: ichwd0 attach returned 6
> >> ichwd0: <Intel ICH8M watchdog timer> at port
> >> 0x1030-0x1037,0x1060-0x107f on isa0 ichwd0: unable to reserve GCS
> >> registers device_attach: ichwd0 attach returned 6
> >>
> >> Is there something I should look at or additional information
> >> needed?
> >
> > Hmm, is your isab device behind a PCI-PCI bridge?
> 
> Looks like it's not:

Hmm, the NEW_PCIB bits only affect two things:

1) Resource allocation for devices behind PCI-PCI bridges, and

2) Resource allocation for devices behind Host-PCI bridges (but 
debug.acpi.disabled="hostres" should turn that off).

I'll see if I can't look in my old thread to see why the allocations are 
failing.

-- 
John Baldwin