From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Richter <thor@math.tu-berlin.de>
Subject: Re: intel-drm-nightly 3.13rc3 broke i830 - more debug
Date: Thu, 19 Dec 2013 19:33:18 +0100
Message-ID: <52B33BEE.7010003@math.tu-berlin.de>
References: <52B30BB7.8070405@math.tu-berlin.de>
	<20131219154617.GQ26371@phenom.ffwll.local>
	<17899_1387468024_52B314F8_17899_17059_1_20131219154757.GR26371@phenom.ffwll.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces@lists.freedesktop.org>
Received: from charon.rus.uni-stuttgart.de (charon.rus.uni-stuttgart.de
	[129.69.192.1])
	by gabe.freedesktop.org (Postfix) with ESMTP id 902DB10E81D
	for <intel-gfx@lists.freedesktop.org>;
	Thu, 19 Dec 2013 10:33:23 -0800 (PST)
In-Reply-To: <17899_1387468024_52B314F8_17899_17059_1_20131219154757.GR26371@phenom.ffwll.local>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Sender: intel-gfx-bounces@lists.freedesktop.org
Errors-To: intel-gfx-bounces@lists.freedesktop.org
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, intel-gfx <intel-gfx@lists.freedesktop.org>
List-Id: intel-gfx@lists.freedesktop.org

Hi Daniel,

>> Quick shot in the dark: Can you please try the below diff?
>>
>> If that doesn't work please remove the locking in that function completely
>> (i.e. remove the calls to drm_modset_lock|unlock_all).
> If that doesn't help please compile a pristine -nightly with lockdep
> (CONFIG_PROVE_LOCKING) rehang the machine and grab the complete dmesg.
> Please make sure that you don't line-wrap it for easier reading. Lockdep
> should be able to tell us who's blocking on what exactly here ...

Ok, tried that. Moving the lock did not improve anything. Removing it, 
well, "sort-of" improved the situation in so far as the system no longer 
hangs. However, I still don't get a working display. All I get is a dark 
screen, and only the cursor on top.

So long,
     Thomas