linux-kernel - Re: i915 black screen introduced by ACPI changes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 4 Mar 2013 09:11:31 -0800
From:	Chris Li <lkml@...isli.org>
To:	Daniel Vetter <daniel.vetter@...ll.ch>
Cc:	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-kernel@...r.kernel.org, robert.moore@...el.com,
	feng.tang@...el.com, len.brown@...el.com,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: i915 black screen introduced by ACPI changes

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 <lkml@...isli.org> wrote:
> Ping. Any update for this black screen problem?
>
> Chris
>
> On Wed, Feb 20, 2013 at 1:04 PM, Chris Li <lkml@...isli.org> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/