From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: BISECTED: Suspend regression on drm-intel-next
Date: Sat, 18 Dec 2010 21:42:22 +0000
Message-ID: <849307$aqoaem@azsmga001.ch.intel.com>
References: <1292702541.3071.7.camel@pcjc2lap>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from mga14.intel.com (mga14.intel.com [143.182.124.37])
	by gabe.freedesktop.org (Postfix) with ESMTP id 57A189E79F
	for <intel-gfx@lists.freedesktop.org>;
	Sat, 18 Dec 2010 13:42:25 -0800 (PST)
In-Reply-To: <1292702541.3071.7.camel@pcjc2lap>
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+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
To: Peter Clifton <pcjc2@cam.ac.uk>, Intel <intel-gfx@lists.freedesktop.org>
List-Id: intel-gfx@lists.freedesktop.org

On Sat, 18 Dec 2010 20:02:21 +0000, Peter Clifton <pcjc2@cam.ac.uk> wrote:
> Hi Chris,
> 
> I bisected the suspend regression I mentioned, and came to this commit:
> 
> commit 0cdab21f9a1fca50dd27e488839f5a6578e333b2
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Sun Dec 5 17:27:06 2010 +0000
> 
>     drm/i915: Uncouple render/power ctx before suspending
>     
>     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> 
> 
> Disabling power context tear down on suspend with this diff:

And you verified the revert against drm-intel-next HEAD? I'll revert just
as soon as I see your confirmation. :)

[The patch was only trying to see if it made Ironlake stable on suspending
with renderctx, to no avail so there should be no repercussions in
reverting.]

Thanks,
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre