From: Steven Rostedt <rostedt@goodmis.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Koehrer Mathias (ETAS/ESS2)" <mathias.koehrer@etas.com>,
Jan Kiszka <jan.kiszka@web.de>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: AW: VirtualBox 4.2.4 freezes PC using RT_PREEMPT kernel
Date: Fri, 21 Dec 2012 10:13:01 -0500 [thread overview]
Message-ID: <1356102781.5896.107.camel@gandalf.local.home> (raw)
In-Reply-To: <alpine.LFD.2.02.1212211604060.3148@ionos>
On Fri, 2012-12-21 at 16:05 +0100, Thomas Gleixner wrote:
> On Fri, 21 Dec 2012, Steven Rostedt wrote:
> > On Fri, 2012-12-21 at 08:23 +0000, Koehrer Mathias (ETAS/ESS2) wrote:
> > > *** DEADLOCK ***
> >
> > So this is an obvious bug in virtualbox. No need to send us a config.
> > This bug has nothing to do with RT. It's just that RT can expose bugs in
> > mainline (or anything added to mainline) much easier.
> >
> > Funny thing is, this deadlock isn't even possible in RT, so there's
> > probably many more bugs in the virtualbox driver.
>
> It's worse on RT, because that's a smp function call interrupt. Which
> just cannot work on RT with the lock not being a raw lock.
>
Ah, I just figured it was an normal interrupt thread. I was avoiding eye
cancer by not looking at the code. I guess I could have figured it out
with looking at the rest of the lockdep dump, but was too lazy ;-)
-- Steve
prev parent reply other threads:[~2012-12-21 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 14:44 VirtualBox 4.2.4 freezes PC using RT_PREEMPT kernel Koehrer Mathias (ETAS/ESS2)
2012-12-20 18:20 ` Thomas Gleixner
2012-12-21 8:23 ` AW: " Koehrer Mathias (ETAS/ESS2)
2012-12-21 14:55 ` Steven Rostedt
2012-12-21 15:05 ` Thomas Gleixner
2012-12-21 15:13 ` Steven Rostedt [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=1356102781.5896.107.camel@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=jan.kiszka@web.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=mathias.koehrer@etas.com \
--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).