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 for Android: free password hash cracker in your pocket

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

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

Hi,

On Fri, 27 Oct 2006, linux@...izon.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/