From: "zwpeng" <zwpeng@etang.com>
To: linux-kernel@vger.kernel.org
Subject: 99% CPU by kswapd on kernel 2.4.13
Date: Sun, 4 Nov 2001 01:24:47 +0800 (CST) [thread overview]
Message-ID: <3BE4285F.17379@mail-smtp2> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3694 bytes --]
Hi,
I'v noticed that Mr Les Schaffer <schaffer@optonline.net> had reported such
problem on Oct 30 in his mail entiled "2.4.13 (SMP): kswapd working furiously,
to no effect". So this mail is just to say that the problem had hit more than
one persons.
I encountered this kswapd problem yesterday after the machine ruuning for 22 hours:
kswapd crazily use 99% of CPU time even if I switched to single mode.
About half an hour ago, when I starting build the newly 2.2.20 kernel and
opened a Mozilla session, I noticed that kswapd got crazy again:
12:48am up 1 day, 7:05, 14 users, load average: 2.38, 3.01, 2.37
76 processes: 72 sleeping, 4 running, 0 zombie, 0 stopped
CPU states: 0.0% user, 99.6% system, 0.3% nice, 0.0% idle
Mem: 385280K av, 361776K used, 23504K free, 0K shrd, 10744K buff
Swap: 128484K av, 1160K used, 127324K free 187740K cached
PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
5 root 19 0 0 0 0 RW 0 99.0 0.0 9:37 kswapd
8337root 17 5 1268 1268 1068 R N 0 0.9 0.3 0:05 top
1 root 8 0 476 476 412 S 0 0.0 0.1 0:04 init
2 root 9 0 0 0 0 SW 0 0.0 0.0 0:02 keventd
3 root 9 0 0 0 0 SW 0 0.0 0.0 0:00 kapm-idled
4 root 19 19 0 0 0 SWN 0 0.0 0.0 0:00 ksoftirqd_CP
6 root 9 0 0 0 0 SW 0 0.0 0.0 0:00 bdflush
7 root 9 0 0 0 0 SW 0 0.0 0.0 0:03 kupdated
8 root 9 0 0 0 0 SW 0 0.0 0.0 0:00 khubd
56 root 9 0 0 0 0 SW 0 0.0 0.0 0:01 kjournald
Howerver it become quite quiet now. I don't know who has made it
calm down :-)
1:19am up 1 day, 7:36, 14 users, load average: 0.38, 0.32, 0.92
84 processes: 83 sleeping, 1 running, 0 zombie, 0 stopped
CPU states: 0.0% user, 2.1% system, 1.7% nice, 96.0% idle
Mem: 385280K av, 380824K used, 4456K free, 0K shrd, 9444K buff
Swap: 128484K av, 904K used, 127580K free 188712K cached
PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
8337 pzw 16 5 1268 1268 1068 S N 0 1.3 0.3 0:26 top
9373 pzw 17 5 1268 1268 1068 R N 0 1.3 0.3 0:00 top
9356 pzw 16 5 28864 28M 14064 S N 0 1.1 7.4 1:00 mozilla-bin
1 root 8 0 476 476 412 S 0 0.0 0.1 0:04 init
2 root 9 0 0 0 0 SW 0 0.0 0.0 0:02 keventd
3 root 9 0 0 0 0 SW 0 0.0 0.0 0:00 kapm-idled
4 root 19 19 0 0 0 SWN 0 0.0 0.0 0:00 ksoftirqd_CP
5 root 9 0 0 0 0 SW 0 0.0 0.0 21:58 kswapd
6 root 9 0 0 0 0 SW 0 0.0 0.0 0:00 bdflush
7 root 9 0 0 0 0 SW 0 0.0 0.0 0:03 kupdated
8 root 9 0 0 0 0 SW 0 0.0 0.0 0:00 khubd
56 root 9 0 0 0 0 SW 0 0.0 0.0 0:01 kjournald
58 root 9 0 0 0 0 SW 0 0.0 0.0 0:00 kreiserfsd
104 root 9 0 460 460 404 S 0 0.0 0.1 0:00 apmd
248 root 9 0 552 552 460 S 0 0.0 0.1 0:00 syslogd
258 root 9 0 1052 1052 404 S 0 0.0 0.2 0:00 klogd
Regards
Zhaowang Peng
-----------------------------------------
ÎÒµÄÐÕÃû ÎÒµÄÓÊÏä
http://name.etang.com/
ÒÚÌÆ¶ÌÐÅ£¬ÄúÌùÉíµÄʱÉйËÎÊ
http://sms.etang.com
ÿÌìÈÃÄãÇáËɼǵ¥´Ê
http://www.etang.com/texthanburg/index.htm
ÖйúÈËÐÔ´óÔÖÄÑ
http://topic.etang.com/renxing/index.htm
reply other threads:[~2001-11-03 17:25 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=3BE4285F.17379@mail-smtp2 \
--to=zwpeng@etang.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