From owner-freebsd-questions@FreeBSD.ORG Mon Jan 17 21:05:26 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 92E1216A4D1 for ; Mon, 17 Jan 2005 21:05:26 +0000 (GMT) Received: from ns1.tiadon.com (SMTP.tiadon.com [69.27.132.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 333F943D1F for ; Mon, 17 Jan 2005 21:05:26 +0000 (GMT) (envelope-from kdk@daleco.biz) Received: from [69.27.131.0] ([69.27.131.0]) by ns1.tiadon.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 17 Jan 2005 15:05:40 -0600 Message-ID: <41EC2892.2050802@daleco.biz> Date: Mon, 17 Jan 2005 15:05:22 -0600 From: Kevin Kinsey User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John References: <20050117144715.A29157@starfire.mn.org> In-Reply-To: <20050117144715.A29157@starfire.mn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 17 Jan 2005 21:05:41.0023 (UTC) FILETIME=[4D1F02F0:01C4FCD8] cc: freebsd-questions@freebsd.org Subject: Re: Kernel time-keeping adjustments - how to tune? 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: Mon, 17 Jan 2005 21:05:26 -0000 John wrote: >OK - on my FreeBSD 5.3-STABLE system, as I have documented (cf: >message thread Re: ntpd problems since upgrading to 5.3), ntpd >won't run, even with an identical configuation to the 5.2.1 system >next to it. Furthermore, when I run adjkerntz -a, it totally whacks >the system's ability to keep time - it races forward at quite a >high rate. ntpdate runs, and sets the time correctly. > >At one point, something managed to get the timekeeping parameters >pretty near normal - less than a second of drift per hour (much >better than the 40% rate it is now - it gains about 24 seconds PER >MINUTE). Then I ran adjkerntz -a again, just to see if it really >was the culprit. It does seem that it is adjkerntz that is causing >(or triggering) the problem, but now I can't get the system back >to a decent time-keeping rate. Whatever it was I stumbled across >before, I'm not finding it again now. > >Now, it doesn't appear that adjkerntz itself has changed in YEARS, >so it must be some change in the system call operation, parameters, >or data structures that is causing this. > >So - since I don't seem to be able to stumble across what I did >right before to get the timekeeping somewhat near normal, I am >wondering if there's a manual way to reach them. > > I read through the cited thread, and don't see any replies; nor do I see enough explanation to give you any magic beans. Of course, I'm no one's fairy godmother... > the clock on my 5.3-STABLE system is RACING. > It is going at almost twice as fast as real time. Hmm, that might mean something. What do you get from: sysctl -a | grep timecounter ?? IANAE, but I wonder if ntpd is going to be able to sync up until the local clock runs realistically.... Kevin Kinsey