From: Paul Bolle <pebolle@tiscali.nl>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: drm: i915: "plane B assertion failure, should be off on pipe B but is still active"
Date: Wed, 02 Jul 2014 10:53:23 +0200 [thread overview]
Message-ID: <1404291203.12021.18.camel@x220> (raw)
In-Reply-To: <87egy5h1yz.fsf@intel.com>
On Tue, 2014-07-01 at 12:17 +0300, Jani Nikula wrote:
> This does not ring any bells to me (but that doesn't prove anything). A
> bisect result would be awesome.
Too bad.
Unless someone else has a better idea I hope to start bisecting one of
these days (that might take quite some time, especially since I can't
yet narrow the bisect to changes in drivers/gpu/drm/i915/, can I?).
Don't expect results before v3.16-rc4.
Feel free to remind me if I stay silent on this subject for too long.
Paul Bolle
WARNING: multiple messages have this Message-ID (diff)
From: Paul Bolle <pebolle@tiscali.nl>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: drm: i915: "plane B assertion failure, should be off on pipe B but is still active"
Date: Wed, 02 Jul 2014 10:53:23 +0200 [thread overview]
Message-ID: <1404291203.12021.18.camel@x220> (raw)
In-Reply-To: <87egy5h1yz.fsf@intel.com>
On Tue, 2014-07-01 at 12:17 +0300, Jani Nikula wrote:
> This does not ring any bells to me (but that doesn't prove anything). A
> bisect result would be awesome.
Too bad.
Unless someone else has a better idea I hope to start bisecting one of
these days (that might take quite some time, especially since I can't
yet narrow the bisect to changes in drivers/gpu/drm/i915/, can I?).
Don't expect results before v3.16-rc4.
Feel free to remind me if I stay silent on this subject for too long.
Paul Bolle
next prev parent reply other threads:[~2014-07-02 8:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 15:05 drm: i915: "plane B assertion failure, should be off on pipe B but is still active" Paul Bolle
2014-07-01 9:17 ` Jani Nikula
2014-07-01 9:17 ` Jani Nikula
2014-07-02 8:53 ` Paul Bolle [this message]
2014-07-02 8:53 ` Paul Bolle
2014-07-13 20:32 ` Paul Bolle
2014-07-13 20:32 ` Paul Bolle
2014-07-14 6:56 ` Daniel Vetter
2014-07-14 6:56 ` Daniel Vetter
2014-07-14 7:13 ` Paul Bolle
2014-07-14 7:13 ` Paul Bolle
2014-07-14 7:18 ` Daniel Vetter
2014-07-14 7:18 ` Daniel Vetter
2014-07-14 16:47 ` Paul Bolle
2014-07-14 16:47 ` Paul Bolle
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=1404291203.12021.18.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.