From owner-freebsd-questions@FreeBSD.ORG  Thu May  5 04:48:08 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AC7FB16A4CE
	for <freebsd-questions@freebsd.org>;
	Thu,  5 May 2005 04:48:08 +0000 (GMT)
Received: from gretel.pobox.com (gretel.pobox.com [208.58.1.197])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 65FF243D6D
	for <freebsd-questions@freebsd.org>;
	Thu,  5 May 2005 04:48:08 +0000 (GMT)	(envelope-from LukeD@pobox.com)
Received: from orb.pobox.com (orb.pobox.com [207.8.226.5])
	by gretel.pobox.com (Postfix) with ESMTP id B935375D719
	for <freebsd-questions@freebsd.org>;
	Wed,  4 May 2005 18:18:40 -0400 (EDT)
Received: from orb (localhost [127.0.0.1])
	by orb.pobox.com (Postfix) with ESMTP
	id C532FA60; Wed,  4 May 2005 18:18:06 -0400 (EDT)
Received: from pool-71-112-215-205.sttlwa.dsl-w.verizon.net
	(pool-71-112-215-205.sttlwa.dsl-w.verizon.net [71.112.215.205])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by orb.sasl.smtp.pobox.com (Postfix) with ESMTP id D8FD78E;
	Wed,  4 May 2005 18:18:04 -0400 (EDT)
Date: Wed, 4 May 2005 15:18:03 -0700 (PDT)
From: Luke Dean <LukeD@pobox.com>
X-X-Sender: lukas@border.crystalsphere.multiverse
To: Ryan Winograd <rylwin@houston.rr.com>
In-Reply-To: <4279448F.4010103@houston.rr.com>
Message-ID: <20050504151359.U72230@border.crystalsphere.multiverse>
References: <42792740.3040501@houston.rr.com>
	<34d0f02f0868350c3c07570e3a73ceef@mac.com>
	<4279448F.4010103@houston.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
cc: freebsd-questions@freebsd.org
Subject: Re: Clock running fast
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Luke Dean <LukeD@pobox.com>
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 May 2005 04:48:08 -0000

On Wed, 4 May 2005, Ryan Winograd wrote:
> Charles Swiger wrote:
>
>> On May 4, 2005, at 3:49 PM, Ryan Winograd wrote:
>> 
>>> I recently noticed that the system clock on a machine i recently set up is 
>>> running very quickly, about 2x realtime by my measuring. What can i do to 
>>> solve/investigate this problem? What information would be helpful?
>> 
>> 
>> Try changing the kern.timecounter.hardware sysctl; you can look at the 
>> available choices via:
>> 
>>      sysctl kern.timecounter.choice
>> 
>
> Thanks for all the advice everyone. The solution was changing the 
> kern.timecounter.hardware sysctl to i8254 (was ACPI-safe). I was using NTP, 
> but when the clock is at 2x even having cron run ntp every minute is too 
> innacurate.
>
> Thx again!
> Ryan

I wish I'd known about that sysctl when I had this problem on my last 
system!  I tried ntp, but having ntp constantly resetting the clock just 
added new problems.
Thanks for sharing the outcome with us.