Hi,
On Fri, 27 Oct 2006, [email protected] 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
