From: Thomas Richter <thor@math.tu-berlin.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: intel-drm-nightly 3.13rc3 broke i830 - more debug
Date: Thu, 19 Dec 2013 19:33:18 +0100 [thread overview]
Message-ID: <52B33BEE.7010003@math.tu-berlin.de> (raw)
In-Reply-To: <17899_1387468024_52B314F8_17899_17059_1_20131219154757.GR26371@phenom.ffwll.local>
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
prev parent reply other threads:[~2013-12-19 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 15:07 intel-drm-nightly 3.13rc3 broke i830 - more debug Thomas Richter
2013-12-19 15:46 ` Daniel Vetter
2013-12-19 15:47 ` Daniel Vetter
[not found] ` <17899_1387468024_52B314F8_17899_17059_1_20131219154757.GR26371@phenom.ffwll.local>
2013-12-19 18:33 ` Thomas Richter [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=52B33BEE.7010003@math.tu-berlin.de \
--to=thor@math.tu-berlin.de \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/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