Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Execlists cannot pin a context without the object
Date: Fri, 26 Feb 2016 13:51:17 +0000	[thread overview]
Message-ID: <56D05855.10505@linux.intel.com> (raw)
In-Reply-To: <56D04F64.3060107@linux.intel.com>


On 26/02/16 13:13, Tvrtko Ursulin wrote:
>
>
> On 26/02/16 12:28, Patchwork wrote:
>> == Series Details ==
>>
>> Series: drm/i915: Execlists cannot pin a context without the object
>> URL   : https://patchwork.freedesktop.org/series/3845/
>> State : failure
>>
>> == Summary ==
>>
>> Series 3845v1 drm/i915: Execlists cannot pin a context without the object
>> http://patchwork.freedesktop.org/api/1.0/series/3845/revisions/1/mbox/
>>
>> Test drv_module_reload_basic:
>>                  fail       -> PASS       (snb-dellxps)
>> Test gem_sync:
>>          Subgroup basic-bsd:
>>                  pass       -> DMESG-FAIL (ilk-hp8440p)
>
> New unrelated: https://bugs.freedesktop.org/show_bug.cgi?id=94307
>
>> Test kms_force_connector_basic:
>>          Subgroup force-load-detect:
>>                  fail       -> DMESG-FAIL (ivb-t430s)
>
> New unrelated: https://bugs.freedesktop.org/show_bug.cgi?id=94306
>
>> Test kms_pipe_crc_basic:
>>          Subgroup suspend-read-crc-pipe-b:
>>                  pass       -> INCOMPLETE (hsw-gt2)
>
> ???
>
>> Test pm_rpm:
>>          Subgroup basic-rte:
>>                  pass       -> FAIL       (bdw-nuci7)
>>
>> bdw-nuci7        total:165  pass:153  dwarn:0   dfail:0   fail:1
>> skip:11
>> bdw-ultra        total:168  pass:154  dwarn:0   dfail:0   fail:0
>> skip:14
>> bsw-nuc-2        total:168  pass:137  dwarn:0   dfail:0   fail:1
>> skip:30
>> byt-nuc          total:168  pass:143  dwarn:0   dfail:0   fail:0
>> skip:25
>> hsw-brixbox      total:168  pass:154  dwarn:0   dfail:0   fail:0
>> skip:14
>> hsw-gt2          total:79   pass:75   dwarn:0   dfail:0   fail:0   skip:3
>> ilk-hp8440p      total:168  pass:117  dwarn:0   dfail:1   fail:1
>> skip:49
>> ivb-t430s        total:168  pass:153  dwarn:0   dfail:1   fail:0
>> skip:14
>> skl-i7k-2        total:168  pass:151  dwarn:1   dfail:0   fail:0
>> skip:16
>> snb-dellxps      total:168  pass:145  dwarn:0   dfail:0   fail:1
>> skip:22
>> snb-x220t        total:168  pass:145  dwarn:0   dfail:0   fail:2
>> skip:21
>>
>> Results at /archive/results/CI_IGT_test/Patchwork_1482/
>>
>> 3401f93d4f525073bfea774c7d5bb927497effd9 drm-intel-nightly:
>> 2016y-02m-26d-11h-30m-51s UTC integration manifest
>> 0d643e82fdf6ddd553bf220d1319a560a00c5957 drm/i915: Execlists cannot
>> pin a context without the object

Merged, thanks for the patch!

Regards,

Tvrtko

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

      reply	other threads:[~2016-02-26 13:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 11:22 [PATCH] drm/i915: Execlists cannot pin a context without the object Tvrtko Ursulin
2016-02-26 12:28 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-02-26 13:13   ` Tvrtko Ursulin
2016-02-26 13:51     ` 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=56D05855.10505@linux.intel.com \
    --to=tvrtko.ursulin@linux.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