ichwd attach failure
John Baldwin
jhb at freebsd.org
Mon Aug 29 18:21:22 UTC 2011
On Friday, August 26, 2011 8:48:17 pm Doug Barton wrote:
> John was working on this, haven't seen an update recently though.
I don't currently have a solution, no. It seems that the BIOS just outright
lies in this case. ichwd is already engaged in some odd behavior to allocate
its resource from isab0 instead of ichwd0. I need to find out what I asked
DES to do that but haven't had time to go digging in my mail archive to figure
it out.
> Doug
>
>
> On 08/26/2011 14:24, Mike Tancsa wrote:
> > Got a newish Intel board in and decided to give it a spin. Trying to
> > load the watchdog, I get this error below on CURRENT. Anyone able to
> > get ichwd working on such a motherboard ? full dmesg and devinfo at
> >
> > http://www.tancsa.com/intel.txt
> > and
> > http://www.tancsa.com/intel-asl.txt
> >
> >
> >
> > isab0: found ICH10 or equivalent chipset: Intel Cougar Point watchdog
timer
> > ichwd0: <Intel Cougar Point watchdog timer> on isa0
> > isab0: found ICH10 or equivalent chipset: Intel Cougar Point watchdog
timer
> > pcib0: allocated type 4 (0x430-0x437) for rid 0 of ichwd0
> > pcib0: allocated type 4 (0x460-0x47f) for rid 1 of ichwd0
> > ichwd0: unable to reserve GCS registers
> > device_attach: ichwd0 attach returned 6
> > pcib0: allocated type 4 (0x3f0-0x3f5) for rid 0 of fdc0
> > pcib0: allocated type 4 (0x3f7-0x3f7) for rid 1 of fdc0
> > ppc0: cannot reserve I/O port range
> > pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart1
> >
> >
>
>
>
> --
>
> Nothin' ever doesn't change, but nothin' changes much.
> -- OK Go
>
> Breadth of IT experience, and depth of knowledge in the DNS.
> Yours for the right price. :) http://SupersetSolutions.com/
>
>
--
John Baldwin
More information about the freebsd-current
mailing list