From: Richard Cochran <richardcochran@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Dave Airlie <airlied@gmail.com>, Tomas Melin <tomas.melin@iki.fi>,
Chris Wilson <chris@chris-wilson.co.uk>,
stable <stable@vger.kernel.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring
Date: Thu, 11 Apr 2013 19:52:21 +0200 [thread overview]
Message-ID: <20130411175220.GC2482@netboy> (raw)
In-Reply-To: <CAKMK7uGTqSdq_V=Pu-BGNhhTqOn=fz5-LvUXBXpGQJqzL1QOUQ@mail.gmail.com>
On Wed, Apr 10, 2013 at 10:03:25PM +0200, Daniel Vetter wrote:
> That patch should crash at all, so this is not expected. Can you pls
> check whether plain drm-intel-nightly is broken, too?
I did try drm-intel-nightly just now (1dd83e3), and it also freezes
the machine. I first verified that the power button shutdown is
working (before starting X). Then, with X running, closing and
reopening the lid results in a blank screen (no backlight) and a
seemingly frozen box.
> I'll quickly port the patch (in it's latest v3 version) to 3.9-rc
> kernels for you to test.
Okay, I'll try this next.
Thanks,
Richard
next prev parent reply other threads:[~2013-04-11 17:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 11:54 Re: drm/i915: new warning (regression) in 3.7.10 and 3.8.3 Tomas Melin
2013-04-09 12:50 ` Daniel Vetter
2013-04-09 13:21 ` Richard Cochran
2013-04-09 17:28 ` Daniel Vetter
2013-04-09 19:51 ` [PATCH] drm/i915: don't check inconsistent modeset state when force-restoring Daniel Vetter
2013-04-10 11:59 ` Richard Cochran
2013-04-10 12:07 ` Daniel Vetter
2013-04-10 17:27 ` Richard Cochran
2013-04-10 18:32 ` Tomas Melin
2013-04-11 5:16 ` Tomas Melin
2013-04-10 20:03 ` [Intel-gfx] " Daniel Vetter
2013-04-10 20:10 ` Daniel Vetter
2013-04-11 17:52 ` Richard Cochran [this message]
2013-04-11 18:14 ` [Intel-gfx] " Daniel Vetter
2013-04-11 18:37 ` Richard Cochran
2013-04-12 6:59 ` Richard Cochran
2013-04-11 18:22 ` Daniel Vetter
2013-04-11 19:17 ` Chris Wilson
2013-04-11 19:28 ` Daniel Vetter
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=20130411175220.GC2482@netboy \
--to=richardcochran@gmail.com \
--cc=airlied@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tomas.melin@iki.fi \
/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