From: Robert Hancock <hancockr@shaw.ca>
To: Dushan Tcholich <dusanc@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: ksoftirqd high cpu load on kernels 2.6.24 to 2.6.27-rc1-mm1
Date: Mon, 04 Aug 2008 13:43:15 -0600 [thread overview]
Message-ID: <48975BD3.6040709@shaw.ca> (raw)
In-Reply-To: <fa.wTMiBcGRgw2fBtdHwtX7y0lkc8s@ifi.uio.no>
Dushan Tcholich wrote:
> Hello
>
> This is my first bugreport on LKML so please be patient :)
>
> top always shows me that ksoftirqd usualy gets around 8%CPU, it
> changes between 6 and 10%.
> It's sometimes ksoftirqd/0 sometimes /1, differs on the reboot but
> doesn't change during work.
> I noticed it because it had very high time+, 500hours or so.
> I reproduced these problems with kernels 2.6.24 .25 and .27-rc1-mm1. I
> don't remember that this happened during .22 and .23 kernels, but I
> can check again if it's necessary.
> Timer freq is 1000Hz
>
> What I tried without changes with help from ##kernel:
> 1. built kernel without kvm;
> 2. disconnected all usb hw except mouse;
> 3. run glxgears which consumed 98% CPU and ksoftirqd 2%;
> 4. Tried to stress disk subsystem by copying a lot of small files on
> the same partition:
> time cp -R /usr/portage/* /tmp/1
> real 2m17.530s
> user 0m0.764s
> sys 0m18.596s
>
> it was 127507 items 1.5GB, but just pdflush jumped to 14% from time to time;
> 5. disabled serial port in BIOS because my UPS was connected to it,
> and I suspected that it was maybe polling too much;
> 6. disconnected eth cable
> 7. tried googling but all I found is that some people had similar
> problem. Some TV cards were the culprit but I don't have that HW.
>
> If you need any more data please cc me as I'm not subscribed
It would be useful to try running oprofile on an otherwise idle system
and see where it reports the CPU time is being used..
next parent reply other threads:[~2008-08-04 19:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.wTMiBcGRgw2fBtdHwtX7y0lkc8s@ifi.uio.no>
2008-08-04 19:43 ` Robert Hancock [this message]
2008-08-04 20:37 ` ksoftirqd high cpu load on kernels 2.6.24 to 2.6.27-rc1-mm1 Dushan Tcholich
[not found] ` <20080807185802.GA16327@electric-eye.fr.zoreil.com>
[not found] ` <a08621850808101200n220afd2dve58abe67830b7a4f@mail.gmail.com>
[not found] ` <a08621850808110053j5cbf23e6xdf52c9e7440abf19@mail.gmail.com>
2008-08-30 1:48 ` Dushan Tcholich
2008-08-31 8:51 ` Dushan Tcholich
2008-08-31 17:05 ` Stephen Hemminger
2008-08-31 17:43 ` [RFC] bridge: STP timer management range checking Stephen Hemminger
2008-08-31 22:02 ` Alan Cox
2008-08-31 23:29 ` Stephen Hemminger
2008-09-01 8:38 ` Alan Cox
2008-09-02 16:40 ` Rick Jones
2008-09-02 23:41 ` David Miller
2008-09-03 0:00 ` Rick Jones
2008-09-01 2:25 ` Valdis.Kletnieks
2008-09-03 0:28 ` David Miller
2008-09-04 22:47 ` [PATCH] bridge: don't allow setting hello time to zero Stephen Hemminger
2008-09-08 20:46 ` David Miller
2008-09-08 21:35 ` Dushan Tcholich
2008-09-08 22:33 ` Stephen Hemminger
2008-08-31 19:14 ` ksoftirqd high cpu load on kernels 2.6.24 to 2.6.27-rc1-mm1 Dushan Tcholich
2008-08-04 14:17 Dushan Tcholich
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=48975BD3.6040709@shaw.ca \
--to=hancockr@shaw.ca \
--cc=dusanc@gmail.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