From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org, Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Move CSB MMIO reads out of the execlists lock (rev4)
Date: Fri, 18 Mar 2016 10:31:12 +0000 [thread overview]
Message-ID: <56EBD8F0.5070103@linux.intel.com> (raw)
In-Reply-To: <20160318070243.13087.64395@emeril.freedesktop.org>
On 18/03/16 07:02, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Move CSB MMIO reads out of the execlists lock (rev4)
> URL : https://patchwork.freedesktop.org/series/3973/
> State : failure
>
> == Summary ==
>
> Series 3973v4 drm/i915: Move CSB MMIO reads out of the execlists lock
> http://patchwork.freedesktop.org/api/1.0/series/3973/revisions/4/mbox/
>
> Test gem_ringfill:
> Subgroup basic-default-s3:
> dmesg-warn -> PASS (skl-nuci5)
> Test gem_storedw_loop:
> Subgroup basic-default:
> dmesg-warn -> PASS (skl-nuci5)
> Test gem_sync:
> Subgroup basic-vebox:
> dmesg-warn -> PASS (skl-nuci5)
> Test kms_flip:
> Subgroup basic-flip-vs-wf_vblank:
> pass -> DMESG-WARN (bdw-ultra)
Device suspended during HW access:
https://bugs.freedesktop.org/show_bug.cgi?id=94349
> Test kms_pipe_crc_basic:
> Subgroup nonblocking-crc-pipe-c-frame-sequence:
> pass -> DMESG-WARN (hsw-brixbox)
Unclaimed register: https://bugs.freedesktop.org/show_bug.cgi?id=94384
> Subgroup read-crc-pipe-a-frame-sequence:
> dmesg-warn -> PASS (hsw-gt2)
> Subgroup suspend-read-crc-pipe-b:
> pass -> INCOMPLETE (hsw-gt2)
Haswell does not use the code touched here so I am discounting this as
unrelated.
> Subgroup suspend-read-crc-pipe-c:
> dmesg-warn -> PASS (bsw-nuc-2)
> Test pm_rpm:
> Subgroup basic-pci-d3-state:
> pass -> DMESG-WARN (hsw-brixbox)
Device suspended during HW access:
https://bugs.freedesktop.org/show_bug.cgi?id=94349
>
> bdw-ultra total:194 pass:171 dwarn:2 dfail:0 fail:0 skip:21
> bsw-nuc-2 total:194 pass:156 dwarn:1 dfail:0 fail:0 skip:37
> hsw-brixbox total:194 pass:169 dwarn:3 dfail:0 fail:0 skip:22
> hsw-gt2 total:115 pass:104 dwarn:1 dfail:0 fail:0 skip:9
> ivb-t430s total:194 pass:168 dwarn:1 dfail:0 fail:0 skip:25
> skl-i5k-2 total:194 pass:170 dwarn:1 dfail:0 fail:0 skip:23
> skl-i7k-2 total:194 pass:170 dwarn:1 dfail:0 fail:0 skip:23
> skl-nuci5 total:194 pass:182 dwarn:1 dfail:0 fail:0 skip:11
>
> Results at /archive/results/CI_IGT_test/Patchwork_1632/
>
> 10e913a48ca36790da9b58bed8729598ea79ebdb drm-intel-nightly: 2016y-03m-17d-13h-22m-41s UTC integration manifest
> f6a228bfa750f3f23c1a95ca76f08b148a02f2a5 drm/i915: Move CSB MMIO reads out of the execlists lock
Merged, thanks for the review.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-03-18 10:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 12:59 [PATCH v3] drm/i915: Move CSB MMIO reads out of the execlists lock Tvrtko Ursulin
2016-03-17 13:14 ` Chris Wilson
2016-03-17 16:30 ` Tvrtko Ursulin
2016-03-21 9:22 ` Daniel Vetter
2016-03-18 7:02 ` ✗ Fi.CI.BAT: failure for drm/i915: Move CSB MMIO reads out of the execlists lock (rev4) Patchwork
2016-03-18 10:31 ` Tvrtko Ursulin [this message]
2016-03-18 9:46 ` Patchwork
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=56EBD8F0.5070103@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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