From mboxrd@z Thu Jan  1 00:00:00 1970
From: Cedric Sodhi <manday@gmx.net>
Subject: Re: Regression: Screen goes black on KMS
Date: Sat, 5 Nov 2011 10:07:27 +0100
Message-ID: <20111105090714.GA2160@slate>
References: <20111104222807.GB2175@slate>
 <yunzkgb89eh.fsf@aiko.keithp.com>
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 mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23])
	by gabe.freedesktop.org (Postfix) with SMTP id 94C2B9E812
	for <intel-gfx@lists.freedesktop.org>;
	Sat,  5 Nov 2011 02:07:40 -0700 (PDT)
Content-Disposition: inline
In-Reply-To: <yunzkgb89eh.fsf@aiko.keithp.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
To: Keith Packard <keithp@keithp.com>
Cc: intel-gfx@lists.freedesktop.org
List-Id: intel-gfx@lists.freedesktop.org

On Fri, Nov 04, 2011 at 09:45:26PM -0700, Keith Packard wrote:
> On Fri, 4 Nov 2011 23:28:07 +0100, Cedric Sodhi <manday@gmx.net> wrote:
> Non-text part: multipart/mixed
> > Hello,
> > 
> > between 3.1 and cc03bbf1 on linux-next there has been a regression which
> > causes the screen to go black (not blank, backlight is still lit) on
> > KMS. The system runs fine in the background and, to all it seems, X even
> > starts, but the screen is black and useless.
> 
> Please create a bugzilla entry on bugs.freedesktop.org that includes a
> dmesg capture in working/not-working modes with drm.debug=6, and a dump
> From intel_reg_dumper in both working and not-working modes. That'll
> show how the device is mis-programmed, and with luck, show us where it
> went wrong.

https://bugs.freedesktop.org/show_bug.cgi?id=42616

Thank you.