From: "Bjørn Mork" <bjorn@mork.no>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: pipe B assertion failure (expected off, current on)
Date: Thu, 11 Oct 2012 17:47:58 +0200 [thread overview]
Message-ID: <87txu1f1sh.fsf@nemi.mork.no> (raw)
In-Reply-To: <CAKMK7uGDCWOguPwd2N_qZ6puBMSJZCeOyaNnx_YQZ4gDOyoYjg@mail.gmail.com> (Daniel Vetter's message of "Thu, 11 Oct 2012 17:22:24 +0200")
Daniel Vetter <daniel.vetter@ffwll.ch> writes:
> On Thu, Oct 11, 2012 at 4:13 PM, Bjørn Mork <bjorn@mork.no> wrote:
>> Let me know if you want ot have more details about these warnings.
>> Otherwise I'll just keep ignoring them ;-)
>
> The drm-intel-fixes branch from
> http://cgit.freedesktop.org/~danvet/drm-intel has a patch to fix some
> of the already reported WARNs. Note that the issue itself is really
> old, it's just that the new i915.ko modeset code is really anal with
> reporting even slight inconsistencies. And some of these WARNs even
> brought some real bugs to the light.
Yes, that was pretty much what I assumed.
> If drm-intel-fixes doesn't get rid of them, please attach a complete
> dmesg withd drm.debug=0xe added to your kernel cmdline. The dmesg
> should include everything up to the first pile of WARNs.
Thanks. Will try the fixes.
Bjørn
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2012-10-11 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 14:13 pipe B assertion failure (expected off, current on) Bjørn Mork
2012-10-11 15:22 ` Daniel Vetter
2012-10-11 15:47 ` Bjørn Mork [this message]
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=87txu1f1sh.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox