public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Dave Gordon <david.s.gordon@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for series starting with drm/i915: check for ERR_PTR from i915_gem_object_pin_map() (rev2)
Date: Wed, 20 Apr 2016 17:01:44 +0100	[thread overview]
Message-ID: <5717A7E8.8010906@linux.intel.com> (raw)
In-Reply-To: <570D2269.3050702@intel.com>



On 12/04/16 17:29, Dave Gordon wrote:
> On 12/04/16 17:03, Patchwork wrote:
>> == Series Details ==
>>
>> Series: series starting with drm/i915: check for ERR_PTR from
>> i915_gem_object_pin_map() (rev2)
>> URL   : https://patchwork.freedesktop.org/series/5591/
>> State : failure
>>
>> == Summary ==
>>
>> Series 5591v2 Series without cover letter
>> http://patchwork.freedesktop.org/api/1.0/series/5591/revisions/2/mbox/
>>
>> Test kms_flip:
>>          Subgroup basic-flip-vs-wf_vblank:
>>                  pass       -> FAIL       (snb-x220t)
>
> https://bugs.freedesktop.org/show_bug.cgi?id=94294
>
> "basic-flip-vs-wf_vblank timestamp vs. seq counter difference"
>
>> bdw-nuci7        total:203  pass:191  dwarn:0   dfail:0   fail:0
>> skip:12
>> bdw-ultra        total:203  pass:180  dwarn:0   dfail:0   fail:0
>> skip:23
>> bsw-nuc-2        total:202  pass:162  dwarn:1   dfail:0   fail:0
>> skip:39
>> byt-nuc          total:202  pass:164  dwarn:0   dfail:0   fail:0
>> skip:38
>> hsw-brixbox      total:203  pass:179  dwarn:0   dfail:0   fail:0
>> skip:24
>> hsw-gt2          total:203  pass:184  dwarn:0   dfail:0   fail:0
>> skip:19
>> ivb-t430s        total:203  pass:175  dwarn:0   dfail:0   fail:0
>> skip:28
>> skl-i7k-2        total:203  pass:178  dwarn:0   dfail:0   fail:0
>> skip:25
>> skl-nuci5        total:203  pass:192  dwarn:0   dfail:0   fail:0
>> skip:11
>> snb-x220t        total:203  pass:164  dwarn:0   dfail:0   fail:2
>> skip:37
>> BOOT FAILED for ilk-hp8440p
>> BOOT FAILED for snb-dellxps
>>
>> Results at /archive/results/CI_IGT_test/Patchwork_1872/
>>
>> d89f227a17b175fce74e11b2d5fa2a41f86fc489 drm-intel-nightly:
>> 2016y-04m-12d-13h-31m-26s UTC integration manifest
>> 33d810a drm/i915: Mark obj->mapping as dirtying the backing storage
>> 0d172b1 drm/i915: check for ERR_PTR from i915_gem_object_pin_map()

Merged the first one, thanks for the patch and review.

Regards,

Tvrtko




_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2016-04-20 16:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 13:32 [PATCH 1/2] drm/i915: Fix up ERR_PTR handling for pinning the ringbuffer Chris Wilson
2016-04-12 13:32 ` [PATCH 2/2] drm/i915: Mark obj->mapping as dirtying the backing storage Chris Wilson
2016-04-12 15:18   ` Chris Wilson
2016-04-20 19:38     ` Dave Gordon
2016-04-21 10:02     ` Dave Gordon
2016-04-12 13:46 ` [PATCH] drm/i915: check for ERR_PTR from i915_gem_object_pin_map() Dave Gordon
2016-04-12 13:53   ` Chris Wilson
2016-04-12 16:03 ` ✗ Fi.CI.BAT: failure for series starting with drm/i915: check for ERR_PTR from i915_gem_object_pin_map() (rev2) Patchwork
2016-04-12 16:29   ` Dave Gordon
2016-04-20 16:01     ` Tvrtko Ursulin [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=5717A7E8.8010906@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=david.s.gordon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox