From: Andrew Morton <akpm@linux-foundation.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
jkarlson@cc.hut.fi
Subject: Re: [Bugme-new] [Bug 8100] New: dynticks makes ksoftirqd1 use unreasonable amount of cpu time
Date: Wed, 28 Feb 2007 14:00:23 -0800 [thread overview]
Message-ID: <20070228140023.46bbba98.akpm@linux-foundation.org> (raw)
In-Reply-To: <200702281734.l1SHYAp0021968@fire-2.osdl.org>
On Wed, 28 Feb 2007 09:34:10 -0800
bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8100
>
> Summary: dynticks makes ksoftirqd1 use unreasonable amount of cpu
> time
> Kernel Version: 2.6.21-rc2
> Status: NEW
> Severity: low
> Owner: johnstul@us.ibm.com
> Submitter: jkarlson@cc.hut.fi
>
>
> Most recent kernel where this bug did *NOT* occur:
> any kernel without dynticks
>
> Distribution:
> Debian etch with linux-2.6.21-rc{2,1}
>
> Hardware Environment:
> Macbook core2 with bios emulation
>
> Software Environment:
> The problem is obvious when listening to shoutcast stream with kmplayer and
> artsd via wi-fi with wpa (wpa_supplicant)
>
> Problem Description:
> ksoftirqd1 uses ~30% cpu-time (by top) no other symptoms, while
> without dyntikcs cpu-load in similar circumstances is negligible.
> This might be a dynticks feature rather than bug.
>
> Steps to reproduce:
> Just watch the top, if the bug is reproducible, probably just booting should
> suffice.
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
next parent reply other threads:[~2007-02-28 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200702281734.l1SHYAp0021968@fire-2.osdl.org>
2007-02-28 22:00 ` Andrew Morton [this message]
2007-03-09 21:23 ` [Bugme-new] [Bug 8100] New: dynticks makes ksoftirqd1 use unreasonable amount of cpu time Pavel Machek
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=20070228140023.46bbba98.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jkarlson@cc.hut.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.