From owner-freebsd-questions@FreeBSD.ORG Wed May 4 21:55:12 2005 Return-Path: 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 8442316A4CE for ; Wed, 4 May 2005 21:55:12 +0000 (GMT) Received: from ms-smtp-04.texas.rr.com (ms-smtp-04.texas.rr.com [24.93.47.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id A12A543D58 for ; Wed, 4 May 2005 21:55:11 +0000 (GMT) (envelope-from rylwin@houston.rr.com) Received: from [192.168.1.40] (cpe-67-10-38-25.houston.res.rr.com [67.10.38.25])j44LsUgJ002432; Wed, 4 May 2005 16:54:31 -0500 (CDT) Message-ID: <4279448F.4010103@houston.rr.com> Date: Wed, 04 May 2005 16:54:23 -0500 From: Ryan Winograd User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Charles Swiger References: <42792740.3040501@houston.rr.com> <34d0f02f0868350c3c07570e3a73ceef@mac.com> In-Reply-To: <34d0f02f0868350c3c07570e3a73ceef@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine cc: freebsd-questions@freebsd.org Subject: Re: Clock running fast X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2005 21:55:12 -0000 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