Date: Thu, 3 Nov 2005 15:48:07 -0500
To: john stultz <johnstul@us.ibm.com>
Cc: Jean-Christian de Rivaz <jc@eclis.ch>, linux-kernel@vger.kernel.org,
       dean@arctic.org
Subject: Re: NTP broken with 2.6.14
Message-ID: <20051103204807.GT9486@csclub.uwaterloo.ca>
References: <4369464B.6040707@eclis.ch> <1130973717.27168.504.camel@cog.beaverton.ibm.com> <43694DD1.3020908@eclis.ch> <1130976935.27168.512.camel@cog.beaverton.ibm.com> <43695D94.10901@eclis.ch> <1130980031.27168.527.camel@cog.beaverton.ibm.com> <43697550.7030400@eclis.ch> <1131046348.27168.537.camel@cog.beaverton.ibm.com> <20051103195124.GE9488@csclub.uwaterloo.ca> <1131048670.27168.573.camel@cog.beaverton.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1131048670.27168.573.camel@cog.beaverton.ibm.com>
User-Agent: Mutt/1.5.9i
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 979
Lines: 22

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.

> 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.

Len Sorensen
-
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/