From owner-freebsd-current  Wed May  1 12:58: 2 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mailout10.sul.t-online.com (mailout10.sul.t-online.com [194.25.134.21])
	by hub.freebsd.org (Postfix) with ESMTP id EF50737B417
	for <current@freebsd.org>; Wed,  1 May 2002 12:57:47 -0700 (PDT)
Received: from fwd02.sul.t-online.de 
	by mailout10.sul.t-online.com with smtp 
	id 1730ER-0001sw-0M; Wed, 01 May 2002 21:57:43 +0200
Received: from dialin.t-online.de (340029380333-0001@[80.128.218.37]) by fmrl02.sul.t-online.com
	with esmtp id 1730EO-1MzlGCC; Wed, 1 May 2002 21:57:40 +0200
Received: from t-online.de (server [172.23.7.1])
	by dialin.t-online.de (8.11.6/8.11.6/Rock) with ESMTP id g41JvJC48016;
	Wed, 1 May 2002 21:57:19 +0200 (MEST)
Message-ID: <3CD0489F.D79EFF3F@t-online.de>
Date: Wed, 01 May 2002 21:57:19 +0200
From: Daniel Rock <D.Rock@t-online.de>
X-Mailer: Mozilla 4.7 [de] (X11; U; SunOS 5.8 i86pc)
X-Accept-Language: de, en
MIME-Version: 1.0
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: current@FreeBSD.ORG
Subject: Re: clock drift in -CURRENT
References: <64858.1020263148@critter.freebsd.dk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Sender: 340029380333-0001@t-dialin.net
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Poul-Henning Kamp schrieb:
> 
> When was your source tree from on that kernel ?
> 
> I'm not too confident in your diagnosis, mostly because we don't
> have a counter like you describe :-)
> 
> My guess is that ntpd get confused.
> 
> Please try a newer kernel, a number of bug(lets) have been fixed
> since march.
> 
> If it happens again, please email me the output of:
>         ntpdc -c peer
>         ntpdc -c loopi
>         ntpdc -c kerni
>         dmesg
> 
[...]

My kernel war relatively recent at the time of last boot - build
around March 2nd from -CURRENT sources a few hours before.

If someone runs -CURRENT with default HZ of 100 and moans 247 days
later, his -CURRENT cannot be called -CURRENT any more...

I am now running an up-to-date -CURRENT. I have set HZ=10000, so
I don't have to wait another 50 days. Hope this high HZ value has
no negative impact on the test.

I will inform you in 3 days if anything strange happens again.


Daniel

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message