From owner-freebsd-questions@FreeBSD.ORG Wed May 4 21:21:57 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 9CE2E16A4CE for ; Wed, 4 May 2005 21:21:57 +0000 (GMT) Received: from usw2.natel.net (2b.bz [209.152.117.190]) by mx1.FreeBSD.org (Postfix) with SMTP id 4308343D31 for ; Wed, 4 May 2005 21:21:56 +0000 (GMT) (envelope-from WD@US-Webmasters.com) Received: (qmail 39607 invoked from network); 4 May 2005 21:21:05 -0000 Received: from batv-01-053.dialup.netins.net (HELO Htebazile.US-Webmasters.com) (216.248.109.54) by us-webmasters.com with SMTP; 4 May 2005 21:21:05 -0000 Message-Id: <5.1.0.14.2.20050504161925.425f3100@209.152.117.178> X-Sender: wd@209.152.117.178 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 04 May 2005 16:20:21 -0500 To: freebsd-questions@freebsd.org From: "W. D." In-Reply-To: <20050504210729.GA9758@xor.obsecurity.org> References: <5.1.0.14.2.20050504154906.4311e370@209.152.117.178> <42792740.3040501@houston.rr.com> <5.1.0.14.2.20050504154906.4311e370@209.152.117.178> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable cc: Ryan Winograd 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:21:57 -0000 At 16:07 5/4/2005, Kris Kennaway wrote: >On Wed, May 04, 2005 at 03:51:05PM -0500, W. D. wrote: >> At 14:49 5/4/2005, Ryan Winograd, wrote: >> >Hi all, >> >I recently noticed that the system clock on a machine i recently set up= =20 >> >is running very quickly, about 2x realtime by my measuring. What can i= =20 >> >do to solve/investigate this problem? What information would be helpful? >>=20 >> http://www.Google.com/search?q=3Dinstall+ntp+on+FreeBSD > >Unfortunately ntp will not always help in these situations, because >the time is changing too quickly/slowly to keep up with. The OP >should check whether changing the kern.timecounter.hardware sysctl to >one of the other values listed in kern.timecounter.choice will fix the >problem (they are ranked in order of quality). Also look for a BIOS >update for your system - that may fix it. > >Kris Also: sometimes the clock speeds up when the battery is dying. Start Here to Find It Fast!=99 ->= http://www.US-Webmasters.com/best-start-page/ $8.77 Domain Names -> http://domains.us-webmasters.com/