From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.IGT: failure for series starting with [01/11] drm/i915: Revoke mmaps and prevent access to fence registers across reset
Date: Wed, 30 Jan 2019 07:32:25 -0000 [thread overview]
Message-ID: <20190130073225.28911.93259@emeril.freedesktop.org> (raw)
In-Reply-To: <20190130021906.17933-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [01/11] drm/i915: Revoke mmaps and prevent access to fence registers across reset
URL : https://patchwork.freedesktop.org/series/55956/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5506_full -> Patchwork_12083_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_12083_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_12083_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_12083_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_eio@unwedge-stress:
- shard-glk: PASS -> FAIL +6
- shard-snb: PASS -> FAIL +1
- shard-apl: PASS -> FAIL +1
* igt@gem_eio@wait-wedge-1us:
- shard-kbl: PASS -> FAIL +1
Known issues
------------
Here are the changes found in Patchwork_12083_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_eio@in-flight-contexts-10ms:
- shard-snb: PASS -> FAIL [fdo#107799] +6
* igt@kms_cursor_crc@cursor-256x256-random:
- shard-glk: PASS -> FAIL [fdo#103232] +1
* igt@kms_cursor_crc@cursor-256x85-random:
- shard-apl: PASS -> FAIL [fdo#103232] +4
* igt@kms_flip@flip-vs-expired-vblank:
- shard-glk: PASS -> FAIL [fdo#105363]
* igt@kms_plane@plane-position-covered-pipe-c-planes:
- shard-apl: PASS -> FAIL [fdo#103166]
* igt@kms_plane_multiple@atomic-pipe-c-tiling-x:
- shard-glk: PASS -> FAIL [fdo#103166]
* igt@kms_setmode@basic:
- shard-kbl: PASS -> FAIL [fdo#99912]
* igt@perf_pmu@rc6-runtime-pm-long:
- shard-kbl: PASS -> FAIL [fdo#105010]
#### Possible fixes ####
* igt@gem_mmap_gtt@hang:
- shard-kbl: FAIL [fdo#109469] -> PASS
- shard-hsw: FAIL [fdo#109469] -> PASS
- shard-snb: FAIL [fdo#109469] -> PASS
- shard-glk: FAIL [fdo#109469] -> PASS
- shard-apl: FAIL [fdo#109469] -> PASS
* igt@kms_cursor_crc@cursor-256x256-suspend:
- shard-apl: FAIL [fdo#103191] / [fdo#103232] -> PASS
* igt@kms_cursor_crc@cursor-64x21-onscreen:
- shard-glk: FAIL [fdo#103232] -> PASS
* igt@kms_cursor_crc@cursor-64x64-dpms:
- shard-apl: FAIL [fdo#103232] -> PASS
* igt@kms_cursor_crc@cursor-64x64-suspend:
- shard-snb: INCOMPLETE [fdo#105411] -> PASS
* igt@kms_plane@pixel-format-pipe-c-planes-source-clamping:
- shard-apl: FAIL [fdo#108948] -> PASS
* igt@kms_plane_multiple@atomic-pipe-b-tiling-none:
- shard-glk: FAIL [fdo#103166] -> PASS +1
- shard-apl: FAIL [fdo#103166] -> PASS +1
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166
[fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
[fdo#103232]: https://bugs.freedesktop.org/show_bug.cgi?id=103232
[fdo#105010]: https://bugs.freedesktop.org/show_bug.cgi?id=105010
[fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363
[fdo#105411]: https://bugs.freedesktop.org/show_bug.cgi?id=105411
[fdo#107799]: https://bugs.freedesktop.org/show_bug.cgi?id=107799
[fdo#108948]: https://bugs.freedesktop.org/show_bug.cgi?id=108948
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109469]: https://bugs.freedesktop.org/show_bug.cgi?id=109469
[fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912
Participating hosts (7 -> 5)
------------------------------
Missing (2): shard-skl shard-iclb
Build changes
-------------
* Linux: CI_DRM_5506 -> Patchwork_12083
CI_DRM_5506: 864d26b6a3e3b28515324f330b2240391f86f458 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4798: 998e0a4aedf10fb5f7c271018cd80d874668bf55 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_12083: 3a880e78d53731890ab3f0d64afef8c217a8c52c @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12083/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-01-30 7:32 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 2:18 [PATCH 01/11] drm/i915: Revoke mmaps and prevent access to fence registers across reset Chris Wilson
2019-01-30 2:18 ` [PATCH 02/11] drm/i915/execlists: Suppress redundant preemption Chris Wilson
2019-01-30 2:18 ` [PATCH 03/11] drm/i915/selftests: Exercise some AB...BA preemption chains Chris Wilson
2019-01-30 2:18 ` [PATCH 04/11] drm/i915: Generalise GPU activity tracking Chris Wilson
2019-01-30 12:02 ` Tvrtko Ursulin
2019-01-30 12:14 ` Chris Wilson
2019-01-30 2:19 ` [PATCH 05/11] drm/i915: Add timeline barrier support Chris Wilson
2019-01-30 2:19 ` [PATCH 06/11] drm/i915: Allocate active tracking nodes from a slabcache Chris Wilson
2019-01-30 15:57 ` Tvrtko Ursulin
2019-01-30 16:08 ` Chris Wilson
2019-01-30 21:58 ` Chris Wilson
2019-01-30 16:37 ` [PATCH v2] " Chris Wilson
2019-01-30 16:47 ` Chris Wilson
2019-01-30 17:25 ` [PATCH v3] " Chris Wilson
2019-01-30 2:19 ` [PATCH 07/11] drm/i915: Pull i915_gem_active into the i915_active family Chris Wilson
2019-01-30 16:11 ` Tvrtko Ursulin
2019-01-30 2:19 ` [PATCH 08/11] drm/i915: Keep timeline HWSP allocated until the system is idle Chris Wilson
2019-01-30 17:54 ` Tvrtko Ursulin
2019-01-30 18:25 ` Chris Wilson
2019-01-30 2:19 ` [PATCH 09/11] drm/i915/execlists: Refactor out can_merge_rq() Chris Wilson
2019-01-30 18:05 ` Tvrtko Ursulin
2019-01-30 18:14 ` Chris Wilson
2019-01-31 9:19 ` Tvrtko Ursulin
2019-01-31 9:30 ` Chris Wilson
2019-01-31 9:36 ` Chris Wilson
2019-01-30 2:19 ` [PATCH 10/11] drm/i915: Use HW semaphores for inter-engine synchronisation on gen8+ Chris Wilson
2019-01-31 13:19 ` Tvrtko Ursulin
2019-01-31 13:39 ` Chris Wilson
2019-01-31 16:20 ` Chris Wilson
2019-02-01 9:03 ` Chris Wilson
2019-01-31 17:21 ` Chris Wilson
2019-01-30 2:19 ` [PATCH 11/11] drm/i915: Prioritise non-busywait semaphore workloads Chris Wilson
2019-01-30 2:43 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/11] drm/i915: Revoke mmaps and prevent access to fence registers across reset Patchwork
2019-01-30 2:48 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-30 3:07 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-30 7:32 ` Patchwork [this message]
2019-01-30 9:17 ` ✗ Fi.CI.IGT: failure " Chris Wilson
2019-01-30 18:41 ` ✗ Fi.CI.BAT: failure for series starting with [01/11] drm/i915: Revoke mmaps and prevent access to fence registers across reset (rev3) 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=20190130073225.28911.93259@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--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