From: Anant Nitya <kernel@prachanda.info>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Subject: Re: [BUG] local_softirq_pending storm
Date: Mon, 21 May 2007 11:52:07 +0530 [thread overview]
Message-ID: <200705211152.08518.kernel@prachanda.hub> (raw)
In-Reply-To: <1179697388.6570.26.camel@chaos>
On Monday 21 May 2007 03:13:08 Thomas Gleixner wrote:
> On Sun, 2007-05-20 at 02:53 +0530, Anant Nitya wrote:
> > > 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.
> >
> > No problem :)
>
> You asked for it :)
>
> Please patch 2.6.22-rc2 with
>
> http://tglx.de/projects/hrtimers/2.6.22-rc2/patch-2.6.22-rc2-hrt2.patch
> and
> http://www.tglx.de/private/tglx/ht-debug/tracer.diff
>
> Compile it with the config
>
> http://www.tglx.de/private/tglx/ht-debug/config.debug
>
> You should find something like:
>
> ( swapper-0 |#0): new 67173 us user-latency.
>
> along with the familiar "NOHZ ......" message in your log file.
>
> Once that happened please do:
>
> $ cat /proc/latency_trace >trace.txt
>
> compress it and send it to me along with the full dmesg output or put
> both up to some place, where I can download it.
Hi Thomas
Here are the links...
http://cybertek.info/taitai/dmesg-2.6.22.rc2.hrt2-1.SMP.DN.LINUX.txt
http://cybertek.info/taitai/trace.txt.bz2
Regards
Ananitya
>
> Michal,
>
> IIRC you encountered the same P4/HT related wreckage. Can you do the
> same ?
>
> Thanks,
>
> tglx
--
Out of many thousands, one may endeavor for perfection, and of
those who have achieved perfection, hardly one knows Me in truth.
-- Gita Sutra Of Mysticism
next prev parent reply other threads:[~2007-05-21 6:25 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 [this message]
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=200705211152.08518.kernel@prachanda.hub \
--to=kernel@prachanda.info \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).