linux-kernel - Re: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution

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]

Message-ID: <53A81BF7.3030207@posteo.de>
Date:	Mon, 23 Jun 2014 14:22:15 +0200
From:	Martin Kepplinger <martink@...teo.de>
To:	"Zhang, Rui" <rui.zhang@...el.com>
CC:	"rjw@...ysocki.net" <rjw@...ysocki.net>,
	"lenb@...nel.org" <lenb@...nel.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-media@...r.kernel.org
Subject: Re: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead
 of native resolution

Am 2014-06-23 03:10, schrieb Zhang, Rui:
> 
> 
>> -----Original Message-----
>> From: Martin Kepplinger [mailto:martink@...teo.de]
>> Sent: Sunday, June 22, 2014 10:25 PM
>> To: Zhang, Rui
>> Cc: rjw@...ysocki.net; lenb@...nel.org; linux-acpi@...r.kernel.org;
>> linux-kernel@...r.kernel.org
>> Subject: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black
>> instead of native resolution
>> Importance: High
>>
>> Since 3.16-rc1 my laptop's just goes black while booting, instead of
>> switching to native screen resolution and showing me the starting
>> system there. It's an Acer TravelMate B113 with i915 driver and
>> acer_wmi. It stays black and is unusable.
>>
>> Do you have other people complain about that? Bisecting didn't lead to
>> a good result. I could be wrong but I somehow suspect the mistake to be
>> somewhere in commit 99678ed73a50d2df8b5f3c801e29e9b7a3e5aa85
>>
> In order to confirm if the problem is introduced by the above commit,
> why not checkout the kernel just before and after this commit and see if the problem exists?
> 
> Thanks,
> rui
> 
So maybe I was wrong. d27050641e9bc056446deb0814e7ba1aa7911f5a is still
good and aaeb2554337217dfa4eac2fcc90da7be540b9a73 is the fist bad one.
This is a big v4l merge. I added the linux-media list in cc now.

What could be the problem here?

> 
>> There is nothing unusual in the kernel log.
>>
>> This is quite unusual for an -rc2. Hence my question. I'm happy to test
>> changes.
>>
>>                                      martin
>> --
>> Martin Kepplinger
>> e-mail        martink AT posteo DOT at
>> chat (XMPP)   martink AT jabber DOT at

--
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/