From owner-freebsd-questions@FreeBSD.ORG  Thu Dec 30 22:56:29 2004
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 E62F216A4CE
	for <questions@freebsd.org>; Thu, 30 Dec 2004 22:56:29 +0000 (GMT)
Received: from elisha.daleco.biz (cdm-66-76-92-15.cart.cox-internet.com
	[66.76.92.15])	by mx1.FreeBSD.org (Postfix) with ESMTP id 5B34343D1D
	for <questions@freebsd.org>; Thu, 30 Dec 2004 22:56:29 +0000 (GMT)
	(envelope-from kadmin@elisha.daleco.biz)
Received: from elisha.daleco.biz (localhost [127.0.0.1])
	by elisha.daleco.biz (8.12.11/8.12.8) with ESMTP id iBUMq5xX003404;
	Thu, 30 Dec 2004 16:52:05 -0600 (CST)
	(envelope-from kadmin@elisha.daleco.biz)
Received: (from kadmin@localhost)
	by elisha.daleco.biz (8.12.11/8.12.8/Submit) id iBUMq4I4003403;
	Thu, 30 Dec 2004 16:52:04 -0600 (CST)
Date: Thu, 30 Dec 2004 16:52:04 -0600
From: Kevin Kinsey <kdk@daleco.biz>
To: questions@freebsd.org
Message-ID: <20041230225204.GA3396@elisha.daleco.biz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
cc: dtalk-ml@prairienet.org
Subject: Clock too fast?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
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, 30 Dec 2004 22:56:30 -0000

>Thank you for the suggestions.  Unfortunately, I've been through all
>that, including the rude values of minpoll and maxpoll, using multiple
>servers, and starting with a fresh drift file.  I'm pretty sure ntpd
>isn't the problem.  In addition, the hardware clock itself appears to be
>plenty accurate, as it is always correct within a second or two when I
>check it directly in BIOS ... and two other 5.3-STABLE hosts on the same
>network, with the same ntpd configuration, but on different hardware, do
>not have this problem, which began when I updated (reinstalled) to
>5.3-STABLE from 5.2.

[503] Thu 30.Dec.2004 16:51:10 [kadmin@archangel][~]
#sysctl kern.timecounter.choice
kern.timecounter.choice: TSC(800) ACPI-fast(1000) i8254(0) dummy(-1000000)

Last box I had trouble like this on was K6-2/500 on Asus p5a mobo.
Setting to i8254 worked in that case.  If you've not tried all the
possibilities, do so now.

I must also say that I *think* I had a box (around PII 200) that I
never got this resolved on (but I'm not sure how hard I tried....)

HTH,

Kevin Kinsey