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: Fri, 18 May 2007 15:01:17 +0200 [thread overview]
Message-ID: <1179493277.12981.69.camel@chaos> (raw)
In-Reply-To: <200705171211.23350.kernel@prachanda.hub>
On Thu, 2007-05-17 at 12:11 +0530, Anant Nitya wrote:
> On Friday 11 May 2007 03:28:46 Thomas Gleixner wrote:
>
> > 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.
> Yes with HT disabled in BIOS there is no local_softirq_pending messages. BTW
> why does this problem persist only with X ?
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 ?
> > When you apply the ratelimit patch, does the softlockup problem
> > persist ?
> >
> Yes, though softlockup is rare and mostly hit when system is under high load.
> Apart of that I am also getting following messages consistently across
> multiple boot cycles with NOHZ=y and ratelimit patch applied.
>
> May 15 11:51:22 rudra kernel: [ 2594.341068] Clocksource tsc unstable (delta =
> 28111260302 ns)
> May 15 11:51:22 rudra kernel: [ 2594.343194] Time: acpi_pm clocksource has
> been installed.
That's informal. The TSC is detected to be unstable and replaced by the
pm timer. Nothing to worry about. It happens with NOHZ=n as well,
right ?
tglx
next prev parent reply other threads:[~2007-05-18 12:56 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 [this message]
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=1179493277.12981.69.camel@chaos \
--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