From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Chris Wilson" <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [CI,1/6] drm/i915/gt: One more flush for Baytrail clear residuals
Date: Tue, 19 Jan 2021 16:30:23 -0000 [thread overview]
Message-ID: <161107382347.4868.8350510191574997372@emeril.freedesktop.org> (raw)
In-Reply-To: <20210119110802.22228-1-chris@chris-wilson.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 5609 bytes --]
== Series Details ==
Series: series starting with [CI,1/6] drm/i915/gt: One more flush for Baytrail clear residuals
URL : https://patchwork.freedesktop.org/series/86038/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9643 -> Patchwork_19406
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_19406 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_19406, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19406/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_19406:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live@hangcheck:
- fi-byt-j1900: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9643/fi-byt-j1900/igt@i915_selftest@live@hangcheck.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19406/fi-byt-j1900/igt@i915_selftest@live@hangcheck.html
Known issues
------------
Here are the changes found in Patchwork_19406 that come from known issues:
### CI changes ###
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_basic@query-info:
- fi-tgl-y: NOTRUN -> [SKIP][3] ([fdo#109315] / [i915#2575])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19406/fi-tgl-y/igt@amdgpu/amd_basic@query-info.html
* igt@prime_self_import@basic-with_two_bos:
- fi-tgl-y: [PASS][4] -> [DMESG-WARN][5] ([i915#402]) +1 similar issue
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9643/fi-tgl-y/igt@prime_self_import@basic-with_two_bos.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19406/fi-tgl-y/igt@prime_self_import@basic-with_two_bos.html
* igt@runner@aborted:
- fi-bdw-5557u: NOTRUN -> [FAIL][6] ([i915#1602] / [i915#2029] / [i915#2369])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19406/fi-bdw-5557u/igt@runner@aborted.html
#### Possible fixes ####
* igt@debugfs_test@read_all_entries:
- fi-tgl-y: [DMESG-WARN][7] ([i915#402]) -> [PASS][8] +2 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9643/fi-tgl-y/igt@debugfs_test@read_all_entries.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19406/fi-tgl-y/igt@debugfs_test@read_all_entries.html
* igt@i915_selftest@live@active:
- fi-skl-6600u: [DMESG-FAIL][9] ([i915#2291] / [i915#666]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9643/fi-skl-6600u/igt@i915_selftest@live@active.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19406/fi-skl-6600u/igt@i915_selftest@live@active.html
* igt@i915_selftest@live@gem_contexts:
- fi-byt-j1900: [DMESG-FAIL][11] -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9643/fi-byt-j1900/igt@i915_selftest@live@gem_contexts.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19406/fi-byt-j1900/igt@i915_selftest@live@gem_contexts.html
* igt@kms_frontbuffer_tracking@basic:
- fi-byt-j1900: [FAIL][13] ([i915#49]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9643/fi-byt-j1900/igt@kms_frontbuffer_tracking@basic.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19406/fi-byt-j1900/igt@kms_frontbuffer_tracking@basic.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[i915#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602
[i915#2029]: https://gitlab.freedesktop.org/drm/intel/issues/2029
[i915#2291]: https://gitlab.freedesktop.org/drm/intel/issues/2291
[i915#2369]: https://gitlab.freedesktop.org/drm/intel/issues/2369
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#2788]: https://gitlab.freedesktop.org/drm/intel/issues/2788
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#666]: https://gitlab.freedesktop.org/drm/intel/issues/666
Participating hosts (42 -> 38)
------------------------------
Additional (1): fi-dg1-1
Missing (5): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_9643 -> Patchwork_19406
CI-20190529: 20190529
CI_DRM_9643: fabbcd086b7f667f0e0cce8eeb26a7b5c7120782 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5960: ace82fcd5f3623f8dde7c220a825873dc53dfae4 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_19406: 26eb26a138f226f5971ba409b69f955f6c13522e @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
26eb26a138f2 drm/i915: Mark per-engine-reset as supported on gen7
cb08fa27de73 drm/i915/gt: Pull ring submission resume under its caller forcewake
137589ac3686 drm/i915/gt: Disable the ring before resetting HEAD/TAIL
303411fd741b drm/i915/gt: Lift stop_ring() to reset_prepare
86ee1d591ead drm/i915/selftests: Prepare the selftests for engine resets with ring submission
e319afa9a845 drm/i915/gt: One more flush for Baytrail clear residuals
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19406/index.html
[-- Attachment #1.2: Type: text/html, Size: 6457 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2021-01-19 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 11:07 [Intel-gfx] [CI 1/6] drm/i915/gt: One more flush for Baytrail clear residuals Chris Wilson
2021-01-19 11:07 ` [Intel-gfx] [CI 2/6] drm/i915/selftests: Prepare the selftests for engine resets with ring submission Chris Wilson
2021-01-19 11:07 ` [Intel-gfx] [CI 3/6] drm/i915/gt: Lift stop_ring() to reset_prepare Chris Wilson
2021-01-19 11:08 ` [Intel-gfx] [CI 4/6] drm/i915/gt: Disable the ring before resetting HEAD/TAIL Chris Wilson
2021-01-19 11:08 ` Mika Kuoppala
2021-01-19 11:08 ` [Intel-gfx] [CI 5/6] drm/i915/gt: Pull ring submission resume under its caller forcewake Chris Wilson
2021-01-19 11:08 ` [Intel-gfx] [CI 6/6] drm/i915: Mark per-engine-reset as supported on gen7 Chris Wilson
2021-01-19 16:00 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/6] drm/i915/gt: One more flush for Baytrail clear residuals Patchwork
2021-01-19 16:30 ` Patchwork [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=161107382347.4868.8350510191574997372@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;
as well as URLs for NNTP newsgroup(s).