From: Mario Vanoni <vanonim@bluewin.ch>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 2.6.1-rc1-mm1: kernel or NFS problem?
Date: Fri, 02 Jan 2004 15:48:36 +0100 [thread overview]
Message-ID: <3FF584C4.2000305@bluewin.ch> (raw)
a) not in lkml, cc if needed
b) 5 machines otherwise 100% working, congrats
c) test on 4 machines, the 5th is production, taboo
d) top used: 2x 2.0.16, 2x 3.1.0
Scenario:
machine 1: top, sees himself, <1% CPU
machine 2: ssh to machine 1 ; top
machine 1: top sees 2 top's, <1% CPU each
machine 2: reboot with ssh _active_ with top
machine 1: the top from machine 2 is not killed
and consumes now >99% CPU,
must be killed explicitly
Same behaviour on 4 machines,
UP's Celeron-1000+512MBmem & P4-3066HT+1GBmem,
dual SMP's P3-550+1GBmem & P3-1266+2GBmem.
Sar(1) -U ALL 1 0 reports the same values as top(1).
It's not a procps problem, same conditions:
machine 1: top and sar -U ALL 1 0
machine 2: ssh to machine 1; sar -U ALL 1 0
machine 1: ps -efw sees sar, top no CPU used
machine 2: reboot with ssh _active_ with sar -U ALL 1 0
machine 1: top no CPU usage, according ps -efw sar -U ALL 1 0
and corresponding sadc 1 are always active,
killall sar kills both
The ethernet is 10Mb, mixed RJ and BNC connectors.
Mario
reply other threads:[~2004-01-02 14:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3FF584C4.2000305@bluewin.ch \
--to=vanonim@bluewin.ch \
--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
Powered by JetHome