From: Paulo Zanoni <paulo.r.zanoni@intel.com>
To: "chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>,
Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [CI 10/21] drm/i915: Mark up all locked waiters
Date: Thu, 22 Sep 2016 16:05:51 -0300 [thread overview]
Message-ID: <1474571151.3073.0.camel@intel.com> (raw)
In-Reply-To: <20160914084001.GF25204@nuc-i3427.alporthouse.com>
Em Qua, 2016-09-14 às 09:40 +0100, chris@chris-wilson.co.uk escreveu:
> On Tue, Sep 13, 2016 at 03:21:48PM +0300, Mika Kuoppala wrote:
> >
> > Mika Kuoppala <mika.kuoppala@linux.intel.com> writes:
> > >
> > > "Zanoni, Paulo R" <paulo.r.zanoni@intel.com> writes:
> > > >
> > > > >
> > > > > +#if IS_ENABLED(CONFIG_LOCKDEP)
> > > > > + GEM_BUG_ON(!!lockdep_is_held(&req->i915-
> > > > > >drm.struct_mutex)
> > > > > !=
> > > > > + !!(flags & I915_WAIT_LOCKED));
> > > > > +#endif
> > > >
> > > > I'm hitting this on my SKL. It usually happens right after the
> > > > login,
> > > > when I click the terminal icon on the toolbar in order to open
> > > > it (on
> > > > Cinnamon). When it doesn't happen at that time, I just open a
> > > > browser
> > > > and browse for like 30 seconds until it happens.
> > > >
> > > > I did manual reverts of this series up to this patch and
> > > > obviously the
> > > > problem goes away (no more GEM_BUG_ON to hit). I didn't try to
> > > > do a
> > > > real bisect to check if this is the first bad commit or if it's
> > > > something later on the series. It could even be an older
> > > > problem that
> > > > just got exposed by the new BUG(). I'm available to test
> > > > patches, just
> > > > send them to me.
> > >
> > > No patches yet but there is a comment on
> > > intel_prepare_plane_fb() that says that it must be called with
> > > mutex
> > > held.
> > >
> > > Quite likely the new GEM_BUG_ON catches this not being true.
> > >
> >
> > As Chris pointed out in irc, its about the reverse. Waiting
> > with mutex when you shouldn't.
>
> Fwiw, the fix is now on the list.
Can you please tell us which patch it is? I see we still have this
problem.
Thanks,
Paulo
> -Chris
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-09-22 19:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 13:11 [CI 01/21] drm/i915: Add a sw fence for collecting up dma fences Chris Wilson
2016-09-09 13:11 ` [CI 02/21] drm/i915: Only queue requests during execlists submission Chris Wilson
2016-09-09 13:11 ` [CI 03/21] drm/i915: Record the position of the workarounds in the tail of the request Chris Wilson
2016-09-09 13:11 ` [CI 04/21] drm/i915: Compute the ELSP register location once Chris Wilson
2016-09-09 13:11 ` [CI 05/21] drm/i915: Reorder submitting the requests to ELSP Chris Wilson
2016-09-09 13:11 ` [CI 06/21] drm/i915: Simplify ELSP queue request tracking Chris Wilson
2016-09-09 13:11 ` [CI 07/21] drm/i915: Separate out reset flags from the reset counter Chris Wilson
2016-09-09 13:11 ` [CI 08/21] drm/i915: Drop local struct_mutex around intel_init_emon[ilk] Chris Wilson
2016-09-09 13:11 ` [CI 09/21] drm/i915: Expand bool interruptible to pass flags to i915_wait_request() Chris Wilson
2016-09-09 13:11 ` [CI 10/21] drm/i915: Mark up all locked waiters Chris Wilson
2016-09-12 19:17 ` Zanoni, Paulo R
2016-09-13 10:59 ` Mika Kuoppala
2016-09-13 12:21 ` Mika Kuoppala
2016-09-14 8:40 ` chris
2016-09-22 19:05 ` Paulo Zanoni [this message]
2016-09-23 7:45 ` chris
2016-09-09 13:11 ` [CI 11/21] drm/i915: Perform a direct reset of the GPU from the waiter Chris Wilson
2016-09-09 13:11 ` [CI 12/21] drm/i915: Replace wait-on-mutex with wait-on-bit in reset worker Chris Wilson
2016-09-09 13:11 ` [CI 13/21] drm/i915: Update reset path to fix incomplete requests Chris Wilson
2016-09-09 13:11 ` [CI 14/21] drm/i915: Drive request submission through fence callbacks Chris Wilson
2016-09-09 13:11 ` [CI 15/21] drm/i915: Reorder i915_add_request to separate the phases better Chris Wilson
2016-09-09 13:11 ` [CI 16/21] drm/i915: Prepare object synchronisation for asynchronicity Chris Wilson
2016-09-09 13:11 ` [CI 17/21] drm/i915/guc: Prepare for nonblocking execbuf submission Chris Wilson
2016-09-09 13:11 ` [CI 18/21] drm/i915: Ignore valid but unknown semaphores Chris Wilson
2016-09-09 13:11 ` [CI 19/21] drm/i915: Avoid incrementing hangcheck whilst waiting for external fence Chris Wilson
2016-09-09 13:12 ` [CI 20/21] drm/i915: Nonblocking request submission Chris Wilson
2016-09-09 13:12 ` [CI 21/21] drm/i915: Serialise execbuf operation after a dma-buf reservation object Chris Wilson
2016-09-12 8:23 ` ✓ Fi.CI.BAT: success for series starting with [CI,01/21] drm/i915: Add a sw fence for collecting up dma fences Patchwork
-- strict thread matches above, loose matches on Subject: below --
2016-09-09 11:00 [CI 01/21] " Chris Wilson
2016-09-09 11:00 ` [CI 10/21] drm/i915: Mark up all locked waiters Chris Wilson
2016-09-09 7:20 [CI 01/21] drm/i915: Add a sw fence for collecting up dma fences Chris Wilson
2016-09-09 7:20 ` [CI 10/21] drm/i915: Mark up all locked waiters Chris Wilson
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=1474571151.3073.0.camel@intel.com \
--to=paulo.r.zanoni@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.intel.com \
/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).