Date: Thu, 26 Oct 2006 15:01:20 +0200 (CEST)
From: Roman Zippel <zippel@linux-m68k.org>
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: <20061026123051.3831.qmail@science.horizon.com>
Message-ID: <Pine.LNX.4.64.0610261449500.6761@scrub.home>
References: <20061026123051.3831.qmail@science.horizon.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1449
Lines: 32

Hi,

On Thu, 26 Oct 2006, linux@horizon.com wrote:

> > Did you ask the author? It would really help to have more specific 
> > information here, e.g. what kernel interfaces are actually used in this 
> > configuration.
> 
> Er... I thought I *was* asking the authors of the Linux kernel/time*
> code.
> 
> If you're deeply suspiscious of a simple device driver, with publicly
> available code, that adds timestamping to the handling of DCD changed
> events from the serial ports, and exports those timestamps to user space,
> I can remove it.  The Acutime 2000 can timestamp pulses sent to it
> (via the RTS line), so I can get sub-microsecond time measurements anyway.

I don't have this hardware, so I can only guess and the less information I 
get the broader I have to guess. Sorry, but currently I don't have the 
time to go on such a broad hunt. Someone familiar with this code should a 
far easier time localizing the problem. It's not just kernel driver, there 
is also lot of code in user space which converts the data to time 
adjustments. There is also more than one way to adjust time, so I need 
more specific information about what is happening and what is expected to 
happen.

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/