From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for series starting with [01/10] drm/i915: Use 0 for the unordered context
Date: Mon, 19 Aug 2019 17:23:51 -0000 [thread overview]
Message-ID: <20190819172351.21819.24977@emeril.freedesktop.org> (raw)
In-Reply-To: <20190819164448.22132-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [01/10] drm/i915: Use 0 for the unordered context
URL : https://patchwork.freedesktop.org/series/65426/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6737 -> Patchwork_14082
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_14082 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_14082, 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_14082/
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_14082:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live_gem_contexts:
- fi-byt-j1900: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-byt-j1900/igt@i915_selftest@live_gem_contexts.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-byt-j1900/igt@i915_selftest@live_gem_contexts.html
- fi-ivb-3770: [PASS][3] -> [DMESG-WARN][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-ivb-3770/igt@i915_selftest@live_gem_contexts.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-ivb-3770/igt@i915_selftest@live_gem_contexts.html
- fi-hsw-4770: [PASS][5] -> [DMESG-WARN][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-hsw-4770/igt@i915_selftest@live_gem_contexts.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-hsw-4770/igt@i915_selftest@live_gem_contexts.html
- fi-hsw-peppy: [PASS][7] -> [DMESG-WARN][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-hsw-peppy/igt@i915_selftest@live_gem_contexts.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-hsw-peppy/igt@i915_selftest@live_gem_contexts.html
- fi-hsw-4770r: [PASS][9] -> [DMESG-WARN][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-hsw-4770r/igt@i915_selftest@live_gem_contexts.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-hsw-4770r/igt@i915_selftest@live_gem_contexts.html
- fi-byt-n2820: [PASS][11] -> [DMESG-WARN][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-byt-n2820/igt@i915_selftest@live_gem_contexts.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-byt-n2820/igt@i915_selftest@live_gem_contexts.html
#### Warnings ####
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][13] ([fdo#111407]) -> [FAIL][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
Known issues
------------
Here are the changes found in Patchwork_14082 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_flink_basic@double-flink:
- fi-icl-u3: [PASS][15] -> [DMESG-WARN][16] ([fdo#107724])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-icl-u3/igt@gem_flink_basic@double-flink.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-icl-u3/igt@gem_flink_basic@double-flink.html
* igt@kms_chamelium@dp-crc-fast:
- fi-cml-u2: [PASS][17] -> [FAIL][18] ([fdo#110627])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-cml-u2/igt@kms_chamelium@dp-crc-fast.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-cml-u2/igt@kms_chamelium@dp-crc-fast.html
* igt@kms_frontbuffer_tracking@basic:
- fi-bxt-j4205: [PASS][19] -> [FAIL][20] ([fdo#103167])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-bxt-j4205/igt@kms_frontbuffer_tracking@basic.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-bxt-j4205/igt@kms_frontbuffer_tracking@basic.html
- fi-bsw-kefka: [PASS][21] -> [FAIL][22] ([fdo#103167])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-bsw-kefka/igt@kms_frontbuffer_tracking@basic.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-bsw-kefka/igt@kms_frontbuffer_tracking@basic.html
- fi-bxt-dsi: [PASS][23] -> [FAIL][24] ([fdo#103167])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-bxt-dsi/igt@kms_frontbuffer_tracking@basic.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-bxt-dsi/igt@kms_frontbuffer_tracking@basic.html
- fi-apl-guc: [PASS][25] -> [FAIL][26] ([fdo#103167])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-apl-guc/igt@kms_frontbuffer_tracking@basic.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-apl-guc/igt@kms_frontbuffer_tracking@basic.html
- fi-byt-j1900: [PASS][27] -> [FAIL][28] ([fdo#103167])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-byt-j1900/igt@kms_frontbuffer_tracking@basic.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-byt-j1900/igt@kms_frontbuffer_tracking@basic.html
- fi-ilk-650: [PASS][29] -> [FAIL][30] ([fdo#103167])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-ilk-650/igt@kms_frontbuffer_tracking@basic.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-ilk-650/igt@kms_frontbuffer_tracking@basic.html
- fi-byt-n2820: [PASS][31] -> [FAIL][32] ([fdo#103167])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-byt-n2820/igt@kms_frontbuffer_tracking@basic.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-byt-n2820/igt@kms_frontbuffer_tracking@basic.html
- fi-bdw-gvtdvm: [PASS][33] -> [FAIL][34] ([fdo#103167])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-bdw-gvtdvm/igt@kms_frontbuffer_tracking@basic.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-bdw-gvtdvm/igt@kms_frontbuffer_tracking@basic.html
- fi-glk-dsi: [PASS][35] -> [FAIL][36] ([fdo#103167])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-glk-dsi/igt@kms_frontbuffer_tracking@basic.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-glk-dsi/igt@kms_frontbuffer_tracking@basic.html
- fi-skl-gvtdvm: [PASS][37] -> [FAIL][38] ([fdo#103167])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-skl-gvtdvm/igt@kms_frontbuffer_tracking@basic.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-skl-gvtdvm/igt@kms_frontbuffer_tracking@basic.html
#### Possible fixes ####
* igt@kms_frontbuffer_tracking@basic:
- fi-icl-u3: [FAIL][39] ([fdo#103167]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-icl-u3/igt@kms_frontbuffer_tracking@basic.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-icl-u3/igt@kms_frontbuffer_tracking@basic.html
- fi-icl-u2: [FAIL][41] ([fdo#103167]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6737/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/fi-icl-u2/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#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#110627]: https://bugs.freedesktop.org/show_bug.cgi?id=110627
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
Participating hosts (55 -> 46)
------------------------------
Missing (9): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-bsw-n3050 fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_6737 -> Patchwork_14082
CI-20190529: 20190529
CI_DRM_6737: 7c1b750b342c7ded6d590589393a40590e0bb7ab @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5141: 7102b417fedc2a1ea6f72d768a9f1bd100a34f13 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_14082: 295f8efb617d41eea2d749d8d3fcdbb13d415014 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
295f8efb617d drm/i915: Be defensive when starting vma activity
5b7dd0fb5eb9 drm/i915: Make shrink/unshrink be atomic
d0405a9011ab drm/i915: Replace i915_vma_put_fence()
965f4453c69e drm/i915: Pull obj->userfault tracking under the ggtt->mutex
82f065549179 drm/i915: Only track bound elements of the GTT
e6cace67721a drm/i915: Track ggtt fence reservations under its own mutex
dc8c79266acb drm/i915: Replace PIN_NONFAULT with calls to PIN_NOEVICT
f9ed69ac9f3b drm/i915: Assume exclusive access to objects inside resume
18f8647117cd drm/i915: Generalise the clflush dma-worker
f3745550c94b drm/i915: Use 0 for the unordered context
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14082/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-19 17:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 16:44 [PATCH 01/10] drm/i915: Use 0 for the unordered context Chris Wilson
2019-08-19 16:44 ` [PATCH 02/10] drm/i915: Generalise the clflush dma-worker Chris Wilson
2019-08-19 18:16 ` Matthew Auld
2019-08-19 18:32 ` Chris Wilson
2019-08-19 16:44 ` [PATCH 03/10] drm/i915: Assume exclusive access to objects inside resume Chris Wilson
2019-08-19 19:57 ` Matthew Auld
2019-08-19 16:44 ` [PATCH 04/10] drm/i915: Replace PIN_NONFAULT with calls to PIN_NOEVICT Chris Wilson
2019-08-19 16:44 ` [PATCH 05/10] drm/i915: Track ggtt fence reservations under its own mutex Chris Wilson
2019-08-19 16:44 ` [PATCH 06/10] drm/i915: Only track bound elements of the GTT Chris Wilson
2019-08-19 16:44 ` [PATCH 07/10] drm/i915: Pull obj->userfault tracking under the ggtt->mutex Chris Wilson
2019-08-19 16:44 ` [PATCH 08/10] drm/i915: Replace i915_vma_put_fence() Chris Wilson
2019-08-19 16:44 ` [PATCH 09/10] drm/i915: Make shrink/unshrink be atomic Chris Wilson
2019-08-19 16:44 ` [PATCH 10/10] drm/i915: Be defensive when starting vma activity Chris Wilson
2019-08-19 17:00 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/10] drm/i915: Use 0 for the unordered context Patchwork
2019-08-19 17:23 ` Patchwork [this message]
2019-08-19 17:29 ` ✗ Fi.CI.BAT: failure " Chris Wilson
2019-08-19 17:36 ` [PATCH 01/10] " Matthew Auld
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=20190819172351.21819.24977@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.