All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Move load time stolen memory init earlier
Date: Mon, 25 Jan 2016 18:47:08 +0100	[thread overview]
Message-ID: <20160125174708.GJ11240@phenom.ffwll.local> (raw)
In-Reply-To: <1453743248.1054.43.camel@intel.com>

On Mon, Jan 25, 2016 at 07:34:08PM +0200, Imre Deak wrote:
> On ma, 2016-01-25 at 17:21 +0100, Daniel Vetter wrote:
> > On Tue, Jan 19, 2016 at 06:22:21PM +0200, Imre Deak wrote:
> > > On ti, 2016-01-19 at 13:49 +0000, Patchwork wrote:
> > > > == Summary ==
> > > > 
> > > > Built on 00a0c7d1ae09b1259c7af8e5a088b0b225d805df drm-intel-
> > > > nightly:
> > > > 2016y-01m-18d-16h-50m-37s UTC integration manifest
> > > > 
> > > > Test gem_ctx_basic:
> > > >                 pass       -> FAIL       (bdw-ultra)
> > > 
> > > Couldn't reproduce it on the same machine. To me it looks unrelated
> > > as
> > > it happened already several times for other patches, always on the
> > > same
> > > machine. These BAT results are not shown on the test's "long term"
> > > history btw. I filed a bug: 
> > 
> > long term only shows changes, not all tests.
> 
> Ok, so I take that's changes for CI runs, but not for patchwork
> initiated tests.
> 
> > Which means it didn't yet
> > fail in -nightly, which is somewhat suspicious ... But I agree that
> > this
> > seems to have blown up a few times in other CI runs.
> 
> Ok, so based on that this patchset is good to go I guess.
> 
> Still not sure why the test fails. One thing I noticed is a bunch of
> "gem_concurrent: drop caches" messages in dmesg before any test would
> be even started. So I think something in gem_concurrent is not guarded
> with igt_fixture{} and gets to run when piglit enumerates the subtests
> (to get the BAT subtests). Not sure though if this has a negative
> effect on anything.

We iirc drop caches as part of gem_quiescent too.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2016-01-25 17:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 13:26 [PATCH 0/7] drm/i915: Move load time stolen memory init earlier Imre Deak
2016-01-19 13:26 ` [PATCH 1/7] drm/i915: Sanitize up DMC/CSR ucode cleanup code Imre Deak
2016-01-22 12:10   ` David Weinehall
2016-01-19 13:26 ` [PATCH 2/7] drm/i915: Sanitize i915_get_bridge_dev() error path Imre Deak
2016-01-22 12:11   ` David Weinehall
2016-01-19 13:26 ` [PATCH 3/7] drm/i915: Sanitize GEM shrinker init and clean-up Imre Deak
2016-01-22 12:15   ` David Weinehall
2016-01-19 13:26 ` [PATCH 4/7] drm/i915: Sanitize i915_gem_load() " Imre Deak
2016-01-22 12:17   ` David Weinehall
2016-01-19 13:26 ` [PATCH 5/7] drm/i915: Move allocation of various workqueues earlier during init Imre Deak
2016-01-22 12:19   ` David Weinehall
2016-01-19 13:26 ` [PATCH 6/7] drm/i915: Move MCHBAR setup " Imre Deak
2016-01-22 12:21   ` David Weinehall
2016-01-19 13:26 ` [PATCH 7/7] drm/i915: Move stolen memory initialization earlier during loading Imre Deak
2016-01-22 12:23   ` David Weinehall
2016-01-27 16:39     ` Imre Deak
2016-01-19 13:49 ` ✗ Fi.CI.BAT: failure for drm/i915: Move load time stolen memory init earlier Patchwork
2016-01-19 16:22   ` Imre Deak
2016-01-25 16:21     ` Daniel Vetter
2016-01-25 17:34       ` Imre Deak
2016-01-25 17:47         ` Daniel Vetter [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=20160125174708.GJ11240@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@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 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.