Date: Sat, 28 Jan 2012 17:06:29 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Andriy Gapon <avg@FreeBSD.org> Cc: freebsd-current@FreeBSD.org, John Baldwin <jhb@FreeBSD.org> Subject: Re: ichwd0: unable to reserve GCS registers Message-ID: <4F249B95.9080808@FreeBSD.org> In-Reply-To: <4F23C2BE.7080600@FreeBSD.org> References: <4E23EE49.5040801@FreeBSD.org> <201201031714.40777.jhb@freebsd.org> <4F0401D3.9040903@FreeBSD.org> <201201271321.39632.jhb@freebsd.org> <4F23BC2B.8070801@FreeBSD.org> <4F23BE29.7040102@FreeBSD.org> <4F23C1DE.2010700@FreeBSD.org> <4F23C2BE.7080600@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE8BABC3CE012797212DF4653 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 01/28/2012 01:41, Andriy Gapon wrote: > on 28/01/2012 11:37 Doug Barton said the following: >> On 01/28/2012 01:21, Andriy Gapon wrote: >>> on 28/01/2012 11:13 Doug Barton said the following: >>>> On 01/27/2012 10:21, John Baldwin wrote: >>>>> Does it operate fully with NEW_PCIB disabled entirely, or do you ge= t this >>>>> same message in that case? >>>> >>>> I put nooptions NEW_PCIB in my kernel config, and got basically the = same: >>>> >>>> isab0: found ICH10 or equivalent chipset: Intel ICH10DO watchdog tim= er >>>> ichwd0: <Intel ICH10DO watchdog timer> on isa0 >>>> isab0: found ICH10 or equivalent chipset: Intel ICH10DO watchdog tim= er >>>> ichwd0: ICH WDT present but disabled in BIOS or hardware >>>> device_attach: ichwd0 attach returned 6 >>> >>> The next logical question is has ichwd ever worked on this system? W= ith any >>> version of FreeBSD.=20 >> >> I have a vague recollection that it did, but I just tried 8.1-RELEASE = on >> the same system and got the same message about it being disabled. >=20 > Then I'd guess that it has never actually worked (with FreeBSD). It's possible, sure. What I find interesting is that the message I'm seeing on -current is different after John's recent commit. OTOH I'm now seeing the same message on 8 as I am on -current, so you're probably righ= t. >> OTOH, >> on my laptop I know that it used to work, and then it didn't. >=20 > But that's a different system and, as such, a different problem? > Have you fixed it or debugged it in a similar fashion to this !laptop s= ystem? I did in the past, yes. But I haven't had a chance to do that since John's latest commit. I'll do that when I can. Doug --=20 It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ --------------enigE8BABC3CE012797212DF4653 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iQEcBAEBCAAGBQJPJJuVAAoJEFzGhvEaGryEimMH/2jWDgy+PovHyl2khFJtd8xo UNqlCkLIdhgtHdLP7ICzFOYpQrWF7QG40JrswHlzPFtOYFAE/aD6wJfx46MByWVH iQ/jrFs9TYVMzgsIwXA0e3a5jqd3ITiArViIg1lb8pNIyaY3T53zp59RIgSKHYWW Z1QIW+myL3UnbKuZRbwsil52R5ctCo2Ghdo+vPJj+4SBBvI/lp1KSI5aDQXlVhE+ OVQnLnJ74M8Z3wuvwe5i3sz885DILFp131qtSGuc4u7jsEk9iBP+EpGaFcn1vgnu XPYhgxoe+/KmTp1WePnniP+3xbg3eyAPxPdYXpErZASTbBHjmKAFVP4folIU8zs= =be6W -----END PGP SIGNATURE----- --------------enigE8BABC3CE012797212DF4653--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F249B95.9080808>