From: Brad Laue <brad@brad-x.com>
To: linux-kernel@vger.kernel.org
Subject: ksoftirqd using mysteriously high amounts of CPU time
Date: Wed, 10 Mar 2004 16:16:22 -0500 [thread overview]
Message-ID: <404F85A6.6070505@brad-x.com> (raw)
Greetings, all
I'm running into an issue where ksoftirqd/0 consumes a considerably
larger amount of CPU time than it should, and begins to actively
consume 99% CPU time during network operations.
I've done my best to diagnose this, but it has followed me from kernel
2.4.20 to 2.6.3 and all versions in between, on three different server
systems with distinct hardware configurations.
The latest system to be affected by this takes considerably longer to
have trouble, but this is only due to its sheer muscle to begin with (2x
MP 2800+), but does indeed appear. After 55 days of uptime:
5 root 34 19 0 0 0 S 0.0 0.0 0:21.40 ksoftirqd_CPU0
6 root 34 19 0 0 0 S 0.0 0.0 0:36.31 ksoftirqd_CPU1
Compare this to another machine which I don't run myself:
3 root 19 19 0 0 0 S 0.0 0.0 0:09.86 ksoftirqd_CPU0
There are peculiarities to my configuration which are shared on all the
affected machines - the use of PPPoE to connect is one example. However
on one of the affected systems a second network interface was subjected
to heavy NFS traffic over simple ethernet and exhibited the same
behavior. Another shared trait is a firewall ruleset I've written for
the machines, which I can attach if someone would like to see them.
The three configurations include:
K6-2 500MHz
Ne2K, RealTek 8139
Duron 900MHz
SiS 900, RealTek 8139
2x Athlon MP 2800+
3com 3c905b 10/100+
The issue begins with ksoftirqd consuming more time than usual, and ends
after four to twelve weeks depending on how powerful the machine, with
the machine crippled and unable to sustain network traffic of any kind.
Any assistance on where to look for solutions to this kind of problem
would be GREATLY appreciated.
Thanks in advance!
Brad
next reply other threads:[~2004-03-10 21:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 21:16 Brad Laue [this message]
2004-03-10 23:57 ` ksoftirqd using mysteriously high amounts of CPU time Andrew Morton
2004-03-11 8:45 ` Brad Laue
2004-03-11 9:28 ` Brad Laue
2004-03-11 10:08 ` Andrew Morton
2004-03-11 14:05 ` Yury V. Umanets
2004-03-11 17:22 ` Brad Laue
2004-03-11 18:09 ` Yury V. Umanets
2004-03-11 18:21 ` Brad Laue
2004-03-11 18:24 ` Brad Laue
2004-03-12 17:51 ` Brad Laue
2004-03-11 14:00 ` Yury V. Umanets
[not found] <Pine.LNX.4.21.0403111916570.3466-100000@linux08.ece.utexas.edu>
2004-03-12 7:06 ` Brad Laue
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=404F85A6.6070505@brad-x.com \
--to=brad@brad-x.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