Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1946386AbWJ0LAZ (ORCPT ); Fri, 27 Oct 2006 07:00:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1946382AbWJ0LAZ (ORCPT ); Fri, 27 Oct 2006 07:00:25 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:38539 "EHLO scrub.xs4all.nl") by vger.kernel.org with ESMTP id S1946386AbWJ0LAY (ORCPT ); Fri, 27 Oct 2006 07:00:24 -0400 Date: Fri, 27 Oct 2006 12:58:37 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@scrub.home To: linux@horizon.com cc: johnstul@us.ibm.com, linux-kernel@vger.kernel.org Subject: Re: 2.6.19-rc2 and very unstable NTP In-Reply-To: <20061027091508.14771.qmail@science.horizon.com> Message-ID: References: <20061027091508.14771.qmail@science.horizon.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 989 Lines: 22 Hi, On Fri, 27 Oct 2006, linux@horizon.com wrote: > And given that, in the course of my experiments, I managed to reproduce > the problem with 2.6.17+linuxpps and 2.6.19-rc3 with the ntp.c patch, > but managed to make it go away with 2.6.19-rc3+linuxpps with the pps > source marked "noselect" (which results in identical kernel activity, > but doesn't actually use the returned timestamp for anything), I'm > looking pretty hard at ntpd right now. To analyze the kernel behaviour I would at least need the information fed to the kernel, e.g. by tracing the ntp daemon via "TZ=utc strace -f -tt -e trace=adjtimex -o ntpd.trace ..." and the ntp peer logs of same time period. Kernel boot messages and config might help as well. bye, Roman - 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/