From: john stultz <johnstul@us.ibm.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Jean-Christian de Rivaz <jc@eclis.ch>,
linux-kernel@vger.kernel.org, dean@arctic.org
Subject: Re: NTP broken with 2.6.14
Date: Thu, 03 Nov 2005 12:11:10 -0800 [thread overview]
Message-ID: <1131048670.27168.573.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <20051103195124.GE9488@csclub.uwaterloo.ca>
On Thu, 2005-11-03 at 14:51 -0500, Lennart Sorensen wrote:
> On Thu, Nov 03, 2005 at 11:32:28AM -0800, john stultz wrote:
> > Yep. Thats what I was guessing. For some reason time is running too
> > quickly on your system. Since it is more then +/-500ppm NTP gives up and
> > won't sync.
> >
> > Time running too fast can have a number of causes.
> >
> > Could you open a bugme bug on this and tag me as the owner?
> > http://bugzilla.kernel.org
> >
> > Also attach dmesg output and we'll see if that doesn't provide more
> > clues.
>
> I have no idea if this is related at all, but I have had system time
> speed issues on my machine for a while too.
>
> With 2.6.8 it always ran fine, with 2.6.12 it seemed to gain around 10
> minutes per hour, and so far today with 2.6.14 it seems to be gaining
> about 3 or 4 minutes per hour. These are all Debian kernels, although I
> hope they haven't added/removed anything that would affect this.
>
> This is happening on an Asus A7N8X-E-DX with an Athlon XP 2800+. I have
> acpi enabled, so who knows if that is what is breaking things. There
> does seem to have been time keeping issues on ati chipsets big time in
> recent kernels, and some other acpi issues at times, so it wouldn't
> surprise me if a fix for one issue causes problems on another chipset.
> The chipset on this board is the nforce2.
Yea, we have some issues with a few specific chipsets, but those were
not regressions to my knowledge.
Hmm. Check bug #5038 to see if sounds familiar.
http://bugzilla.kernel.org/show_bug.cgi?id=5038
thanks
-john
next prev parent reply other threads:[~2005-11-03 20:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 23:05 Jean-Christian de Rivaz
2005-11-02 23:21 ` john stultz
2005-11-02 23:37 ` Jean-Christian de Rivaz
2005-11-03 0:15 ` john stultz
2005-11-03 0:45 ` Jean-Christian de Rivaz
2005-11-03 1:07 ` john stultz
2005-11-03 2:26 ` Jean-Christian de Rivaz
2005-11-03 19:32 ` john stultz
2005-11-03 19:51 ` Lennart Sorensen
2005-11-03 20:11 ` john stultz [this message]
2005-11-03 20:48 ` Lennart Sorensen
2005-11-03 21:00 ` john stultz
2005-11-03 21:12 ` Lennart Sorensen
2005-11-03 21:28 ` Jean-Christian de Rivaz
2005-11-03 21:12 ` Jean-Christian de Rivaz
2005-11-03 21:41 ` john stultz
2005-11-03 22:10 ` Jean-Christian de Rivaz
2005-11-03 22:54 ` john stultz
2005-11-04 0:15 ` Jean-Christian de Rivaz
2005-11-04 0:40 ` john stultz
2005-11-04 2:50 ` Jean-Christian de Rivaz
2005-11-06 22:49 ` Hans-Peter Jansen
2005-11-07 21:44 ` Jean-Christian de Rivaz
2005-11-04 12:40 ` Maciej W. Rozycki
2005-11-02 23:24 ` john stultz
2005-11-03 0:36 ` Roman Zippel
2005-11-03 1:13 ` Jean-Christian de Rivaz
2005-11-03 9:42 ` Roman Zippel
2005-11-04 3:44 Brown, Len
2005-11-04 4:07 ` john stultz
2005-11-04 13:51 ` Lennart Sorensen
2005-11-04 16:39 ` Jean-Christian de Rivaz
2005-11-04 17:41 ` Jean-Christian de Rivaz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1131048670.27168.573.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=dean@arctic.org \
--cc=jc@eclis.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®