[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAA8Xd+-hCKnuy96PMoo2T5xwDPNh+79sme8bakK_ossMbfMs7Q@mail.gmail.com>
Date: Thu, 26 Feb 2015 13:40:27 -0300
From: Gustavo Bittencourt <gbitten@...il.com>
To: Mike Galbraith <umgwanakikbuti@...il.com>
Cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
linux-rt-users <linux-rt-users@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Steven Rostedt <rostedt@...dmis.org>,
John Kacur <jkacur@...hat.com>
Subject: Re: [ANNOUNCE] 3.18.7-rt2
On Thu, Feb 26, 2015 at 5:02 AM, Mike Galbraith
<umgwanakikbuti@...il.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.
>
> Grr, because dummy here munged a reject when he backported to 3.18-rt.
> Please try the below, my trusty old Q6600 box is now running with
> nouveau/drm in both 3.18-rt and 4.0-rt.
>
> I found what was breaking my core2 lappy in 4.0-rt as well, namely the
> rtmutex.c set_current_state() munging that went into mainline recently,
> and that also broke my Q6600 box with nouveau/drm as well! Seems you
> need a slow box and drm to experience the breakage nice and repeatably,
> which is kinda worrisome. Anyway, all of my boxen can use drm just fine
> in both rt trees now, so your box _should_ be happy too.
>
Mike, my box is running very well now. Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists