Re: NTP broken with 2.6.14

[john stultz <johnstul@us.ibm.com>]

On Thu, 2005-11-03 at 15:48 -0500, Lennart Sorensen wrote:
> On Thu, Nov 03, 2005 at 12:11:10PM -0800, john stultz wrote:
> > Yea, we have some issues with a few specific chipsets, but those were
> > not regressions to my knowledge. 
> 
> Well my nforce2 worked with 2.6.8 and earlier, and I believe it was even
> fine with 2.6.10 and 2.6.11, but certainly 2.6.12 ran rather awful time
> sync wise, and 2.6.14 appears so far to be running a little fast,
> although I can't say for sure.  It is much better than 2.6.12 was.  It
> may be that 2.6.14 is running correctly, but that the previous drift has
> caused something to need to be realigned.

You could try disabling NTP and running the python script I sent out
earlier in this thread to determine your systems ppm drift. Outside
+/-500ppm is def broken, outside of +/-250ppm is probably broken,
outside +/-100ppm isn't great but correctable and inside +/-100ppm is
(unfortunately) pretty average for most hardware.

> 
> > Hmm. Check bug #5038 to see if sounds familiar.
> > http://bugzilla.kernel.org/show_bug.cgi?id=5038
> 
> I was seeting WAY more drift than that with 2.6.12.

Ok, do you want to open your own bug on this and we'll mark them
duplicate as needed?

Please attach dmesg output to the bug as well.

thanks
-john


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