[ntp:questions] Re: ntpd under linux kernel 2.6.1

Ryan ntpthis at ddnsupportDOT.com
Sat Jan 24 03:30:08 UTC 2004

On Fri, 23 Jan 2004 10:46:26 +0900, Kalin KOZHUHAROV
<kalin at ThinRope.net> wrote:

>Ruben Navarro Huedo wrote:
>> Hello friends:
>> Our system is a Debian Woody + backports running now kernel 2.6.1.
>> We have to run this kernel becouse 2.4.24 has a lot of problems with ham radio
>> ports.
>> The problem is that ntpd is not running very well with this kernel.
>> pool reports that our server is unreachable:
>>     -94.4 __________________________________________________
>> Have we forgotten some kernel option?
>> Our ntp version:
>> linux:~# dpkg -l | grep ntp
>> ii  ntp            4.1.2a-1.backp Daemon and utilities for full NTP v4 timekee
>I use ntp-4.1.2 on linux-2.6.1 and linux-2.6.0 and it dies in somewhere between an hour and a day. No idea why, but the same version on 2.4.23 works OK.
>It seems that things changed in 2.6 with the introduction of a new nanosecond call (found from other posts), but nobody seems to have problems?
>I was thinkinbg to use daemontools to monitor the ntpd and restart it when it dies, but for now just a plan (Anybody with ready run scripts?)
>Thats the sitiation here, Gentoo linux 1.4.

I have two systems running solid on 2.6.1 (and 2.6.0 before that).  What
I miss is that with 2.4.20 (and the PPSkit) I was able to use my M12+
for super accurate time.  It doesn't work with 2.6.1. :(

here is one of 'em (Pentium 200)
ntp_gettime() returns code 0 (OK)
  time c3bc63aa.97014000  Fri, Jan 23 2004 19:23:22.589, (.589863),
  maximum error 402716 us, estimated error 777 us
ntp_adjtime() returns code 0 (OK)
  modes 0x0 (),
  offset 1237.000 us, frequency -51.704 ppm, interval 4 s,
  maximum error 402716 us, estimated error 777 us,
  status 0x1 (PLL),
  time constant 6, precision 1.000 us, tolerance 512 ppm,
  pps frequency 0.000 ppm, stability 512.000 ppm, jitter 200.000 us,
  intervals 0, jitter exceeded 0, stability exceeded 0, errors 0.

When you have your problem, what shows up in the log?

Ryan (take of the extra dot to respond, or reply here)

More information about the questions mailing list