From owner-freebsd-current  Thu Mar  5 02:01:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA15680
          for freebsd-current-outgoing; Thu, 5 Mar 1998 02:01:41 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15671
          for <freebsd-current@FreeBSD.ORG>; Thu, 5 Mar 1998 02:01:35 -0800 (PST)
          (envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id KAA10158;
	Thu, 5 Mar 1998 10:55:28 +0100 (CET)
To: Bruce Evans <bde@zeta.org.au>
cc: cjb@efn.org, freebsd-current@FreeBSD.ORG
Subject: Re: Weird CPU clock in dmesg 
In-reply-to: Your message of "Thu, 05 Mar 1998 19:08:12 +1100."
             <199803050808.TAA10228@godzilla.zeta.org.au> 
Date: Thu, 05 Mar 1998 10:55:27 +0100
Message-ID: <10156.889091727@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <199803050808.TAA10228@godzilla.zeta.org.au>, Bruce Evans writes:
>>I recently noticed something weird in my dmesg:
>>CPU: Pentium (0.00-MHz 586-class CPU)
>>  Origin = "GenuineIntel"  Id = 0x52c  Stepping=12
>>  Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
>
>Setting of the frequency is broken if apm0 is configured (even if apm0
>is disabled or its probe fails).  Don't configure apm0 if you don't
>use it.

I'm currently looking at handling this better.

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
"Drink MONO-tonic, it goes down but it will NEVER come back up!"

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message