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 [1/3] drm/i915/gt: Cancel submitted requests upon context reset (rev2)
Date: Sat, 26 Dec 2020 00:06:36 -0000 [thread overview]
Message-ID: <160894119632.24395.8571298437875591705@emeril.freedesktop.org> (raw)
In-Reply-To: <20201225204938.20248-1-chris@chris-wilson.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 4063 bytes --]
== Series Details ==
Series: series starting with [1/3] drm/i915/gt: Cancel submitted requests upon context reset (rev2)
URL : https://patchwork.freedesktop.org/series/85238/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9527 -> Patchwork_19217
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_19217 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_19217, 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_19217/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_19217:
### IGT changes ###
#### Possible regressions ####
* igt@kms_chamelium@hdmi-crc-fast:
- fi-kbl-7500u: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9527/fi-kbl-7500u/igt@kms_chamelium@hdmi-crc-fast.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19217/fi-kbl-7500u/igt@kms_chamelium@hdmi-crc-fast.html
Known issues
------------
Here are the changes found in Patchwork_19217 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [PASS][3] -> [DMESG-FAIL][4] ([i915#165])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9527/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19217/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
* igt@runner@aborted:
- fi-bdw-5557u: NOTRUN -> [FAIL][5] ([i915#2029])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19217/fi-bdw-5557u/igt@runner@aborted.html
* igt@vgem_basic@setversion:
- fi-tgl-y: [PASS][6] -> [DMESG-WARN][7] ([i915#402]) +1 similar issue
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9527/fi-tgl-y/igt@vgem_basic@setversion.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19217/fi-tgl-y/igt@vgem_basic@setversion.html
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s3:
- fi-tgl-y: [DMESG-WARN][8] ([i915#2411] / [i915#402]) -> [PASS][9]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9527/fi-tgl-y/igt@gem_exec_suspend@basic-s3.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19217/fi-tgl-y/igt@gem_exec_suspend@basic-s3.html
* igt@vgem_basic@create:
- fi-tgl-y: [DMESG-WARN][10] ([i915#402]) -> [PASS][11] +1 similar issue
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9527/fi-tgl-y/igt@vgem_basic@create.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19217/fi-tgl-y/igt@vgem_basic@create.html
[i915#165]: https://gitlab.freedesktop.org/drm/intel/issues/165
[i915#2029]: https://gitlab.freedesktop.org/drm/intel/issues/2029
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
Participating hosts (40 -> 38)
------------------------------
Missing (2): fi-bsw-cyan fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_9527 -> Patchwork_19217
CI-20190529: 20190529
CI_DRM_9527: 5f4ab60f910567453058c32e806ed10cc72cd8d7 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5922: 334f0c326bb2812e7a2764dc63ff83c83b6daf58 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_19217: 4b5df9a7f3a9ad5b2f4454ccc19e86aa4c8a8595 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
4b5df9a7f3a9 drm/i915/gem: Peek at the inflight context
bb38680d5740 drm/i915/gt: Pull context closure check from request submit to schedule-in
7828a509e7de drm/i915/gt: Cancel submitted requests upon context reset
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19217/index.html
[-- Attachment #1.2: Type: text/html, Size: 4967 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:[~2020-12-26 0:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 20:49 [Intel-gfx] [PATCH 1/3] drm/i915/gt: Cancel submitted requests upon context reset Chris Wilson
2020-12-25 20:49 ` [Intel-gfx] [PATCH 2/3] drm/i915/gt: Pull context closure check from request submit to schedule-in Chris Wilson
2020-12-25 20:49 ` [Intel-gfx] [PATCH 3/3] drm/i915/gem: Peek at the inflight context Chris Wilson
2020-12-25 22:24 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/3] drm/i915/gt: Cancel submitted requests upon context reset Patchwork
2020-12-26 0:06 ` 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=160894119632.24395.8571298437875591705@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 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.