From: Arun Siluvery <arun.siluvery@linux.intel.com>
To: Patchwork <patchwork@annarchy.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: warning for drm/i915/gen9: Correct max save/restore register count during gpu reset with GuC
Date: Tue, 19 Jan 2016 17:51:02 +0000 [thread overview]
Message-ID: <569E7786.4010300@linux.intel.com> (raw)
In-Reply-To: <20160118162057.11857.65199@annarchy.freedesktop.org>
On 18/01/2016 16:20, Patchwork wrote:
> == Summary ==
>
> Built on 98ee62c2326e0b6881eb0f427895aab745febf6f drm-intel-nightly: 2016y-01m-18d-14h-18m-27s UTC integration manifest
>
> Test gem_storedw_loop:
> Subgroup basic-render:
> pass -> DMESG-WARN (skl-i5k-2) UNSTABLE
> pass -> DMESG-WARN (skl-i7k-2) UNSTABLE
This patch updates a #define which is only relevant in GuC Submission
mode (which is disabled by default).
This dmesg-warn is because of an existing issue,
https://bugs.freedesktop.org/show_bug.cgi?id=93693
> Test kms_pipe_crc_basic:
> Subgroup read-crc-pipe-b-frame-sequence:
> pass -> DMESG-WARN (byt-nuc)
This is because of https://bugs.freedesktop.org/show_bug.cgi?id=93121
regards
Arun
> Subgroup suspend-read-crc-pipe-a:
> dmesg-warn -> PASS (snb-x220t)
>
> bdw-nuci7 total:140 pass:131 dwarn:0 dfail:0 fail:0 skip:9
> bdw-ultra total:140 pass:132 dwarn:1 dfail:1 fail:0 skip:6
> bsw-nuc-2 total:143 pass:117 dwarn:2 dfail:0 fail:0 skip:24
> byt-nuc total:143 pass:124 dwarn:4 dfail:0 fail:0 skip:15
> hsw-brixbox total:143 pass:136 dwarn:0 dfail:0 fail:0 skip:7
> hsw-gt2 total:143 pass:139 dwarn:0 dfail:0 fail:0 skip:4
> ilk-hp8440p total:143 pass:102 dwarn:3 dfail:0 fail:0 skip:38
> ivb-t430s total:137 pass:124 dwarn:3 dfail:4 fail:0 skip:6
> skl-i5k-2 total:143 pass:133 dwarn:2 dfail:0 fail:0 skip:8
> skl-i7k-2 total:143 pass:133 dwarn:2 dfail:0 fail:0 skip:8
> snb-dellxps total:143 pass:124 dwarn:5 dfail:0 fail:0 skip:14
> snb-x220t total:143 pass:124 dwarn:5 dfail:0 fail:1 skip:13
>
> Results at /archive/results/CI_IGT_test/Patchwork_1214/
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-01-19 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 15:59 [PATCH] drm/i915/gen9: Correct max save/restore register count during gpu reset with GuC Arun Siluvery
2016-01-18 16:20 ` ✗ Fi.CI.BAT: warning for " Patchwork
2016-01-18 16:29 ` Arun Siluvery
2016-01-19 17:51 ` Arun Siluvery [this message]
2016-01-19 18:13 ` [PATCH] " Yu Dai
2016-01-19 19:38 ` Daniel Vetter
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=569E7786.4010300@linux.intel.com \
--to=arun.siluvery@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@annarchy.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;
as well as URLs for NNTP newsgroup(s).