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

[Zhang Rui]

On Mon, 2014-06-23 at 14:22 +0200, Martin Kepplinger wrote:
> Am 2014-06-23 03:10, schrieb Zhang, Rui:
> > 
> > 
> >> -----Original Message-----
> >> From: Martin Kepplinger [mailto:martink@xxxxxxxxx]
> >> Sent: Sunday, June 22, 2014 10:25 PM
> >> To: Zhang, Rui
> >> Cc: rjw@xxxxxxxxxxxxx; lenb@xxxxxxxxxx; linux-acpi@xxxxxxxxxxxxxxx;
> >> linux-kernel@xxxxxxxxxxxxxxx
> >> 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.
> >>
This looks like a duplicate of
https://bugzilla.kernel.org/show_bug.cgi?id=78601

thanks,
rui
> >> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/