From: Thomas Gleixner <tglx@linutronix.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Lukas Erlinghagen <lukas.erlinghagen@x2e.de>,
linux-rt-users@vger.kernel.org
Subject: Re: Kernel panic with PREEMPT_RT_FULL and UIO driver
Date: Thu, 22 Dec 2011 13:58:21 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1112221246350.3020@ionos> (raw)
In-Reply-To: <20111222103114.GE24496@pengutronix.de>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 497 bytes --]
On Thu, 22 Dec 2011, Uwe Kleine-König wrote:
> On Wed, Dec 21, 2011 at 11:48:36AM +0100, Lukas Erlinghagen wrote:
> > ------------[ cut here ]------------
> > kernel BUG at kernel/rtmutex.c:724!
> That's a recursive spinlock. Try enabling CONFIG_PROVE_LOCKING.
News at eleven. I already explained Lukas, _why_ this happens. So what
the heck will CONFIG_PROVE_LOCKING provide as extra value?
We all appreciate your helpfulness, but your signal to noise ratio is
approaching zero.
Thanks,
tglx
prev parent reply other threads:[~2011-12-22 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 10:48 Kernel panic with PREEMPT_RT_FULL and UIO driver Lukas Erlinghagen
2011-12-21 11:38 ` Thomas Gleixner
2011-12-22 10:31 ` Uwe Kleine-König
2011-12-22 12:58 ` 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=alpine.LFD.2.02.1112221246350.3020@ionos \
--to=tglx@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=lukas.erlinghagen@x2e.de \
--cc=u.kleine-koenig@pengutronix.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