From owner-freebsd-stable@FreeBSD.ORG Thu Dec 30 23:06:45 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E624916A4CE for ; Thu, 30 Dec 2004 23:06:45 +0000 (GMT) Received: from ezekiel.daleco.biz (cdm-66-76-92-18.cart.cox-internet.com [66.76.92.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F4E843D31 for ; Thu, 30 Dec 2004 23:06:45 +0000 (GMT) (envelope-from kadmin@ezekiel.daleco.biz) Received: from ezekiel.daleco.biz (localhost [127.0.0.1]) by ezekiel.daleco.biz (8.13.1/8.13.1) with ESMTP id iBUN6ip8087037; Thu, 30 Dec 2004 17:06:44 -0600 (CST) (envelope-from kadmin@ezekiel.daleco.biz) Received: (from kadmin@localhost) by ezekiel.daleco.biz (8.13.1/8.13.1/Submit) id iBUN6h2k087036; Thu, 30 Dec 2004 17:06:43 -0600 (CST) (envelope-from kadmin) Date: Thu, 30 Dec 2004 17:06:43 -0600 From: Kevin Kinsey To: FreeBSD Stable Message-ID: <20041230230643.GA87010@ezekiel.daleco.biz> References: <20041230222903.GA16002@archangel.daleco.biz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041230222903.GA16002@archangel.daleco.biz> User-Agent: Mutt/1.4.2.1i cc: dtalk-ml@prairienet.org Subject: Re: clock running fast X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 23:06:46 -0000 > [ rc.conf and ntp.conf snipped ] > > 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. > > - -- > David Talkington > dtalk-ml@prairienet.org I apparently misposted this earlier, my apologies. Have you tried all possible values for kern.timecounter.hardware? #sysctl kern.timecounter.choice My most recent encounter with this issue, a K6-2/500 on an Asus P5A mobo, needed "i8254". HTH, Kevin Kinsey