From: Dave Gordon <david.s.gordon@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Ro.CI.BAT: failure for series starting with [1/5] drm/i915/guc: doorbell reset should avoid used doorbells
Date: Tue, 19 Jul 2016 16:07:39 +0100 [thread overview]
Message-ID: <578E423B.1030700@intel.com> (raw)
In-Reply-To: <20160719141600.15800.68027@emeril.freedesktop.org>
On 19/07/16 15:16, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [1/5] drm/i915/guc: doorbell reset should avoid used doorbells
> URL : https://patchwork.freedesktop.org/series/10040/
> State : failure
>
> == Summary ==
>
> Series 10040v1 Series without cover letter
> http://patchwork.freedesktop.org/api/1.0/series/10040/revisions/1/mbox
>
> Test drv_module_reload_basic:
> pass -> SKIP (ro-hsw-i3-4010u)
> Test gem_sync:
> Subgroup basic-store-each:
> fail -> PASS (ro-bdw-i7-5600u)
> Test kms_cursor_legacy:
> Subgroup basic-cursor-vs-flip:
> pass -> FAIL (ro-ilk1-i5-650)
Wibble? The test log for this says:
+ Results for igt@kms_cursor_legacy@basic-flip-vs-cursor
+ Result: pass
+
+ IGT-Version: 1.15-g4d03467 (x86_64) (Linux:
4.7.0-rc7-gfxbench-RO_Patchwork_1532+ x86_64)
+ Test requirement not met in function __real_main427, file
kms_cursor_legacy.c:448:
+ Test requirement: !(n >= data.resources->count_crtcs)
+ Subtest basic-flip-vs-cursor: SUCCESS (1.156s)
+
+ Command /opt/igt/tests/kms_cursor_legacy --run-subtest
basic-flip-vs-cursor
So whatever that unfulfilled test requirement is, the result should be PASS.
> Test kms_pipe_crc_basic:
> Subgroup read-crc-pipe-c-frame-sequence:
> pass -> DMESG-WARN (fi-hsw-i7-4770k)
[ 436.687908] [drm:drm_edid_block_valid] *ERROR* EDID checksum is
invalid, remainder is 122
[ 436.688345] [drm:drm_edid_block_valid] *ERROR* EDID checksum is
invalid, remainder is 122
which looks like
https://bugzilla.kernel.org/show_bug.cgi?id=85951
[hsw] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid,
remainder is 46
(which was closed as unreproducible)
.Dave.
> Subgroup suspend-read-crc-pipe-c:
> pass -> SKIP (fi-hsw-i7-4770k)
> Test prime_vgem:
> Subgroup basic-fence-read:
> fail -> PASS (ro-byt-n2820)
>
> fi-hsw-i7-4770k total:243 pass:211 dwarn:1 dfail:0 fail:10 skip:21
> fi-kbl-qkkr total:243 pass:177 dwarn:26 dfail:1 fail:10 skip:29
> fi-skl-i7-6700k total:243 pass:208 dwarn:0 dfail:0 fail:9 skip:26
> fi-snb-i7-2600 total:243 pass:193 dwarn:0 dfail:0 fail:10 skip:40
> ro-bdw-i5-5250u total:244 pass:217 dwarn:4 dfail:0 fail:10 skip:13
> ro-bdw-i7-5557U total:244 pass:219 dwarn:1 dfail:0 fail:9 skip:15
> ro-bdw-i7-5600u total:244 pass:202 dwarn:0 dfail:0 fail:10 skip:32
> ro-bsw-n3050 total:218 pass:173 dwarn:0 dfail:0 fail:2 skip:42
> ro-byt-n2820 total:244 pass:195 dwarn:0 dfail:0 fail:11 skip:38
> ro-hsw-i3-4010u total:244 pass:208 dwarn:0 dfail:0 fail:11 skip:25
> ro-hsw-i7-4770r total:244 pass:209 dwarn:0 dfail:0 fail:11 skip:24
> ro-ilk1-i5-650 total:239 pass:169 dwarn:0 dfail:0 fail:12 skip:58
> ro-ivb-i7-3770 total:244 pass:200 dwarn:0 dfail:0 fail:11 skip:33
> ro-skl3-i5-6260u total:244 pass:221 dwarn:1 dfail:0 fail:10 skip:12
> ro-snb-i7-2620M total:244 pass:190 dwarn:0 dfail:0 fail:12 skip:42
> fi-skl-i5-6260u failed to connect after reboot
>
> Results at /archive/results/CI_IGT_test/RO_Patchwork_1532/
>
> 635555a drm-intel-nightly: 2016y-07m-19d-13h-02m-39s UTC integration manifest
> 207ec9d drm/i915/guc: use for_each_engine_id() where appropriate
> 5982c52 drm/i915/guc: add engine mask to GuC client & pass to GuC
> b1f5991 drm/i915/guc: use a separate GuC client for each engine
> 89623f4 drm/i915/guc: refactor guc_init_doorbell_hw()
> b9c0a41 drm/i915/guc: doorbell reset should avoid used doorbells
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-07-19 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 12:59 [PATCH 1/5] drm/i915/guc: doorbell reset should avoid used doorbells Dave Gordon
2016-07-19 12:59 ` [PATCH 2/5] drm/i915/guc: refactor guc_init_doorbell_hw() Dave Gordon
2016-07-19 14:51 ` Tvrtko Ursulin
2016-07-19 12:59 ` [PATCH 3/5] drm/i915/guc: use a separate GuC client for each engine Dave Gordon
2016-07-19 15:02 ` Tvrtko Ursulin
2016-07-19 15:13 ` Dave Gordon
2016-07-19 12:59 ` [PATCH 4/5] drm/i915/guc: add engine mask to GuC client & pass to GuC Dave Gordon
2016-07-19 15:06 ` Tvrtko Ursulin
2016-07-27 20:06 ` kbuild test robot
2016-07-19 12:59 ` [PATCH 5/5] drm/i915/guc: use for_each_engine_id() where appropriate Dave Gordon
2016-07-19 15:09 ` Tvrtko Ursulin
2016-07-19 14:16 ` ✗ Ro.CI.BAT: failure for series starting with [1/5] drm/i915/guc: doorbell reset should avoid used doorbells Patchwork
2016-07-19 15:07 ` Dave Gordon [this message]
2016-07-19 14:43 ` [PATCH 1/5] " Tvrtko Ursulin
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=578E423B.1030700@intel.com \
--to=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 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.