Re: Re: time is running out

> Der Herr Hofrat wrote:
> >>Could this also be the cause of CLOCK_GPOS running 150us/s (13 sec in 24h) faster
> >>than CLOCK_REALTIME? I have reported this problem before, but no answer/fix yet.
> >>
> > 
> > Hi !
> > 
> >  just ran 2.4.26 (Slackware 10.0 default config) and compared this to 2.4.27-rtl-3.2-rc1
> > (with the fixes from latest CVS) - time drift seems to be the same for both setups (5s/12h
> > vs 4s/12h) so I assume that this is a linux inprecision issue and not realy related to
> > rtlinux - checked my firewall that has an uptime of 235 days - offset is -216 seconds as
> > the box has not ntpd running - linux 2.2.13 (486/75), so I guess drifts in the range of a
> > few seconds/day are not that unusual. Does anbody else see any increased drift of ntp with
> > older rtlinux versions running ?
> 
> So the CLOCK_GPOS is only driven by the linux kernel, untouched by rtlinux? I'm about to test
> running a plain linux kernel to see if I get the same drift as before. Unfortunately since
> a few days I can't contact a ntp server due to a firewall problem.
> 
> I can't believe a drift of a few seconds per day is normal. Even a 3$ watch performs better
> than that. The strange thing is that the real-time clocks seems to run at the right pace.
> Every night I run ntpdate -su someserver followed by hwclock --systohc. In the logs I always
> see the (world) clock being adjusted about 13 seconds. And measuring the difference in clock
> speed of CLOCK_GPOS and CLOCK_REALTIME gives 151 us/s (on all our boxes). 151 us/s * 3600 s * 24
> is also 13 s! So CLOCK_REALTIME is exacty OK, but CLOCK_GPOS runs away.
> 
> >  Also what do you have in /etc/ntp.drift ??
>
did you check with the latest CVS changes ?
I had CLOCK_GPOS running - but I don't see that
behavior any longer with the changes (recompiling
the kernel and rtlinux)

hofrat 
_______________________________________________
Rtl mailing list
[email protected]
http://www2.fsmlabs.com/mailman/listinfo/rtl