From: Daniel Jacobowitz <dan@debian.org>
To: Frank van Maarseveen <frankvm@frankvm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13 SMP on Athlon X2: nanosleep returning waay to soon, clock_gettime(CLOCK_REALTIME...) proceeding too fast
Date: Sun, 4 Sep 2005 10:27:28 -0400 [thread overview]
Message-ID: <20050904142728.GA32691@nevyn.them.org> (raw)
In-Reply-To: <20050904113915.GA13954@janus>
On Sun, Sep 04, 2005 at 01:39:15PM +0200, Frank van Maarseveen wrote:
> After replacing the kernel on a fresh FC4 install with a stock 2.6.13
> (using gcc 3.2) and my own config it appears that the clock is going too
> fast: it gains at least an hour every 12 hours or so. FC4 kernel (rpm:
> kernel-2.6.11-1.1369_FC4) seems ok
Mind sticking this information in bugzilla.kernel.org, bug 5105?
> annotated output:
>
> CPU0 CPU1 Total
> -----------------------
> 1 0 + 251 = 251
> 2 0 + 251 = 251
> 3 0 + 251 = 251
> 4 0 + 251 = 251
> 5 0 + 251 = 251
> 6 52 + 196 = 248 <== (?)
> 7 251 + 0 = 251
> 8 251 + 0 = 251
> 9 251 + 0 = 251
> 10 251 + 0 = 251
> 11 251 + 0 = 251
> 12 251 + 0 = 251
> 13 251 + 0 = 251
> 14 251 + 0 = 251
> 15 251 + 0 = 251
> 16 147 + 1 = 148 <==
> 17 0 + 252 = 252
Hmmmmmmmmmmmmmmmmmmmmmm, very interesting.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-09-04 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 7:41 lost ticks and Hangcheck Nathan Becker
2005-08-19 9:45 ` Kurt Wall
2005-08-20 0:22 ` Nathan Becker
2005-08-20 0:34 ` john stultz
2005-08-20 9:50 ` Nathan Becker
2005-08-30 13:47 ` Frank van Maarseveen
2005-09-04 11:39 ` 2.6.13 SMP on Athlon X2: nanosleep returning waay to soon, clock_gettime(CLOCK_REALTIME...) proceeding too fast Frank van Maarseveen
2005-09-04 14:27 ` Daniel Jacobowitz [this message]
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=20050904142728.GA32691@nevyn.them.org \
--to=dan@debian.org \
--cc=frankvm@frankvm.com \
--cc=linux-kernel@vger.kernel.org \
/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