[pkg-ntp-maintainers] Bug#559634: Bug#559634: no kernel sync and "ntpdc -c kerninfo" reports incorrect estimates of time on Xen dom0

[Kurt Roeckx]

On Sat, Dec 05, 2009 at 08:00:23PM -0500, Michael Bilow wrote:
> 
> I checked when I started this reply, and I was seeing 116.892 ppm
> from "ntpdc -c kerninfo". I just checked it again a few minutes
> later, and it is 57.596 ppm. This is not good.

This is clearly not normal.  Everything seems to point to the
kernel being broken.  As far as I know it's kernel that calculates
the new frequency.  The kerninfo will just read what info the
kernel has now.

> There does not seem to be much consistency in the "time reset"
> corrections, some positive and some negative but never more than
> 25ms; here are all of them logged for 4th and 5th Dec:

I guess you mean 250 ms.  It only does it above 0.125 or 0.128
or something.

> (Providence)
> Dec  4 00:39:55 virtual1 ntpd[2722]: time reset -0.189828 s
> Dec  4 02:06:25 virtual1 ntpd[2722]: time reset +0.171192 s
> Dec  4 05:21:01 virtual1 ntpd[2722]: time reset -0.157675 s
> Dec  4 08:40:53 virtual1 ntpd[2722]: time reset +0.128741 s
> 
> (Boston)
> Dec  5 00:07:29 virtual1 ntpd[3462]: time reset -0.210643 s
> Dec  5 00:41:51 virtual1 ntpd[3462]: time reset -0.160555 s
> Dec  5 03:58:00 virtual1 ntpd[3462]: time reset +0.145374 s

> I would be open to
> deleting the drift file and restarting the daemon if you think that
> would be a worthwhile test.

I don't think that's going to help.


Kurt