From: David Ford <david+challenge-response@blue-labs.org>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: /proc or ps tools bug? 2.6.3, time is off
Date: Wed, 25 Feb 2004 16:39:20 -0500 [thread overview]
Message-ID: <403D1608.7060706@blue-labs.org> (raw)
In-Reply-To: <20040225091425.GA16783@elektroni.ee.tut.fi>
powerix root # grep cpu /proc/stat; cat /proc/uptime
cpu 403880 466666 580559 15017904 475868 10864 3030
cpu0 403880 466666 580559 15017904 475868 10864 3030
186882.63 154999.74
(gdb) p 403880 +466666 +580559 +15017904 +475868 +10864 +3030
$1 = 16958771
(gdb) p 16958771/186882.63
$2 = 90.745571164104447
Hmm, not quite 100.0
david
Petri Kaukasoina wrote:
>Hi,
>
>I reported the same problem some time ago. Could you type
>
>grep cpu /proc/stat; cat /proc/uptime
>
>for example, I get
>
>cpu 140708 1489 43735 21209021 292168 4879 4192
>cpu0 140708 1489 43735 21209021 292168 4879 4192
>216925.15 215037.34
>
>Then add jiffies and divide by uptime:
>
>(140708+1489+43735+21209021+292168+4879+4192)/216925.15 = 100.01695
>
>which is not 100 here as it should be. (On kernel 2.2.* I have it exactly
>100). ps uses Hertz=100 but it should be 170 ppm larger which makes an error
>of about 15 seconds a day. (Running without ntpd doesn't fix it.)
>
>
prev parent reply other threads:[~2004-02-25 21:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 1:58 /proc or ps tools bug? 2.6.3, time is off David Ford
2004-02-25 1:54 ` Albert Cahalan
2004-02-25 5:10 ` David Ford
2004-02-25 3:27 ` Albert Cahalan
2004-02-25 16:28 ` George Anzinger
2004-02-25 16:04 ` Albert Cahalan
2004-02-25 20:45 ` George Anzinger
2004-02-25 19:16 ` Albert Cahalan
2004-02-25 21:10 ` George Anzinger
2004-02-26 1:52 ` john stultz
2004-02-26 23:06 ` George Anzinger
2004-02-26 23:10 ` john stultz
2004-02-27 0:20 ` George Anzinger
2004-04-13 22:38 ` john stultz
2004-04-13 22:59 ` George Anzinger
2004-04-14 12:10 ` Tim Schmielau
2004-04-14 17:03 ` George Anzinger
2004-04-14 18:28 ` john stultz
2004-04-15 10:37 ` Petri Kaukasoina
2004-04-15 11:05 ` Tim Schmielau
2004-04-15 16:14 ` Petri Kaukasoina
2004-05-01 13:51 ` Tim Schmielau
2004-05-02 1:41 ` Andrew Morton
2004-05-02 1:59 ` Tim Schmielau
2004-05-04 2:40 ` john stultz
2004-05-04 6:12 ` Tim Schmielau
2004-05-04 14:59 ` john stultz
2004-05-04 16:50 ` Tim Schmielau
2004-05-07 0:33 ` George Anzinger
2004-05-07 1:21 ` john stultz
2004-05-07 20:41 ` George Anzinger
2004-05-07 21:38 ` john stultz
2004-02-26 23:14 ` George Anzinger
2004-02-25 9:14 ` Petri Kaukasoina
2004-02-25 9:18 ` Petri Kaukasoina
2004-02-25 21:39 ` David Ford [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=403D1608.7060706@blue-labs.org \
--to=david+challenge-response@blue-labs.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.