From: Thomas Gleixner <tglx@linutronix.de>
To: Anant Nitya <kernel@prachanda.info>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] local_softirq_pending storm
Date: Thu, 10 May 2007 23:58:46 +0200 [thread overview]
Message-ID: <1178834326.22481.18.camel@localhost.localdomain> (raw)
In-Reply-To: <d95aa510705100453y666cf310ic9ee4dc609f099f1@mail.gmail.com>
On Thu, 2007-05-10 at 17:23 +0530, Anant Nitya wrote:
> On 5/9/07, Thomas Gleixner <tglx@linutronix.de> wrote:
> > On Wed, 2007-05-09 at 19:42 +0530, Anant Nitya wrote:
> > > Hi,
> > > Ever since I upgrade to 2.6.21/.1, system log is filled with following
> > > messages if I enable CONFIG_NO_HZ=y, going through archives it seems ingo
> > > sometime back posted some patch and now it is upstream, but its not helping
> > > here. If I disable NOHZ by kernel command line nohz=off this problem
> > > disappears. This system is P4/2.40GHz/HT with SMP/SMT on in kernel config.
> > > One more thing that I noticed is this problem only arises while using X or
> > > network otherwise plain command line with no network access don't trigger
> > > this with nohz=on.
> >
> > Is this independent of the load on the system ? i.e. : What happens if
> > you only use the console and run a kernel compile with -j4 ?
> Yep, it seems independent of load on the system, to test I compiled
> kernel with make -j8 and to throw some more load same time I also used
> amavisd to clean around 2000 of spam/virus infected mails and same
> time was listening to few radio stream over net in console only login
> mode. Even then there was not a single NOHZ: local_softirq_pending
> message in log. Once kernel got compiled and amavisd finished its job
> and load drops back to around 0.5/2.0 I started X and within few secs
> log starts getting filled with local_softirq_pending messages, (sorry,
> I didn't applied ratelimit patch since I wanted to test is it high
> load on system that causes this or something else). It seems even
> network operation is not causing this. It seems either X is doing
> something terribly wrong or kernel is getting hosed by X.
> If some more information is needed please feel free to ask
Ok, that's consistent with earlier reports. The problem surfaces when
one of the SMT-"cpus" goes idle. The problem goes away when you disable
hyperthreading.
When you apply the ratelimit patch, does the softlockup problem
persist ?
tglx
next prev parent reply other threads:[~2007-05-10 21:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 14:12 [BUG] local_softirq_pending storm Anant Nitya
2007-05-09 16:31 ` Thomas Gleixner
2007-05-10 11:53 ` Anant Nitya
2007-05-10 21:58 ` Thomas Gleixner [this message]
2007-05-17 6:41 ` Anant Nitya
2007-05-18 13:01 ` Thomas Gleixner
2007-05-19 4:30 ` Anant Nitya
2007-05-19 9:55 ` Anant Nitya
2007-05-19 19:11 ` Thomas Gleixner
2007-05-19 21:23 ` Anant Nitya
2007-05-20 21:43 ` Thomas Gleixner
2007-05-21 6:22 ` Anant Nitya
2007-05-21 9:01 ` Thomas Gleixner
2007-05-21 10:02 ` Anant Nitya
2007-05-21 18:45 ` Anant Nitya
2007-05-22 19:03 ` Michal Piotrowski
2007-05-22 19:59 ` Michal Piotrowski
2007-05-22 20:10 ` Ingo Molnar
2007-05-22 20:23 ` Michal Piotrowski
2007-05-23 17:00 ` Chuck Ebbert
2007-05-23 18:38 ` Chuck Ebbert
2007-05-23 23:24 ` Anant Nitya
2007-05-24 7:45 ` Ingo Molnar
2007-05-20 10:18 ` Heiko Carstens
2007-05-20 13:52 ` Thomas Gleixner
2007-05-20 18:36 ` Heiko Carstens
[not found] ` <20070520191800.GA14225@osiris.ibm.com>
[not found] ` <1179689389.6570.1.camel@chaos>
[not found] ` <20070521200428.GA9855@osiris.ibm.com>
2007-05-23 20:54 ` Mikulas Patocka
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=1178834326.22481.18.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=kernel@prachanda.info \
--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