From: Brad Laue <brad@brad-x.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ksoftirqd using mysteriously high amounts of CPU time
Date: Thu, 11 Mar 2004 13:24:02 -0500 [thread overview]
Message-ID: <4050AEC2.8070000@brad-x.com> (raw)
In-Reply-To: <20040311020832.1aa25177.akpm@osdl.org>
Andrew Morton wrote:
> Brad Laue <brad@brad-x.com> wrote:
>
>> Brad Laue wrote:
>> > Hopefully the attached shows some irregularity. If not, I'll have to
>> > reply back in a few weeks when the problem recurs over the course of time.
>>
>> And without further ado, the attachment. It's been a long day. :)
>
>
> It beats me. Something must be waking up ksoftirqd all the time.
>
> If you have time, could you please apply the below, then wait for ksoftirqd
> to go bad again and then run:
>
>
> dmesg -c
> echo 1 > /proc/sys/debug/0 ; sleep 1; echo 0 > /proc/sys/debug/0
> dmesg -s 1000000 > /tmp/foo
>
> and then send foo?
Will do. I think the profile output I generated was a bit premature.
I'll wait a few days until the problem resurfaces in earnest and attach
some more output then.
For now, it looks like the 'pppoe' process itself is waking up ksoftirqd
the most according to the output of dmesg, but that may change with time.
Will keep you posted.
Brad
next prev parent reply other threads:[~2004-03-11 18:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 21:16 ksoftirqd using mysteriously high amounts of CPU time Brad Laue
2004-03-10 23:57 ` 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 [this message]
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=4050AEC2.8070000@brad-x.com \
--to=brad@brad-x.com \
--cc=akpm@osdl.org \
--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