From: Thomas Gleixner <tglx@linutronix.de>
To: Vernon Mauery <vernux@us.ibm.com>
Cc: kernel list <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [BUG 2.6.16-rt18] BUG at kernel/rtmutex.c:639!
Date: Fri, 28 Apr 2006 22:53:09 +0200 [thread overview]
Message-ID: <1146257590.1322.637.camel@localhost.localdomain> (raw)
In-Reply-To: <200604280713.45219.vernux@us.ibm.com>
On Fri, 2006-04-28 at 07:13 -0700, Vernon Mauery wrote:
> Ingo,
>
> On an IBM Intellistation A-Pro I am seeing the bug regularly as seen below.
> We also see this bug on an LS-20 blade. The way this bug is triggered is
> to add 'irqpoll' to the kernel command line. If we remove this from the
> command line, we don't see this bug. I know the easy answer is that if you
> don't want to see the bug, don't use irqpoll. So we don't. But we thought
> that just in case this bug does expose something real that it should be
> reported.
That's a lock recursion caused by the irqpoll option. Needs some
thoughts to fix it. Thanks for reporting though.
tglx
prev parent reply other threads:[~2006-04-28 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 14:13 Vernon Mauery
2006-04-28 20:53 ` Thomas Gleixner [this message]
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=1146257590.1322.637.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vernux@us.ibm.com \
/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
Powered by JetHome