Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932120Ab3CDRLf (ORCPT ); Mon, 4 Mar 2013 12:11:35 -0500 Received: from mail-oa0-f45.google.com ([209.85.219.45]:62033 "EHLO mail-oa0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758453Ab3CDRLc (ORCPT ); Mon, 4 Mar 2013 12:11:32 -0500 MIME-Version: 1.0 In-Reply-To: References: <20130219100849.72d2330b@jbarnes-desktop> <20130219125217.6b6f55ff@jbarnes-desktop> Date: Mon, 4 Mar 2013 09:11:31 -0800 X-Google-Sender-Auth: H2a43bVCpSsF5RM2G9Pyqj37poY Message-ID: Subject: Re: i915 black screen introduced by ACPI changes From: Chris Li To: Daniel Vetter Cc: Jesse Barnes , linux-kernel@vger.kernel.org, robert.moore@intel.com, feng.tang@intel.com, len.brown@intel.com, Linus Torvalds Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1092 Lines: 35 Ping, To recap, the black screen first show up after the ACPI change to use widows 8 string. The i915_setmode function did not crash. The printk output from that function seems the same as the one that is in 3.6 kernel. I also include the 3.6 and 3.7 kernel dmesg. The black screen is 100% reproducible. Any suggestion how to further debug this i9515 black screen problem? I really want to get it fixed. Thanks Chris On Fri, Feb 22, 2013 at 2:42 PM, Chris Li wrote: > Ping. Any update for this black screen problem? > > Chris > > On Wed, Feb 20, 2013 at 1:04 PM, Chris Li wrote: >> Here is the dmesg with "drm.debug=0xe" at >> 80187431762989ebade986468d3c548287a12689 >> >> That is the 3.6 kernel, exactly one commit before the ACPI commit >> which triggering the black screen. >> >> Thanks >> >> Chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/