✗ Fi.CI.BAT: failure for series starting with [01/31] drm/i915: Verify the engine after acquiring the active.lock
Patchwork
patchwork at emeril.freedesktop.org
Tue Sep 17 18:57:55 UTC 2019
== Series Details ==
Series: series starting with [01/31] drm/i915: Verify the engine after acquiring the active.lock
URL : https://patchwork.freedesktop.org/series/66823/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6911 -> Trybot_5034
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Trybot_5034 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Trybot_5034, 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/Trybot_5034/
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Trybot_5034:
### IGT changes ###
#### Possible regressions ####
* igt at i915_selftest@live_hangcheck:
- fi-hsw-4770r: [PASS][1] -> [DMESG-FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6911/fi-hsw-4770r/igt@i915_selftest@live_hangcheck.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5034/fi-hsw-4770r/igt@i915_selftest@live_hangcheck.html
New tests
---------
New tests have been introduced between CI_DRM_6911 and Trybot_5034:
### New IGT tests (1) ###
* igt at i915_selftest@live_gt_lrc:
- Statuses : 43 pass(s)
- Exec time: [0.38, 2.06] s
Known issues
------------
Here are the changes found in Trybot_5034 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt at gem_exec_suspend@basic-s4-devices:
- fi-blb-e6850: [PASS][3] -> [INCOMPLETE][4] ([fdo#107718])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6911/fi-blb-e6850/igt@gem_exec_suspend@basic-s4-devices.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5034/fi-blb-e6850/igt@gem_exec_suspend@basic-s4-devices.html
* igt at gem_mmap@basic:
- fi-icl-u3: [PASS][5] -> [DMESG-WARN][6] ([fdo#107724]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6911/fi-icl-u3/igt@gem_mmap@basic.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5034/fi-icl-u3/igt@gem_mmap@basic.html
* igt at i915_module_load@reload:
- fi-icl-u3: [PASS][7] -> [DMESG-WARN][8] ([fdo#107724] / [fdo#111214])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6911/fi-icl-u3/igt@i915_module_load@reload.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5034/fi-icl-u3/igt@i915_module_load@reload.html
* igt at kms_frontbuffer_tracking@basic:
- fi-icl-u2: [PASS][9] -> [FAIL][10] ([fdo#103167])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6911/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5034/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html
#### Possible fixes ####
* igt at gem_exec_gttfill@basic:
- fi-apl-guc: [DMESG-WARN][11] ([fdo#109385] / [fdo#111652 ]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6911/fi-apl-guc/igt@gem_exec_gttfill@basic.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5034/fi-apl-guc/igt@gem_exec_gttfill@basic.html
* igt at gem_mmap_gtt@basic-write-no-prefault:
- fi-icl-u3: [DMESG-WARN][13] ([fdo#107724]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6911/fi-icl-u3/igt@gem_mmap_gtt@basic-write-no-prefault.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5034/fi-icl-u3/igt@gem_mmap_gtt@basic-write-no-prefault.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#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602
[fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#109385]: https://bugs.freedesktop.org/show_bug.cgi?id=109385
[fdo#111045]: https://bugs.freedesktop.org/show_bug.cgi?id=111045
[fdo#111214]: https://bugs.freedesktop.org/show_bug.cgi?id=111214
[fdo#111562]: https://bugs.freedesktop.org/show_bug.cgi?id=111562
[fdo#111597]: https://bugs.freedesktop.org/show_bug.cgi?id=111597
[fdo#111652 ]: https://bugs.freedesktop.org/show_bug.cgi?id=111652
Participating hosts (54 -> 46)
------------------------------
Missing (8): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-icl-y fi-icl-dsi fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_6911 -> Trybot_5034
CI-20190529: 20190529
CI_DRM_6911: 2e04def5afc3b2bd724dc6f3f6525c5ebf1f87d2 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5189: c78b9959fa4050725b16d55a5e56315884a2753d @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Trybot_5034: 7cf84303f53fbfbd5edc66369a64dbc94d1064a2 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
7cf84303f53f drm/i915: Drop struct_mutex from around GEM initialisation
4891dbe4c664 drm/i915/selftests: Drop vestigal struct_mutex guards
8de4b018d149 drm/i915: Drop struct_mutex from suspend state save/restore
14e5db212735 drm/i915: Remove struct_mutex guard for debugfs/opregion
6d0adb5c95aa drm/i915: Drop struct_mutex guard from debugfs/framebuffer_info
89e73d8356f1 drm/i915/overlay: Drop struct_mutex guard
603a095fa8a2 drm/i915: Move context management under GEM
0a80e575224b drm/i915: Remove logical HW ID
5c4b469a6b7d drm/i915: Replace hangcheck by heartbeats
d6666919ec2d drm/i915: Cancel non-persistent contexts on close
9f6d93ff6298 drm/i915/execlists: Cancel banned contexts on schedule-out
8c399172404b drm/i915: Mark up "sentinel" requests
fd94a78ec7d5 drm/i915/execlists: Force preemption
d51e86b1dee6 drm/i915: Only enqueue already completed requests
61e852eb8677 drm/i915/execlists: Always request completion before marking an error
d109988d8788 drm/i915: Move global activity tracking from GEM to GT
3dbe9e225b81 drm/i915: Move request runtime management onto gt
b4803b369527 drm/i915: Merge wait_for_timelines with retire_request
40655cfe0075 drm/i915: Remove the GEM idle worker
09c6e4eb4d7c drm/i915: Drop struct_mutex from around i915_retire_requests()
23cdbb862b7c drm/i915: Move idle barrier cleanup into engine-pm
26fb0254cb8a drm/i915: Coordinate i915_active with its own mutex
2e5670ff3d4b drm/i915: Push the i915_active.retire into a worker
e689904c44fa drm/i915: Pull i915_vma_pin under the vm->mutex
09f8f9989322 drm/i915: Mark up address spaces that may need to allocate
518152b25f23 drm/i915: Only track bound elements of the GTT
8273e122dd04 drm/mm: Pack allocated/scanned boolean into a bitfield
84d5ed6f7487 dma-fence: Serialise signal enabling (dma_fence_enable_sw_signaling)
2a17a72ef62a drm/i915/selftests: Verify the LRC register layout between init and HW
a4262e6aff86 drm/i915: Lock signaler timeline while navigating
504d30214b6f drm/i915: Verify the engine after acquiring the active.lock
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5034/index.html
More information about the Intel-gfx-trybot
mailing list