| Re: [chrony-dev] Let the kernel write the sys clock to RTC |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
On Wed, May 19, 2010 at 10:00:09AM -0400, Piotr Grudzinski wrote:
> >Interesting.
> >
> >For me, 1.24 settles down to the same drift, and I can't imagine what
> >could be causing this.
>
> What system are you using for testing? Mine is a small 192MHz ARM 9
> based board. Kernel HZ is 100.
Mine is a full size x86_64 PC, currently running kernel 2.6.33.3
compiled with CONFIG_NOHZ.
> I ran ntpd program all night and this morning the estimated drift is 3.740.
> And it seems that the +- convention is opposite in chrony and ntpd. So the
> git chrony and ntpd seems to quite close.
I presume you have the rtcsync option enabled, maybe it somehow
affects the system clock? Does it change when it's disabled? For me,
the result is always the same.
> Also, for chrony and adjtimex, offset is always 0 and timeconstant is 2;
> for ntpd - offset is not 0 and timeconstant goes from 2 (on start) to 10.
That's ok, chrony doesn't use the kernel PLL discipline.
--
Miroslav Lichvar
---
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.