Message-ID: <4050AEC2.8070000@brad-x.com>
Date: Thu, 11 Mar 2004 13:24:02 -0500
From: Brad Laue <brad@brad-x.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040222
MIME-Version: 1.0
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ksoftirqd using mysteriously high amounts of CPU time
References: <404F85A6.6070505@brad-x.com>	<20040310155712.7472e31c.akpm@osdl.org>	<4050271C.3070103@brad-x.com>	<40503120.9000008@brad-x.com> <20040311020832.1aa25177.akpm@osdl.org>
In-Reply-To: <20040311020832.1aa25177.akpm@osdl.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1225
Lines: 37

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/