From: Damien Lespiau <damien.lespiau@intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Daniel Vetter <daniel@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] Regression in drm-intel caused by d91a2cb8e510
Date: Mon, 1 Sep 2014 23:13:44 +0100 [thread overview]
Message-ID: <20140901221344.GA22902@strange.ger.corp.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1409011609390.13894-100000@netrider.rowland.org>
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
Thanks,
--
Damien
next prev parent reply other threads:[~2014-09-01 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 20:19 Regression in drm-intel caused by d91a2cb8e510 Alan Stern
2014-09-01 22:13 ` Damien Lespiau [this message]
2014-09-02 1:23 ` [Intel-gfx] " Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140901221344.GA22902@strange.ger.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox