From owner-freebsd-questions@FreeBSD.ORG Wed Mar 22 00:47:08 2006 Return-Path: X-Original-To: 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 1949116A420 for ; Wed, 22 Mar 2006 00:47:08 +0000 (UTC) (envelope-from sub02@freeode.co.uk) Received: from mail.freeode.co.uk (freeode.co.uk [213.162.123.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99D2843D53 for ; Wed, 22 Mar 2006 00:47:01 +0000 (GMT) (envelope-from sub02@freeode.co.uk) Received: from lexx.freeode.co.uk (lexx.freeode.co.uk [10.10.10.2]) by mail.freeode.co.uk (8.13.4/8.13.4) with ESMTP id k2M0kv6u033472; Wed, 22 Mar 2006 00:46:57 GMT (envelope-from sub02@freeode.co.uk) From: John Murphy To: Alfred Morgan Date: Wed, 22 Mar 2006 00:46:57 +0000 Message-ID: <7c61221qt0meet1dudmids5vgcisejjjth@4ax.com> References: <44204E79.4090408@experclick.com> In-Reply-To: <44204E79.4090408@experclick.com> X-Mailer: Forte Agent 1.93/32.576 English (American) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: clock drifts after upgrade from 5.x to 6.x X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sub02@freeode.co.uk List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Mar 2006 00:47:08 -0000 Alfred Morgan wrote: > > I have upgraded 4 different machines from various FreeBSD versions of > 5 to various versions of 6 and 3 of the machines has a problem where > the clock will drift very quickly slowing about 2 seconds per minute. Interesting. Were all the upgrades from versions less than 5.3 I wonder? Reason I ask is that many people (including me) seem to have started having problems with ntp around that time. There was a thread in the stable mailing list about it here: http://docs.freebsd.org/cgi/mid.cgi?20050401104508.GJ71384 Perhaps the ntp problem is related to what you're seeing and not an ntp problem at all. Someone raised a bug report at ntp.isc.org https://ntp.isc.org/bugs/show_bug.cgi?id=452 but it has had no action. Sorry it's only a hunch and not a solution. -- John.