linux-kernel - Re: 2.6.19-rc2 and very unstable NTP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0610270048470.6761@scrub.home>
Date:	Fri, 27 Oct 2006 01:06:39 +0200 (CEST)
From:	Roman Zippel <zippel@...ux-m68k.org>
To:	john stultz <johnstul@...ibm.com>
cc:	linux@...izon.com, linux-kernel@...r.kernel.org
Subject: Re: 2.6.19-rc2 and very unstable NTP

Hi,

On Thu, 26 Oct 2006, john stultz wrote:

> One of the recent changes was removing the in-kernel PPS code. This was
> done because there were no in-kernel users of the interface (the only
> ones being I believe in a variant of this LinuxPPS patch). While from
> the diffstat below it doesn't look like the patch affects the
> timekeeping code, it would be good to first reproduce the issue without
> the patch.

The recent patch by Jim Houston explains the misbehaviour. It seems the 
ntp daemon uses ADJ_OFFSET_SINGLESHOT for time adjustments, which is 
rather coarse-grained. By adding proper PPS support one should be able to 
get a more stable clock, but it's better done by someone who has the 
hardware to test this.

bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/