From: Arun Siluvery <arun.siluvery@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: warning for drm/i915: Capture revision id in error state (rev2)
Date: Fri, 29 Jan 2016 11:08:53 +0000 [thread overview]
Message-ID: <56AB4845.7020200@linux.intel.com> (raw)
In-Reply-To: <20160129102709.21970.26973@annarchy.freedesktop.org>
On 29/01/2016 10:27, Patchwork wrote:
> == Summary ==
>
> Series 2850v2 drm/i915: Capture revision id in error state
> http://patchwork.freedesktop.org/api/1.0/series/2850/revisions/2/mbox/
>
> Test kms_flip:
> Subgroup basic-flip-vs-dpms:
> pass -> DMESG-WARN (ilk-hp8440p) UNSTABLE
[BAT ILK] sporadic fifo underruns in igt@kms_flip@basic-flip-vs-* on
ilk-hp8440p
known issue, https://bugs.freedesktop.org/show_bug.cgi?id=93787
> Test kms_force_connector_basic:
> Subgroup prune-stale-modes:
> pass -> SKIP (ilk-hp8440p)
It is not showing up in patchwork results page.
> Test kms_pipe_crc_basic:
> Subgroup bad-nb-words-1:
> pass -> DMESG-WARN (hsw-gt2)
known issue, it is not on P1 list though,
https://bugs.freedesktop.org/show_bug.cgi?id=93226
> Subgroup nonblocking-crc-pipe-a:
> skip -> PASS (byt-nuc)
It is not showing up in patchwork results page, checked detailed results
page and it was skipped once before.
> Subgroup nonblocking-crc-pipe-b:
> pass -> DMESG-WARN (ilk-hp8440p)
[BAT ILK] sporadic fifo underruns in igt@kms_flip@basic-flip-vs-* on
ilk-hp8440p
known issue, https://bugs.freedesktop.org/show_bug.cgi?id=93787
regards
Arun
>
> bdw-nuci7 total:156 pass:147 dwarn:0 dfail:0 fail:0 skip:9
> bdw-ultra total:159 pass:147 dwarn:0 dfail:0 fail:0 skip:12
> bsw-nuc-2 total:159 pass:129 dwarn:0 dfail:0 fail:0 skip:30
> byt-nuc total:159 pass:136 dwarn:0 dfail:0 fail:0 skip:23
> hsw-brixbox total:159 pass:146 dwarn:0 dfail:0 fail:0 skip:13
> hsw-gt2 total:159 pass:148 dwarn:1 dfail:0 fail:0 skip:10
> ilk-hp8440p total:159 pass:108 dwarn:2 dfail:0 fail:0 skip:49
> ivb-t430s total:159 pass:145 dwarn:0 dfail:0 fail:0 skip:14
> skl-i5k-2 total:159 pass:144 dwarn:1 dfail:0 fail:0 skip:14
> snb-dellxps total:159 pass:137 dwarn:0 dfail:0 fail:0 skip:22
> snb-x220t total:159 pass:137 dwarn:0 dfail:0 fail:1 skip:21
>
> Results at /archive/results/CI_IGT_test/Patchwork_1313/
>
> 5de97b25e5f3c5a63ee243a9d3b22d30792f7d3e drm-intel-nightly: 2016y-01m-29d-07h-32m-09s UTC integration manifest
> 76d742df11e81b8fa096b65c5f7864c6237afa6b drm/i915: Capture PCI revision and subsytem details in error state
>
>
_______________________________________________
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-29 11:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 17:52 [PATCH] drm/i915: Capture revision id in error state Arun Siluvery
2016-01-27 11:33 ` Ville Syrjälä
2016-01-27 11:44 ` Arun Siluvery
2016-01-27 17:46 ` Chris Wilson
2016-01-27 17:38 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-01-28 14:33 ` Patchwork
2016-01-28 17:18 ` [PATCH] drm/i915: Capture PCI revision and subsytem details " Arun Siluvery
2016-02-10 7:47 ` Daniel Vetter
2016-01-29 10:27 ` ✗ Fi.CI.BAT: warning for drm/i915: Capture revision id in error state (rev2) Patchwork
2016-01-29 11:08 ` Arun Siluvery [this message]
2016-02-10 7:48 ` 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=56AB4845.7020200@linux.intel.com \
--to=arun.siluvery@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;
as well as URLs for NNTP newsgroup(s).