LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Gustavo Bittencourt <gbitten@gmail.com>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.18.7-rt2
Date: Tue, 24 Feb 2015 17:00:31 -0300 [thread overview]
Message-ID: <CAA8Xd+-+zGz8R2H2t1Smp0erN7NtwDLbxAWshRz_FjU2T8CnEA@mail.gmail.com> (raw)
In-Reply-To: <1424800214.6955.30.camel@gmail.com>
On Tue, Feb 24, 2015 at 2:50 PM, Mike Galbraith
<umgwanakikbuti@gmail.com> wrote:
> On Tue, 2015-02-24 at 13:19 -0300, Gustavo Bittencourt wrote:
>>
>> The deadlock returned after I applied this patch in v3.18.7-rt2. Here is my log:
>
>
> Hrmph. I definitely want your patch to die ;-) It adds a whole new
> dimension to ww_mutex that only now exists in -rt. That's not good.
No problem.
> My
> patchlet may not be perfect either, but it lets ww_mutex do that return
> EALREADY business it's supposed to, vs going straight to while(1). We
> can't have it both ways, so I suppose I'll fire up my old Q6600 box
> (that doesn't have annoying GTX980 that my userspace can't deal with DRM
> wise), and see if I can chase the nouveau thing down. I'm not all that
> enthusiastic though, as there are or at least were other issues with
> nouveau. Sebastian reported some completely _missing_ locking IIRC,
> that led to his box exploding.
Is there anyway that I could help? I think I can write a code to
reproduce the deadlock without the nouveau driver.
next prev parent reply other threads:[~2015-02-24 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 9:06 Sebastian Andrzej Siewior
2015-02-24 13:41 ` Mike Galbraith
2015-02-24 14:13 ` Mike Galbraith
2015-02-24 16:19 ` Gustavo Bittencourt
2015-02-24 17:50 ` Mike Galbraith
2015-02-24 20:00 ` Gustavo Bittencourt [this message]
2015-02-25 2:27 ` Mike Galbraith
2015-02-26 8:02 ` Mike Galbraith
2015-02-26 10:53 ` Sebastian Andrzej Siewior
2015-02-26 11:30 ` Mike Galbraith
2015-02-26 16:40 ` Gustavo Bittencourt
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=CAA8Xd+-+zGz8R2H2t1Smp0erN7NtwDLbxAWshRz_FjU2T8CnEA@mail.gmail.com \
--to=gbitten@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.com \
--subject='Re: [ANNOUNCE] 3.18.7-rt2' \
/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
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).