From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754250AbbBZQka (ORCPT ); Thu, 26 Feb 2015 11:40:30 -0500 Received: from mail-oi0-f46.google.com ([209.85.218.46]:55938 "EHLO mail-oi0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752748AbbBZQk2 (ORCPT ); Thu, 26 Feb 2015 11:40:28 -0500 MIME-Version: 1.0 In-Reply-To: <1424937725.3622.31.camel@gmail.com> References: <20150223090617.GA26453@linutronix.de> <1424785301.8767.11.camel@gmail.com> <1424937725.3622.31.camel@gmail.com> Date: Thu, 26 Feb 2015 13:40:27 -0300 Message-ID: Subject: Re: [ANNOUNCE] 3.18.7-rt2 From: Gustavo Bittencourt To: Mike Galbraith Cc: Sebastian Andrzej Siewior , linux-rt-users , LKML , Thomas Gleixner , Steven Rostedt , John Kacur Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 26, 2015 at 5:02 AM, Mike Galbraith 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.