mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Luyer" <david@luyer.net>
To: <linux-kernel@vger.kernel.org>
Cc: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>
Subject: RE: Linux 2.4.19ac3rc3 on IBM x330/x340 SMP - "ps" time skew
Date: Wed, 31 Jul 2002 21:01:45 +1000	[thread overview]
Message-ID: <00b601c23881$a8dfa180$638317d2@pacific.net.au> (raw)
In-Reply-To: 

I wrote:

> In Linux 2.4.19ac3rc3 on IBM x330/x340 SMP systems we're seeing this:
> 
> luyer@praxis8:~$ ps auxwww | tail -1
> luyer     1025  0.0  0.0  1276  352 pts/2    S    Aug06   0:00 tail -1
> luyer@praxis8:~$ date
> Wed Jul 31 12:35:16 EST 2002

(UP systems are fine, SMP have this problem)

Reason:

luyer@praxis8:~$ ps --info 2>&1 | grep Hertz
EUID=111 TTY=136,3 Hertz=50

procps is getting the hertz value wrong, it's computing it as:

  h = (unsigned long)( (double)jiffies/seconds/smp_num_cpus );

but we're only getting timer interrupts on CPU 0, and hence
jiffies is only incrementing once per 100th of a second.

luyer@praxis8:~/procps/procps-2.0.7.orig/proc$ cat /proc/interrupts
           CPU0       CPU1
  0:   52459351          0  local-APIC-edge  timer
  1:          0          2    IO-APIC-edge  keyboard
  2:          0          0          XT-PIC  cascade
 24:     883655     863043   IO-APIC-level  ips
 26:          7          9   IO-APIC-level  aic7xxx
 27:          8          8   IO-APIC-level  aic7xxx
 28:   97880608   96542591   IO-APIC-level  eth0
NMI:          0          0
LOC:   52456889   52456887
ERR:          0
MIS:          0

procps version is 2.0.7 (Debian 3.0).

Where's the mistake -- should timer interrupts be on both
CPUs (I think this is the problem), or is procps miscalculating
Hz (seems less likely, someone would have noticed by now...)?

David.


             reply	other threads:[~2002-07-31 10:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-31 11:01 David Luyer [this message]
2002-07-31 13:28 ` Alan Cox
2002-07-31 12:59   ` David Luyer
2002-07-31 14:26     ` Alan Cox
2002-07-31 13:18       ` David Luyer
2002-07-31 13:31       ` Dana Lacoste
2002-07-31 13:38         ` David Luyer
2002-07-31 15:04           ` Alan Cox
2002-07-31 13:57             ` David Luyer
2002-07-31 16:15       ` NMI watchdog, die(), & console_loglevel Jonathan Lundell
2002-07-31 19:14       ` Linux 2.4.19ac3rc3 on IBM x330/x340 SMP - "ps" time skew Albert D. Cahalan
2002-08-01  0:37         ` Alan Cox
2002-07-31 23:49           ` Dave Jones
2002-08-01  1:30             ` Alan Cox
2002-08-01  0:19               ` Dave Jones
2002-07-31 23:42     ` Lincoln Dale
2002-08-01  1:33       ` Albert D. Cahalan
2002-08-01  3:34         ` Martin J. Bligh
2002-08-01 14:16           ` Alan Cox
2002-08-01  8:49         ` Benjamin Herrenschmidt
2002-08-01 11:40         ` Lincoln Dale
2002-08-01 18:26           ` Albert D. Cahalan
2002-08-01 14:15         ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-07-31  2:46 David Luyer

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='00b601c23881$a8dfa180$638317d2@pacific.net.au' \
    --to=david@luyer.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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

all inboxes | Powered by JetHome®