From: Arun Siluvery <arun.siluvery@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for Capture more useful details in error state (rev3)
Date: Mon, 29 Feb 2016 10:32:12 +0000 [thread overview]
Message-ID: <56D41E2C.8040608@linux.intel.com> (raw)
In-Reply-To: <20160226170113.30359.88233@emeril.freedesktop.org>
On 26/02/2016 17:01, Patchwork wrote:
> == Series Details ==
>
> Series: Capture more useful details in error state (rev3)
> URL : https://patchwork.freedesktop.org/series/2906/
> State : failure
>
> == Summary ==
>
> Series 2906v3 Capture more useful details in error state
> http://patchwork.freedesktop.org/api/1.0/series/2906/revisions/3/mbox/
>
> Test drv_hangman:
> Subgroup error-state-basic:
> pass -> INCOMPLETE (snb-dellxps)
> pass -> FAIL (ilk-hp8440p)
No log available for INCOMPLETE case.
For FAIL case below commit is the suspect which replaces stop_ring with
a real gpu hang. I tried this subtest on SKL and it works fine, possibly
affecting old gen (also successful on BAT)
https://bugs.freedesktop.org/show_bug.cgi?id=94305
commit 0753057446da0c74843c8a1000f589797da9388d
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Fri Dec 11 13:27:49 2015 +0000
igt/drv_hangman: Inject a true hang
Wean drv_hangman off the atrocious stop_rings and use a real GPU
hang instead.
> Test kms_flip:
> Subgroup basic-flip-vs-dpms:
> dmesg-warn -> PASS (ilk-hp8440p) UNSTABLE
> Subgroup basic-flip-vs-modeset:
> incomplete -> PASS (ilk-hp8440p) UNSTABLE
> Subgroup basic-flip-vs-wf_vblank:
> pass -> FAIL (snb-x220t)
known issue, https://bugs.freedesktop.org/show_bug.cgi?id=94294
> Test kms_force_connector_basic:
> Subgroup force-load-detect:
> fail -> DMESG-FAIL (snb-x220t)
unrelated to this patch, looks like it has been like this for a while:
/archive/results/CI_IGT_test/igt@kms_force_connector_basic@force-load-detect.html
> Test kms_pipe_crc_basic:
> Subgroup suspend-read-crc-pipe-b:
> incomplete -> PASS (hsw-gt2)
> pass -> DMESG-WARN (ivb-t430s)
could be related to this?
https://bugs.freedesktop.org/show_bug.cgi?id=93787
> Subgroup suspend-read-crc-pipe-c:
> pass -> DMESG-WARN (bsw-nuc-2)
https://bugs.freedesktop.org/show_bug.cgi?id=93294
> Test pm_rpm:
> Subgroup basic-pci-d3-state:
> pass -> DMESG-WARN (bsw-nuc-2)
unrelated, failed couple of times on previous BAT runs
regards
Arun
>
> bdw-nuci7 total:166 pass:155 dwarn:0 dfail:0 fail:0 skip:11
> bdw-ultra total:169 pass:155 dwarn:0 dfail:0 fail:0 skip:14
> bsw-nuc-2 total:169 pass:136 dwarn:2 dfail:0 fail:1 skip:30
> byt-nuc total:169 pass:144 dwarn:0 dfail:0 fail:0 skip:25
> hsw-brixbox total:169 pass:155 dwarn:0 dfail:0 fail:0 skip:14
> hsw-gt2 total:169 pass:158 dwarn:0 dfail:1 fail:0 skip:10
> ilk-hp8440p total:169 pass:118 dwarn:0 dfail:1 fail:1 skip:49
> ivb-t430s total:169 pass:153 dwarn:1 dfail:0 fail:1 skip:14
> skl-i7k-2 total:169 pass:152 dwarn:1 dfail:0 fail:0 skip:16
> snb-dellxps total:20 pass:18 dwarn:0 dfail:0 fail:0 skip:1
> snb-x220t total:169 pass:145 dwarn:0 dfail:1 fail:2 skip:21
>
> Results at /archive/results/CI_IGT_test/Patchwork_1486/
>
> e511a05b4b3bb4d1dbca99b00af6d0dc0a65d295 drm-intel-nightly: 2016y-02m-26d-13h-42m-46s UTC integration manifest
> c072adf745e744b6d20d1fdcdc2979235430599e drm/i915/error: Capture WA ctx batch in error state
> d187fe59fc41065bf02447604c2df9fbcc20a337 drm/i915/error: add GuC state error capture & decode
> 42341a5325b0b2dde27ecd09f4a536ecb1036c2b drm/i915/guc: Improve action error reporting
> 6dfb136e296a5906cde48fe578d7a9f5fc53cf3b drm/i915/error: enhanced error capture of requests
> 57b7c25ac7e9595d29cc4e7be4b5890069d249bb drm/i915/error: capture errored context based on request context-id
> 01bc355da54332af17ea674c606de5924f117189 drm/i915/error: improve CSB reporting
> 7c5e4382756f0fc89ca8b7209861ac73f2059eef drm/i915/error: report ctx id & desc for each request in the queue
> 64d800fceb8ddc6f1e431ea09c674077db359c9b drm/i915/error: capture ringbuffer pointed to by START
> 8398e7f4626cc0353d2d9d57c5fe2accf734612f drm/i915/error: capture execlist state on error
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-02-29 10:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 15:50 [PATCH v2 0/9] Capture more useful details in error state Arun Siluvery
2016-02-10 15:50 ` [PATCH v2 1/9] drm/i915/error: capture execlist state on error Arun Siluvery
2016-02-10 15:50 ` [PATCH v2 2/9] drm/i915/error: capture ringbuffer pointed to by START Arun Siluvery
2016-02-10 15:50 ` [PATCH v2 3/9] drm/i915/error: report ctx id & desc for each request in the queue Arun Siluvery
2016-02-10 15:50 ` [PATCH v2 4/9] drm/i915/error: improve CSB reporting Arun Siluvery
2016-02-10 15:50 ` [PATCH v2 5/9] drm/i915/error: capture errored context based on request context-id Arun Siluvery
2016-02-10 15:50 ` [PATCH v2 6/9] drm/i915/error: enhanced error capture of requests Arun Siluvery
2016-02-10 15:50 ` [PATCH v2 7/9] drm/i915/guc: Improve action error reporting Arun Siluvery
2016-02-10 15:50 ` [PATCH v2 8/9] drm/i915/error: add GuC state error capture & decode Arun Siluvery
2016-02-10 15:50 ` [PATCH v2 9/9] drm/i915/error: Capture WA ctx batch in error state Arun Siluvery
2016-02-26 14:53 ` Mika Kuoppala
2016-02-26 15:35 ` Chris Wilson
2016-02-26 16:06 ` [PATCH v3 " Arun Siluvery
2016-03-01 10:34 ` Tvrtko Ursulin
2016-02-15 13:52 ` ✗ Fi.CI.BAT: failure for Capture more useful details in error state (rev2) Patchwork
2016-02-26 16:27 ` ✗ Fi.CI.BAT: warning for Capture more useful details in error state (rev3) Patchwork
2016-02-26 17:01 ` ✗ Fi.CI.BAT: failure " Patchwork
2016-02-29 10:32 ` Arun Siluvery [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=56D41E2C.8040608@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 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.