--PNTmBPCT7hxwcZjr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Nov 15, 2006 at 07:35:02PM +0000, Matthias Drochner wrote:
>  Very strange, a 0 is illegal according to Intel's manual
>  (Software developers manual, System programming part 2, Appendix B)
>
>  I've got a quite similar box, also with FSB667, and it is
>  recognized without error:
>  cpu0: Intel Core 2 (Merom) (686-class), 1995.09 MHz, id 0x6f6
>  [...]
>  cpu0: "Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz"
>  cpu0: I-cache 32 KB 64B/line 8-way, D-cache 32 KB 64B/line 8-way
>  cpu0: using thermal monitor 1
>  >                case 0:
>  >                        bus_clock =3D 6666;
>  >                        break;
> =20
>  This is very likely incorrect, as (a) the "0" shouldn't happen,
>  and (b) it would affect all Core/Core2 processors.
> =20
>  Are you using some non-default compiler optimisation?

Nope - I'm using stock i386 GENERIC.MP from autobuild about a week
ago. It's i386 kernel, rather then amd64, though.  Perhaps that
might be the problem?

Jaromir
--=20
Jaromir Dolecek <jdolecek@NetBSD.org>            http://www.NetBSD.cz/
-=3D- We can walk our road together if our goals are all the same;     -=3D-
-=3D- We can run alone and free if we pursue a different aim.          -=3D-

--PNTmBPCT7hxwcZjr
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: +O+DWNKtNCiQcAcP2UXqyCG7cIzAsvWa

iQCVAwUBRVuOp7ZjOQfIPRaZAQH2KgP+ItAGH7TmutprWXQxSmnkP7Jwfb948Azr
KDjh8cGI7qCW+5VY0Bi7OVxA3/NlsZIPJBP/x4Yw0tiSQDHXTP0hGwpZGUpSvU2j
hCsDPk4u65uw+HBeTXql3bNzpv3o5JPsOe+PRdMiLkBQvsEW98wTVlUnxgtCfFdv
n0UiFRxj9tw=
=68EM
-----END PGP SIGNATURE-----

--PNTmBPCT7hxwcZjr--