Re: Linux 2.6.29-rc6

[Jesper Krogh]

john stultz wrote:
> On Mon, 2009-03-02 at 10:53 +0100, Jesper Krogh wrote:
> > john stultz wrote:
> > > Ok, so it seems ntp hasn't really had a chance to settle down, its only
> > > made a 10ppm adjustment so far. NTPd will stop corrections at ~
> > > +/-500ppm, so you're not at that bound yet, where things would be really
> > > broken.
> > >
> > > If the affected kernel isn't resetting in the logs anymore, I'd be
> > > interested in what the new ppm value is.
> > After 20 hours.. its still resetting.
> > Mar  2 10:43:24 quad12 ntpd[4416]: synchronized to 10.194.133.12, stratum 4
> > Mar  2 10:50:37 quad12 ntpd[4416]: time reset -1.103654 s
>
> So what's the "ntpdc -c kerninfo" output now?

Mar  3 06:41:10 quad12 ntpd[4416]: time reset -0.813957 s
Mar  3 06:45:20 quad12 ntpd[4416]: synchronized to LOCAL(0), stratum 13
Mar  3 06:45:36 quad12 ntpd[4416]: synchronized to 10.194.133.12, stratum 4
Mar  3 06:51:57 quad12 ntpd[4416]: synchronized to 10.194.133.13, stratum 4
Mar  3 07:00:29 quad12 ntpd[4416]: time reset -0.783390 s
jk@quad12:~$ ntpdc -c kerninfo
pll offset:           0 s
pll frequency:        -28.691 ppm
maximum error:        1.0433 s
estimated error:      0 s
status:               0001  pll
pll time constant:    4
precision:            1e-06 s
frequency tolerance:  500 ppm
jk@quad12:~$ w
 07:03:17 up 1 day, 16:59,  1 user,  load average: 0.00, 0.00, 0.00


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/