Re: kern/44224: -current double-fault at boot

[Arnaud Lacombe <lacombar%gmail.com@localhost>]

The following reply was made to PR kern/44224; it has been noted by GNATS.

From: Arnaud Lacombe <lacombar%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/44224: -current double-fault at boot
Date: Sun, 12 Dec 2010 17:58:55 -0500

 Hi,
 
 On Sun, Dec 12, 2010 at 5:15 PM, Martin Husemann 
<martin%duskware.de@localhost> wrote=
 :
 > The following reply was made to PR kern/44224; it has been noted by GNATS=
 .
 >
 > From: Martin Husemann <martin%duskware.de@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc:
 > Subject: Re: kern/44224: -current double-fault at boot
 > Date: Sun, 12 Dec 2010 23:10:40 +0100
 >
 > =A0On Sun, Dec 12, 2010 at 07:10:01PM +0000, lacombar%gmail.com@localhost 
 > wrote:
 > =A0> cpu0 at mainbus0 apid 0: Intel 686-class, 2154MHz, id 0x6fd
 >
 > =A0What kind of cpu is that exactly?
 Despite what the dmesg say, it should be the following CPU:
 
 Intel Core 2 (Merom) (686-class), 1795.62 MHz, id 0x6fd
 
 this would match the fact that `machdep.est.frequency.available' does
 not display any frequency above 1800MHz.
 
 Full dmesg is here:
 
 http://mail-index.netbsd.org/current-users/2010/04/17/msg013120.html
 
  - Arnaud
 
 ps: it would seem 5.99.25 misdetects the CPU, as 5.99.13 was detecting
 the right frequency.