From: "Ville Syrjälä" <syrjala@sci.fi>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Meelis Roos <mroos@linux.ee>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: i915 pipe A assertion failure (expected on, current off)
Date: Sat, 21 Sep 2013 19:03:06 +0300 [thread overview]
Message-ID: <20130921160306.GE3501@sci.fi> (raw)
In-Reply-To: <CAKMK7uHynzChMurTLAYMfeRF07aDJxes-6eSO1iDbrET8xD84Q@mail.gmail.com>
On Sat, Sep 21, 2013 at 05:48:42PM +0200, Daniel Vetter wrote:
> On Sat, Sep 21, 2013 at 5:29 PM, Meelis Roos <mroos@linux.ee> wrote:
> >> Tried 3.11-rc7 on Thinkpad X30 (first 3-11-rc tried on this hw). Works
> >> but i915 gives strange assertion failure with WARNING stack trace. This
> >> is new since 3.10.
> >
> > It is still there with 3.12-rc1 but now I git around to bisecting it.
> > This is the commit that introduces the warning.
> >
> > commit 9f11a9e4e50006b615ba94722dfc33ced89664cf
> > Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Date: Thu Jun 13 00:54:58 2013 +0200
> >
> > drm/i915: set up PIPECONF explicitly for i9xx/vlv platforms
>
> My apologies for not responding to your first report, fell through the
> cracks somehow. Can you please boot with drm.debug=0xe, reproduce the
> WARN and grab the full dmesg (please make sure everything from boot-up
> is in there). That's usually enough to figure out what's going wrong
> here.
I'd say it's a simple matter of forgetting about QUIRK_PIPEA_FORCE in
i9xx_set_pipeconf().
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
next prev parent reply other threads:[~2013-09-21 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 13:14 i915 pipe A assertion failure (expected on, current off) Meelis Roos
2013-09-21 15:29 ` Meelis Roos
2013-09-21 15:48 ` Daniel Vetter
2013-09-21 16:03 ` Ville Syrjälä [this message]
2013-09-22 6:02 ` Meelis Roos
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=20130921160306.GE3501@sci.fi \
--to=syrjala@sci.fi \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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;
as well as URLs for NNTP newsgroup(s).