Subject: Re: port-i386/35059:
To: None <,,>
From: Jaromir Dolecek <>
List: netbsd-bugs
Date: 11/15/2006 22:05:03
The following reply was made to PR port-i386/35059; it has been noted by GNATS.

From: Jaromir Dolecek <>
Subject: Re: port-i386/35059:
Date: Wed, 15 Nov 2006 23:03:19 +0100

 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 Dolecek <>  
 -=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-
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 Version: PGPfreeware 5.0i for non-commercial use
 MessageID: +O+DWNKtNCiQcAcP2UXqyCG7cIzAsvWa