From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Timothy B. Terriberry" <tterribe@xiph.org>
Subject: Re: how get drm-intel-next into a stable kernel
Date: Thu, 05 Aug 2010 12:47:54 -0700
Message-ID: <4C5B156A.4030300@xiph.org>
References: <1281022735.29410.6.camel@segulix>	<20100805105409.35575e31@virtuousgeek.org>	<20100805175836.GA12571@kroah.com>
	<4C5B0741.5060904@xiph.org> <4C5B0AE9.70803@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Content-Transfer-Encoding: quoted-printable
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from mxip1i.isis.unc.edu (mxip1i.isis.unc.edu [152.2.0.74])
	by gabe.freedesktop.org (Postfix) with ESMTP id 7129F9E73D
	for <intel-gfx@lists.freedesktop.org>;
	Thu,  5 Aug 2010 12:57:35 -0700 (PDT)
Received: from [10.250.3.250] (corp-240.mv.mozilla.com [63.245.220.240])
	(authenticated bits=0)
	by smtp.unc.edu (8.14.3/8.14.3) with ESMTP id o75JltPJ028510
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <intel-gfx@lists.freedesktop.org>;
	Thu, 5 Aug 2010 15:47:56 -0400 (EDT)
In-Reply-To: <4C5B0AE9.70803@gmail.com>
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
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
List-Id: intel-gfx@lists.freedesktop.org

Brice Goglin wrote:
> Le 05/08/2010 20:47, Timothy B. Terriberry a =E9crit :
>> This no longer works on 2.6.35 (black screen after starting X).
> =

> Could be https://bugzilla.kernel.org/show_bug.cgi?id=3D16496 ?

Reverting that patch (or, more accurately, just deleting the redundant =

backlight_off call) does indeed solve the problem when initially =

starting X. So now it's just the suspend issue. Same behavior as 2.6.34: =

when resuming, the display is off, and switching VTs, etc., won't turn =

it on. What does work, if I type very carefully, is hibernating and then =

resuming.