linux-kernel - Re: [Intel-gfx] Regression in drm-intel caused by d91a2cb8e510

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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.1409012122220.18553-100000@netrider.rowland.org>
Date:	Mon, 1 Sep 2014 21:23:14 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Damien Lespiau <damien.lespiau@...el.com>
cc:	Daniel Vetter <daniel@...ll.ch>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: [Intel-gfx] Regression in drm-intel caused by d91a2cb8e510

On Mon, 1 Sep 2014, Damien Lespiau wrote:

> On Mon, Sep 01, 2014 at 04:19:23PM -0400, Alan Stern wrote:
> > Daniel:
> > 
> > I'm encountering a problem with the drm-intel-nightly branch in your
> > drm-intel repository.  The symptom is that when I boot my laptop, at
> > some point during the start-up procedure the screen goes totally blank,
> > as though the backlight were turned off, and it remains that way.  I
> > can't tell if the backlight really is off -- it may be that there's
> > just nothing being displayed -- and playing with the screen-brightness
> > function keys doesn't help.
> > 
> > Git bisect located the source of the problem as commit d91a2cb8e510
> > (drm/i915: Add 180 degree primary plane rotation support).  The problem
> > occurs when I boot a kernel built from that commit, and it doesn't
> > occur when I boot a kernel built from the preceding commit
> > (19ac737dc3c3).
> > 
> > If necessary, I can get debugging info by logging in over a network 
> > connection.  Tell me what you need.
> 
> It seems like Ville and Mika already caught a similar bug today, could
> you give Ville's patch a go (available on the intel-gfx):
> 
>   drm/i915: Don't call intel_plane_restore() when the prop value didn't change

Yes, that patch fixed the problem.  Thank you.

Tested-by: Alan Stern <stern@...land.harvard.edu>

Alan Stern

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