All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Anant Nitya <kernel@prachanda.info>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [BUG] local_softirq_pending storm
Date: Sun, 20 May 2007 12:18:00 +0200	[thread overview]
Message-ID: <20070520101800.GC9892@osiris.ibm.com> (raw)
In-Reply-To: <1179601868.12981.127.camel@chaos>

On Sat, May 19, 2007 at 09:11:08PM +0200, Thomas Gleixner wrote:
> On Sat, 2007-05-19 at 15:25 +0530, Anant Nitya wrote:
> > > No idea. I uploaded a debug patch against 2.6.22-rc1 to
> > >
> > > http://www.tglx.de/private/tglx/2.6.22-rc1-hrt-debug.patch
> > >
> > > Can you give it a try and report the output ?
> > Hi
> > Here it goes 
> > [  159.646196] NOHZ softirq pending 22 on CPU 0
> > [  159.646207] .... task state: 1 00000000
> 
> 1 == TASK_INTERRUPTIBLE, so we know that ksoftirqd was not woken up. At
> least it is not a scheduler problem.
> 
> I work out a more complex debug patch and pester you to test once I'm
> done.

I've also tons of 'NOHZ: local_softirq_pending 08' that disappear with
nohz=off. But I'm still running 2.6.21. Are there any patches that should
fix this?
Machine is a Lenovo T60p:

i686 Intel(R) Core(TM)2 CPU T7600  @ 2.33GHz GenuineIntel GNU/Linux

Besides that I get a lot of clock skews on 'make headers_check', but
these are unrelated to nohz:

  CHECK   include/asm/dasd.h
make[2]: warning:  Clock skew detected.  Your build may be incomplete.
make[2]: Warning: File `/dev/null' has modification time 5.1e+03 s in the future

  parent reply	other threads:[~2007-05-20 10:18 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
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 [this message]
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=20070520101800.GC9892@osiris.ibm.com \
    --to=heiko.carstens@de.ibm.com \
    --cc=kernel@prachanda.info \
    --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.