Bug#410415: [pkg-ntp-maintainers] Bug#410415: ntpdate unable to maintain stable time

Clayton ckoeni at gmail.com
Sat Feb 10 18:07:04 CET 2007


On Sat, 10 Feb 2007 17:28:07 +0100
Kurt Roeckx <kurt at roeckx.be> wrote:

> On Sat, Feb 10, 2007 at 11:29:41PM +0800, clayton wrote:
> > Package: ntpdate
> > Version: 1:4.2.2.p4+dfsg-1
> > 
> > 10 Feb 04:46:56 ntpdate[9287]: step time server 195.234.188.3
> > offset -6975.269708 sec 10 Feb 06:08:48 ntpdate[13281]: step time
> > server 80.127.4.179 offset -2070.299497 sec
> 
> So, your clock's rate is off by about 0.42 seconds/second
> 
> > 10 Feb 06:33:20 ntpdate[13312]: step time server 80.127.4.179
> > offset -598.189759 sec
> 
> About 0.40 seconds/second
> 
> > 10 Feb 06:40:20 ntpdate[13330]: step time server 192.87.106.3
> > offset -175.634248 sec
> 
> About 0.41 seconds/second
> 
> And I'm guessing the rest will show about the same thing.
> This looks like either a hardware or kernel problem to me.

Kurt, thanks for the prompt reply. This is a server that has been running continually since last July. This problem started abruptly some time since the new year. I roll my own kernels, and I am seeing the build date for my last kernel (where I moved from 2.6.17 to 2.6.18) is 6 Jan 2007, which seems way more then coincidental. So I am voting for a kernel problem. Would you like to reassign this to kernel 2.6.18? I am using the latest and greatest standard Debian kernel source from testing. (On a old thinkpad 600e, if hardware is important information here.)

Clayton




More information about the pkg-ntp-maintainers mailing list