Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756010AbZCCUB5 (ORCPT ); Tue, 3 Mar 2009 15:01:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750774AbZCCUBt (ORCPT ); Tue, 3 Mar 2009 15:01:49 -0500 Received: from e35.co.us.ibm.com ([32.97.110.153]:59924 "EHLO e35.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753356AbZCCUBs (ORCPT ); Tue, 3 Mar 2009 15:01:48 -0500 Subject: Re: Linux 2.6.29-rc6 From: john stultz To: Jesper Krogh Cc: Thomas Gleixner , Linus Torvalds , Linux Kernel Mailing List , Len Brown In-Reply-To: <49ACC853.8070205@krogh.cc> References: <49A6F39F.9040801@krogh.cc> <49A6FEE2.90700@krogh.cc> <1f1b08da0902261319k7a60d80xaafc1101facfd2d9@mail.gmail.com> <49A70B24.6090706@krogh.cc> <1235685269.6811.11.camel@localhost.localdomain> <1235687483.6811.26.camel@localhost.localdomain> <49A78C79.304@krogh.cc> <1235766936.7402.5.camel@localhost.localdomain> <49ABACA0.3090300@krogh.cc> <1236029277.7756.0.camel@localhost.localdomain> <49ACC853.8070205@krogh.cc> Content-Type: text/plain Date: Tue, 03 Mar 2009 11:53:46 -0800 Message-Id: <1236110026.6068.18.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2058 Lines: 53 On Tue, 2009-03-03 at 07:04 +0100, Jesper Krogh wrote: > john stultz wrote: > > On Mon, 2009-03-02 at 10:53 +0100, Jesper Krogh wrote: > >> john stultz wrote: > >>> Ok, so it seems ntp hasn't really had a chance to settle down, its only > >>> made a 10ppm adjustment so far. NTPd will stop corrections at ~ > >>> +/-500ppm, so you're not at that bound yet, where things would be really > >>> broken. > >>> > >>> If the affected kernel isn't resetting in the logs anymore, I'd be > >>> interested in what the new ppm value is. > >> After 20 hours.. its still resetting. > >> Mar 2 10:43:24 quad12 ntpd[4416]: synchronized to 10.194.133.12, stratum 4 > >> Mar 2 10:50:37 quad12 ntpd[4416]: time reset -1.103654 s > > > > So what's the "ntpdc -c kerninfo" output now? > > Mar 3 06:41:10 quad12 ntpd[4416]: time reset -0.813957 s > Mar 3 06:45:20 quad12 ntpd[4416]: synchronized to LOCAL(0), stratum 13 > Mar 3 06:45:36 quad12 ntpd[4416]: synchronized to 10.194.133.12, stratum 4 > Mar 3 06:51:57 quad12 ntpd[4416]: synchronized to 10.194.133.13, stratum 4 > Mar 3 07:00:29 quad12 ntpd[4416]: time reset -0.783390 s > jk@quad12:~$ ntpdc -c kerninfo > pll offset: 0 s > pll frequency: -28.691 ppm This is baffling. You've only gone from -34.754ppm to -28.691ppm in over a day? And you're still not syncing? If the calibration was so bad that NTP couldn't sync, I'd expect the freq value to hit +/-500ppm before it gave up. This just doesn't follow my expectations. Could you provide: /usr/sbin/ntpdc -c version Do you see the same behavior if you drop all but one server (including the local clock: 127.127.1.0)? You might also add "minpoll 4 maxpoll 4" to the server line to speed up testing. Actually, if you could, I'd be interested if you could send your ntp.conf thanks -john -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/