Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Oct 2011 13:58:27 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        d@delphij.net
Cc:        Doug Barton <dougb@freebsd.org>, Michael Butler <imb@protected-networks.net>, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: Fixed: ichwd failure to attach
Message-ID:  <201110141358.28250.jhb@freebsd.org>
In-Reply-To: <4E9872D7.7050905@delphij.net>
References:  <4E95B028.6090307@protected-networks.net> <201110140735.52298.jhb@freebsd.org> <4E9872D7.7050905@delphij.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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?

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201110141358.28250.jhb>