Security mitigation for Intel Gen7 HWs
Subsystems (2)
v3 cover Security mitigation for Intel Gen7 HWs
**** NOTE: ****
This series is in active development and is not intended to be merged to mainline in its current form. The intent of the RFC is simply to outline the strategy for the mitigation, as a focus for active discussion, and to openly share progress. There has been only minimal attention paid to performance thus far, as the focus is on robustness. It is not anticipated that there will be any measurable performance impact in the final version.
**** END NOTE ****
Intel ID: PSIRT-TA-201910-001
CVEID: CVE-2019-14615
Summary of Vulnerability
------------------------
Insufficient control flow in certain data structures for some Intel(R) Processors with Intel Processor Graphics may allow an unauthenticated user to potentially enable information disclosure via local access
Products affected:
------------------
Intel CPU’s with Gen7, Gen7.5 and Gen9 Graphics.
Mitigation Summary
------------------
This patch provides mitigation for Gen7 and Gen7.5 hardware only. Patch for Gen9 devices have been provided and merged to Linux mainline, and backported to stable kernels.
Note that Gen8 is not impacted due to a previously implemented workaround.
The mitigation involves submitting a custom EU kernel prior to every context restore, in order to forcibly clear down residual EU and URB resources.
This is currently an RFC while more analysis is performed on the performance implications.
Note on Address Space Isolation (Full PPGTT)
--------------------------------------------
Isolation of EU kernel assets should be considered complementary to the existing support for address space isolation (aka Full PPGTT), since without address space isolation there is minimal value in preventing leakage between EU contexts. Full PPGTT has long been supported on Gen Gfx devices since Gen8, and protection against EU residual leakage is a welcome addition for these newer platforms.
By contrast, Gen7 and Gen7.5 device introduced Full PPGTT support only as a hardware development feature for anticipated Gen8 productization. Support was never intended for, or provided to the Linux kernels for these platforms. Recent work (still ongoing) to the mainline kernel is retroactively providing this support, but due to the level of complexity it is not practical to attempt to backport this to earlier stable kernels. Since without Full PPGTT, EU residuals protection has questionable benefit, *there are no plans to provide stable kernel backports for this patch series.*
Mika Kuoppala (1):
drm/i915: Add mechanism to submit a context WA on ring submission
Prathap Kumar Valsan (1):
drm/i915/gen7: Clear all EU/L3 residual contexts
drivers/gpu/drm/i915/Makefile | 1 + drivers/gpu/drm/i915/gt/gen7_renderclear.c | 524 ++++++++++++++++++ drivers/gpu/drm/i915/gt/gen7_renderclear.h | 15 + drivers/gpu/drm/i915/gt/intel_gpu_commands.h | 17 +- .../gpu/drm/i915/gt/intel_ring_submission.c | 133 ++++- drivers/gpu/drm/i915/i915_utils.h | 5 + 6 files changed, 689 insertions(+), 6 deletions(-) create mode 100644 drivers/gpu/drm/i915/gt/gen7_renderclear.c create mode 100644 drivers/gpu/drm/i915/gt/gen7_renderclear.h
Signature · 6 lines
2.20.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
RFC PATCH v3 1/2 drm/i915: Add mechanism to submit a context WA on ring submission
From: Mika Kuoppala <[email protected]>
**** NOTE: ****
This series is in active development and is not intended to be merged to mainline in its current form. The intent of the RFC is simply to outline the strategy for the mitigation, as a focus for active discussion, and to openly share progress. There has been only minimal attention paid to performance thus far, as the focus is on robustness. It is not anticipated that there will be any measurable performance impact in the final version.
**** END NOTE ****
This patch adds framework to submit an arbitrary batchbuffer on each context switch to clear residual state for render engine on Gen7/7.5 devices.
The idea of always emitting the context and vm setup around each request is primary to make reset recovery easy, and not require rewriting the ringbuffer. As each request would set up its own context, leaving it to the HW to notice and elide no-op context switches, we could restart the ring at any point, and reorder the requests freely.
However, to avoid emitting clear_residuals() between consecutive requests in the ringbuffer of the same context, we do want to track the current context in the ring. In doing so, we need to be careful to only record a context switch when we are sure the next request will be emitted.
v2: No change
v3: elide optimization patch squashed, courtesy of Chris Wilson - the changes show significant performance improvements, on par with current drm-tips.
--- .../gpu/drm/i915/gt/intel_ring_submission.c | 132 +++++++++++++++++- 1 file changed, 129 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/gt/intel_ring_submission.c +129 -3
@@ -1384,7 +1384,9 @@ static int load_pd_dir(struct i915_request *rq,return rq->engine->emit_flush (rq,EMIT_FLUSH ); } -static inline int mi_set_context (struct i915_request *rq,u32 flags) +static inline int mi_set_context (struct i915_request *rq, +struct intel_context *ce, +u32 flags) {struct drm_i915_private *i915 = rq->i915;struct intel_engine_cs *engine = rq->engine;
@@ -1459,7 +1461,7 @@ static inline int mi_set_context(struct i915_request *rq, u32 flags) *cs++ =MI_NOOP ; *cs++ =MI_SET_CONTEXT ; - *cs++ =i915_ggtt_offset (rq->context->state) | flags; + *cs++ =i915_ggtt_offset (ce->state) | flags;/* * w/a: MI_SET_CONTEXT must always be followed by MI_NOOP * WaMiSetContext_Hang:snb,ivb,vlv
@@ -1574,13 +1576,56 @@ static int switch_mm(struct i915_request *rq, struct i915_address_space *vm)return rq->engine->emit_flush (rq,EMIT_INVALIDATE ); } +static int clear_residuals (struct i915_request *rq) +{ +struct intel_engine_cs *engine = rq->engine; +int ret; + +GEM_BUG_ON (!engine->kernel_context->state); + + ret =switch_mm (rq,vm_alias (engine->kernel_context)); +if (ret) +return ret; + + ret =mi_set_context (rq, + engine->kernel_context, +MI_MM_SPACE_GTT |MI_RESTORE_INHIBIT ); +if (ret) +return ret; + + ret = engine->emit_bb_start (rq, + engine->wa_ctx.vma->node.start,0 , +0 ); +if (ret) +return ret; + + ret = engine->emit_flush (rq,EMIT_FLUSH ); +if (ret) +return ret; + +/* Always invalidate before the next switch_mm() */ +return engine->emit_flush (rq,EMIT_INVALIDATE ); +} +static int switch_context (struct i915_request *rq) { +struct intel_engine_cs *engine = rq->engine;struct intel_context *ce = rq->context; +void **residuals =NULL ;int ret;GEM_BUG_ON (HAS_EXECLISTS (rq->i915)); +if (engine->wa_ctx.vma && ce != engine->kernel_context) { +if (engine->wa_ctx.vma->private != ce) { + ret =clear_residuals (rq); +if (ret) +return ret; + + residuals = &engine->wa_ctx.vma->private; + } + } + ret =switch_mm (rq,vm_alias (ce));if (ret)return ret;
@@ -1600,7 +1645,7 @@ static int switch_context(struct i915_request *rq)else flags |=MI_RESTORE_INHIBIT ; - ret =mi_set_context (rq, flags); + ret =mi_set_context (rq, ce, flags);if (ret)return ret; }
@@ -1609,6 +1654,20 @@ static int switch_context(struct i915_request *rq)if (ret)return ret; +/* +* Now past the point of no return, this request _will_ be emitted. +* +* Or at least this preamble will be emitted, the request may be +* interrupted prior to submitting the user payload. If so, we +* still submit the "empty" request in order to preserve global +* state tracking such as this, our tracking of the current +* dirty context. +*/ +if (residuals) { +intel_context_put (*residuals); + *residuals =intel_context_get (ce); + } +return 0 ; }
@@ -1792,6 +1851,11 @@ static void ring_release(struct intel_engine_cs *engine)intel_engine_cleanup_common (engine); +if (engine->wa_ctx.vma) { +intel_context_put (engine->wa_ctx.vma->private); +i915_vma_unpin_and_release (&engine->wa_ctx.vma,0 ); + } +intel_ring_unpin (engine->legacy.ring);intel_ring_put (engine->legacy.ring);
@@ -1939,6 +2003,60 @@ static void setup_vecs(struct intel_engine_cs *engine) engine->emit_fini_breadcrumb = gen7_xcs_emit_breadcrumb; } +static int gen7_ctx_switch_bb_setup (struct intel_engine_cs *const engine, +struct i915_vma *const vma) +{ +return 0 ; +} + +static int gen7_ctx_switch_bb_init (struct intel_engine_cs *engine) +{ +struct drm_i915_gem_object *obj; +struct i915_vma *vma; +int size; +int err; + + size =gen7_ctx_switch_bb_setup (engine,NULL /* probe size */ ); +if (size <=0 ) +return size; + + size =ALIGN (size,PAGE_SIZE ); + obj =i915_gem_object_create_internal (engine->i915, size); +if (IS_ERR (obj)) +return PTR_ERR (obj); + + vma =i915_vma_instance (obj, engine->gt->vm,NULL ); +if (IS_ERR (vma)) { + err =PTR_ERR (vma); + goto err_obj; + } + + vma->private =intel_context_create (engine);/* dummy residuals */ +if (IS_ERR (vma->private)) { + err =PTR_ERR (vma->private); + goto err_obj; + } + + err =i915_vma_pin (vma,0 ,0 ,PIN_USER |PIN_HIGH ); +if (err) + goto err_private; + + err =gen7_ctx_switch_bb_setup (engine, vma); +if (err) + goto err_unpin; + + engine->wa_ctx.vma = vma; +return 0 ; + +err_unpin: +i915_vma_unpin (vma); +err_private: +intel_context_put (vma->private); +err_obj: +i915_gem_object_put (obj); +return err; +} +int intel_ring_submission_setup (struct intel_engine_cs *engine) {struct intel_timeline *timeline;
@@ -1992,11 +2110,19 @@ int intel_ring_submission_setup(struct intel_engine_cs *engine)GEM_BUG_ON (timeline->hwsp_ggtt != engine->status_page.vma); +if (IS_GEN (engine->i915,7 ) && engine->class ==RENDER_CLASS ) { + err =gen7_ctx_switch_bb_init (engine); +if (err) + goto err_ring_unpin; + } +/* Finally, take ownership and responsibility for cleanup! */ engine->release = ring_release;return 0 ; +err_ring_unpin: +intel_ring_unpin (ring); err_ring:intel_ring_put (ring); err_timeline_unpin:
Signature · 6 lines
2.20.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
RFC PATCH v3 2/2 drm/i915/gen7: Clear all EU/L3 residual contexts
In reply to Akeem G AbodunrinFrom: Prathap Kumar Valsan <[email protected]>
**** NOTE: ****
This series is in active development and is not intended to be merged to mainline in its current form. The intent of the RFC is simply to outline the strategy for the mitigation, as a focus for active discussion, and to openly share progress. There has been only minimal attention paid to performance thus far, as the focus is on robustness. It is not anticipated that there will be any measurable performance impact in the final version.
**** END NOTE ****
On gen7 and gen7.5 devices, there could be leftover data residuals in EU/L3 from the retiring context. This patch introduces workaround to clear that residual contexts, by submitting a batch buffer with dedicated HW context to the GPU with ring allocation for each context switching.
v2: Addressed comments about unused code, code formatting, and include additional debug code as suggested by Chris Wilson.
v3: Expand debug code for every batch_alloc_items() call... Current patch series shows significant performance improvements, on par with current drm-tips.
--- drivers/gpu/drm/i915/Makefile | 1 + drivers/gpu/drm/i915/gt/gen7_renderclear.c | 524 ++++++++++++++++++ drivers/gpu/drm/i915/gt/gen7_renderclear.h | 15 + drivers/gpu/drm/i915/gt/intel_gpu_commands.h | 17 +- .../gpu/drm/i915/gt/intel_ring_submission.c | 3 +- drivers/gpu/drm/i915/i915_utils.h | 5 + 6 files changed, 561 insertions(+), 4 deletions(-) create mode 100644 drivers/gpu/drm/i915/gt/gen7_renderclear.c create mode 100644 drivers/gpu/drm/i915/gt/gen7_renderclear.h
drivers/gpu/drm/i915/Makefile +1 -0
@@ -78,6 +78,7 @@ gt-y += \ gt/debugfs_gt.o \ gt/debugfs_gt_pm.o \ gt/gen6_ppgtt.o \ + gt/gen7_renderclear.o \ gt/gen8_ppgtt.o \ gt/intel_breadcrumbs.o \ gt/intel_context.o \
drivers/gpu/drm/i915/gt/gen7_renderclear.c new file +524 -0
524 lines not on this page · raw message
drivers/gpu/drm/i915/gt/gen7_renderclear.h new file +15 -0
@@ -0,0 +1,15 @@ +/* SPDX-License-Identifier: MIT */ +/* +* Copyright © 2019 Intel Corporation +*/ + +#ifndef __GEN7_RENDERCLEAR_H__ +#define __GEN7_RENDERCLEAR_H__ + +struct intel_engine_cs ; +struct i915_vma ; + +int gen7_setup_clear_gpr_bb (struct intel_engine_cs *const engine, +struct i915_vma *const vma); + +#endif /* __GEN7_RENDERCLEAR_H__ */
drivers/gpu/drm/i915/gt/intel_gpu_commands.h +14 -3
@@ -292,10 +292,21 @@#define MI_STORE_URB_MEM MI_INSTR(0x2D, 0)#define MI_CONDITIONAL_BATCH_BUFFER_END MI_INSTR(0x36, 0) -#define PIPELINE_SELECT ((0x3<<29)|(0x1<<27)|(0x1<<24)|(0x4<<16)) -#define GFX_OP_3DSTATE_VF_STATISTICS ((0x3<<29)|(0x1<<27)|(0x0<<24)|(0xB<<16)) -#define MEDIA_VFE_STATE ((0x3<<29)|(0x2<<27)|(0x0<<24)|(0x0<<16)) +#define STATE_BASE_ADDRESS \ + ((0x3 << 29) | (0x0 << 27) | (0x1 << 24) | (0x1 << 16)) +#define BASE_ADDRESS_MODIFY REG_BIT(0) +#define PIPELINE_SELECT \ + ((0x3 << 29) | (0x1 << 27) | (0x1 << 24) | (0x4 << 16)) +#define PIPELINE_SELECT_MEDIA REG_BIT(0) +#define GFX_OP_3DSTATE_VF_STATISTICS \ + ((0x3 << 29) | (0x1 << 27) | (0x0 << 24) | (0xB << 16)) +#define MEDIA_VFE_STATE \ + ((0x3 << 29) | (0x2 << 27) | (0x0 << 24) | (0x0 << 16))#define MEDIA_VFE_STATE_MMIO_ACCESS_MASK (0x18) +#define MEDIA_INTERFACE_DESCRIPTOR_LOAD \ + ((0x3 << 29) | (0x2 << 27) | (0x0 << 24) | (0x2 << 16)) +#define MEDIA_OBJECT \ + ((0x3 << 29) | (0x2 << 27) | (0x1 << 24) | (0x0 << 16))#define GPGPU_OBJECT ((0x3<<29)|(0x2<<27)|(0x1<<24)|(0x4<<16))#define GPGPU_WALKER ((0x3<<29)|(0x2<<27)|(0x1<<24)|(0x5<<16))#define GFX_OP_3DSTATE_DX9_CONSTANTF_VS \
drivers/gpu/drm/i915/gt/intel_ring_submission.c +2 -1
@@ -34,6 +34,7 @@#include "gem/i915_gem_context.h" #include "gen6_ppgtt.h" +#include "gen7_renderclear.h" #include "i915_drv.h" #include "i915_trace.h" #include "intel_context.h"
@@ -2006,7 +2007,7 @@ static void setup_vecs(struct intel_engine_cs *engine)static int gen7_ctx_switch_bb_setup (struct intel_engine_cs *const engine,struct i915_vma *const vma) { -return 0 ; +return gen7_setup_clear_gpr_bb (engine, vma); }static int gen7_ctx_switch_bb_init (struct intel_engine_cs *engine)
drivers/gpu/drm/i915/i915_utils.h +5 -0
@@ -172,6 +172,11 @@ __check_struct_size(size_t base, size_t arr, size_t count, size_t *size) (typeof (ptr))(__v +1 ); \ }) +#define ptr_align (ptr, align) ({ \ + unsigned long __v = (unsigned long)(ptr); \ + (typeof(ptr))round_up(__v, (align)); \ +}) +#define page_mask_bits (ptr) ptr_mask_bits(ptr, PAGE_SHIFT)#define page_unmask_bits (ptr) ptr_unmask_bits(ptr, PAGE_SHIFT)#define page_pack_bits (ptr, bits) ptr_pack_bits(ptr, bits, PAGE_SHIFT)
Signature · 6 lines
2.20.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [RFC PATCH v3 2/2] drm/i915/gen7: Clear all EU/L3 residual contexts
Quoting Akeem G Abodunrin (2020-01-16 17:46:55)
Quoted 10 lines
drivers/gpu/drm/i915/gt/gen7_renderclear.c new file +10
-0+static u32 +gen7_fill_interface_descriptor (struct batch_chunk *state, +const struct batch_vals *bv, +const struct cb_kernel *kernel, +unsigned int count) +{ +u32 *cs =batch_alloc_items (state,32 ,8 * count); +u32 offset =batch_offset (state, cs); + + *cs++ =gen7_fill_kernel_data (state, kernel->data, kernel->size);
drivers/gpu/drm/i915/gt/gen7_renderclear.c line 331
Quoted 10 lines
drivers/gpu/drm/i915/gt/gen7_renderclear.c new file +10
-0+ *cs++ = (1 <<7 ) | (1 <<13 ); + *cs++ =0 ; + *cs++ = (gen7_fill_binding_table (state, bv) - state->offset) |1 ; + *cs++ =0 ; + *cs++ =0 ; + *cs++ =0 ; + *cs++ =0 ; +/* 1 - 63dummy idds */ +memset32 (cs,0x00 , (count -1 ) *8 ); +batch_advance (state, cs);
cs is not at the end of the pack here. [cs + (count - 1) * 8]
drivers/gpu/drm/i915/gt/gen7_renderclear.c line 278
Quoted 3 lines
drivers/gpu/drm/i915/gt/gen7_renderclear.c new file +3
-0+ +return offset; +}
All others look ok.
-Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Security mitigation for Intel Gen7 HWs (rev3)
In reply to Akeem G Abodunrin== Series Details ==
== Series Details ==
Series: Security mitigation for Intel Gen7 HWs (rev3)
URL : https://patchwork.freedesktop.org/series/72028/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip b4f95c3d55d7 drm/i915: Add mechanism to submit a context WA on ring submission cf6f7615d09a drm/i915/gen7: Clear all EU/L3 residual contexts -:48: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating? #48: new file mode 100644
total: 0 errors, 1 warnings, 0 checks, 596 lines checked
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for Security mitigation for Intel Gen7 HWs (rev3)
In reply to Akeem G Abodunrin== Series Details ==
== Series Details ==
Series: Security mitigation for Intel Gen7 HWs (rev3)
URL : https://patchwork.freedesktop.org/series/72028/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7758 -> Patchwork_16141
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/index.html
Known issues
------------
Here are the changes found in Patchwork_16141 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_module_load@reload-with-fault-injection:
- fi-bxt-dsi: [PASS][1] -> [INCOMPLETE][2] ([fdo#103927])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-bxt-dsi/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/fi-bxt-dsi/igt@[email protected]
- fi-skl-6700k2: [PASS][3] -> [DMESG-WARN][4] ([i915#889])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-skl-6700k2/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/fi-skl-6700k2/igt@[email protected]
* igt@i915_pm_rpm@module-reload:
- fi-skl-guc: [PASS][5] -> [INCOMPLETE][6] ([i915#151])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-skl-guc/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/fi-skl-guc/igt@[email protected]
#### Possible fixes ####
* igt@gem_exec_create@basic:
- fi-icl-dsi: [DMESG-WARN][7] ([i915#109]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-icl-dsi/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/fi-icl-dsi/igt@[email protected]
* igt@gem_exec_suspend@basic-s0:
- {fi-ehl-1}: [INCOMPLETE][9] ([i915#937]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-ehl-1/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/fi-ehl-1/igt@[email protected]
* igt@i915_pm_rpm@module-reload:
- fi-skl-6770hq: [FAIL][11] ([i915#178]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/fi-skl-6770hq/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/fi-skl-6770hq/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[i915#109]: https://gitlab.freedesktop.org/drm/intel/issues/109
[i915#151]: https://gitlab.freedesktop.org/drm/intel/issues/151
[i915#178]: https://gitlab.freedesktop.org/drm/intel/issues/178
[i915#889]: https://gitlab.freedesktop.org/drm/intel/issues/889
[i915#937]: https://gitlab.freedesktop.org/drm/intel/issues/937
Participating hosts (47 -> 41)
------------------------------
Additional (2): fi-kbl-soraka fi-tgl-y
Missing (8): fi-hsw-4770r fi-ilk-m540 fi-hsw-4200u fi-hsw-peppy fi-byt-squawks fi-bsw-cyan fi-hsw-4770 fi-ivb-3770
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7758 -> Patchwork_16141
CI-20190529: 20190529
CI_DRM_7758: d19270ce1f367fbfc1ff3b539bcb50e11ded181f @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5371: 1b2816124ec3dbd53b81725d39292f45d41d895b @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_16141: cf6f7615d09af23b18c7b03fd4c7cb04fa96ecea @ git://anongit.freedesktop.org/gfx-ci/linux
== Kernel 32bit build ==
Warning: Kernel 32bit buildtest failed:
https://intel-gfx-ci.01.org/Patchwork_16141/build_32bit.log
CALL scripts/checksyscalls.sh CALL scripts/atomic/check-atomics.sh CHK include/generated/compile.h
Kernel: arch/x86/boot/bzImage is ready (#1)
Building modules, stage 2.
MODPOST 122 modules
ERROR: "__udivdi3" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined! scripts/Makefile.modpost:93: recipe for target '__modpost' failed make[1]: *** [__modpost] Error 1
Makefile:1282: recipe for target 'modules' failed
make: *** [modules] Error 2
== Linux commits ==
cf6f7615d09a drm/i915/gen7: Clear all EU/L3 residual contexts b4f95c3d55d7 drm/i915: Add mechanism to submit a context WA on ring submission
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BUILD: warning for Security mitigation for Intel Gen7 HWs (rev3)
In reply to Akeem G Abodunrin== Series Details ==
== Series Details ==
Series: Security mitigation for Intel Gen7 HWs (rev3)
URL : https://patchwork.freedesktop.org/series/72028/
State : warning
== Summary ==
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
CHK include/generated/compile.h
Kernel: arch/x86/boot/bzImage is ready (#1)
Building modules, stage 2.
MODPOST 122 modules
ERROR: "__udivdi3" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined! scripts/Makefile.modpost:93: recipe for target '__modpost' failed make[1]: *** [__modpost] Error 1
Makefile:1282: recipe for target 'modules' failed
make: *** [modules] Error 2
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/build_32bit.log
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for Security mitigation for Intel Gen7 HWs (rev3)
In reply to Akeem G Abodunrin== Series Details ==
== Series Details ==
Series: Security mitigation for Intel Gen7 HWs (rev3)
URL : https://patchwork.freedesktop.org/series/72028/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7758_full -> Patchwork_16141_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_16141_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_busy@busy-vcs1:
- shard-iclb: [PASS][1] -> [SKIP][2] ([fdo#112080]) +9 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb4/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb6/igt@[email protected]
* igt@gem_ctx_persistence@vcs1-hostile-preempt:
- shard-iclb: [PASS][3] -> [SKIP][4] ([fdo#109276] / [fdo#112080]) +2 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb2/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb5/igt@[email protected]
* igt@gem_ctx_persistence@vecs0-mixed-process:
- shard-skl: [PASS][5] -> [FAIL][6] ([i915#679])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-skl9/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-skl7/igt@[email protected]
* igt@gem_exec_schedule@preempt-other-chain-bsd:
- shard-iclb: [PASS][7] -> [SKIP][8] ([fdo#112146]) +3 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb6/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb1/igt@[email protected]
* igt@gem_exec_schedule@smoketest-bsd1:
- shard-tglb: [PASS][9] -> [INCOMPLETE][10] ([i915#463] / [i915#472])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-tglb1/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-tglb3/igt@[email protected]
* igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing:
- shard-skl: [PASS][11] -> [TIMEOUT][12] ([fdo#112271] / [i915#530])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-skl5/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-skl6/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html
- shard-tglb: [PASS][13] -> [TIMEOUT][14] ([fdo#112126] / [fdo#112271] / [i915#530])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-tglb3/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-tglb3/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html
* igt@gem_persistent_relocs@forked-interruptible-thrashing:
- shard-tglb: [PASS][15] -> [INCOMPLETE][16] ([i915#472] / [i915#530])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-tglb7/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-tglb6/igt@[email protected]
* igt@gem_sync@basic-store-each:
- shard-tglb: [PASS][17] -> [INCOMPLETE][18] ([i915#472])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-tglb1/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-tglb3/igt@[email protected]
* igt@i915_suspend@forcewake:
- shard-skl: [PASS][19] -> [INCOMPLETE][20] ([i915#69])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-skl10/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-skl3/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-varying-size:
- shard-skl: [PASS][21] -> [FAIL][22] ([IGT#5] / [i915#697])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-skl2/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-skl4/igt@[email protected]
* igt@kms_draw_crc@draw-method-xrgb2101010-mmap-wc-untiled:
- shard-skl: [PASS][23] -> [FAIL][24] ([i915#52] / [i915#54]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-skl9/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-skl8/igt@[email protected]
* igt@kms_flip@plain-flip-fb-recreate-interruptible:
- shard-kbl: [PASS][25] -> [FAIL][26] ([i915#34])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-kbl1/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-kbl4/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-msflip-blt:
- shard-tglb: [PASS][27] -> [FAIL][28] ([i915#49]) +1 similar issue
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-tglb4/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-tglb1/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: [PASS][29] -> [DMESG-WARN][30] ([i915#180]) +6 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-kbl7/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-kbl1/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-pwrite:
- shard-skl: [PASS][31] -> [FAIL][32] ([i915#49])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-skl9/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-skl8/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [PASS][33] -> [FAIL][34] ([fdo#108145] / [i915#265])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-skl1/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-skl1/igt@[email protected]
* igt@kms_psr@psr2_primary_page_flip:
- shard-iclb: [PASS][35] -> [SKIP][36] ([fdo#109441])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb5/igt@kms_psr@psr2_primary_page_flip.html
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-apl: [PASS][37] -> [DMESG-WARN][38] ([i915#180]) +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-apl8/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-apl4/igt@[email protected]
* igt@perf@oa-exponents:
- shard-glk: [PASS][39] -> [FAIL][40] ([i915#84])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-glk5/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-glk5/igt@[email protected]
* igt@prime_busy@hang-bsd2:
- shard-iclb: [PASS][41] -> [SKIP][42] ([fdo#109276]) +17 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb2/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb5/igt@[email protected]
#### Possible fixes ####
* igt@gem_ctx_isolation@vcs1-dirty-create:
- shard-iclb: [SKIP][43] ([fdo#109276] / [fdo#112080]) -> [PASS][44] +4 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb6/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb1/igt@[email protected]
* igt@gem_ctx_persistence@processes:
- shard-iclb: [FAIL][45] ([i915#570]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb4/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb6/igt@[email protected]
* igt@gem_ctx_shared@q-smoketest-bsd2:
- shard-tglb: [INCOMPLETE][47] ([i915#461] / [i915#472]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-tglb3/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-tglb1/igt@[email protected]
* igt@gem_ctx_shared@q-smoketest-vebox:
- shard-tglb: [INCOMPLETE][49] ([fdo#111735] / [i915#472]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-tglb6/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-tglb5/igt@[email protected]
* igt@gem_eio@kms:
- shard-tglb: [INCOMPLETE][51] ([i915#472] / [i915#476]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-tglb6/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-tglb3/igt@[email protected]
* igt@gem_exec_await@wide-all:
- shard-tglb: [INCOMPLETE][53] ([fdo#111736] / [i915#472]) -> [PASS][54] +1 similar issue
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-tglb3/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-tglb1/igt@[email protected]
* igt@gem_exec_balancer@hang:
- shard-iclb: [INCOMPLETE][55] ([i915#140]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb2/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb6/igt@[email protected]
* igt@gem_exec_create@madvise:
- shard-tglb: [INCOMPLETE][57] ([i915#472]) -> [PASS][58] +2 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-tglb4/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-tglb5/igt@[email protected]
* igt@gem_exec_schedule@pi-common-bsd:
- shard-iclb: [SKIP][59] ([i915#677]) -> [PASS][60] +1 similar issue
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb4/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb6/igt@[email protected]
* igt@gem_exec_schedule@preempt-queue-bsd1:
- shard-iclb: [SKIP][61] ([fdo#109276]) -> [PASS][62] +18 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb6/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb1/igt@[email protected]
* igt@gem_exec_schedule@preemptive-hang-bsd:
- shard-iclb: [SKIP][63] ([fdo#112146]) -> [PASS][64] +7 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb4/igt@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb6/igt@[email protected]
* igt@gem_exec_schedule@smoketest-all:
- shard-tglb: [INCOMPLETE][65] ([i915#463] / [i915#472]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-tglb7/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-tglb7/igt@[email protected]
* igt@gem_exec_schedule@smoketest-vebox:
- shard-tglb: [INCOMPLETE][67] ([i915#472] / [i915#707]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-tglb4/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-tglb8/igt@[email protected]
* igt@gem_persistent_relocs@forked-faulting-reloc-thrashing:
- shard-kbl: [INCOMPLETE][69] ([fdo#103665] / [i915#530]) -> [PASS][70]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-kbl6/igt@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-kbl1/igt@[email protected]
* igt@gem_ppgtt@flink-and-close-vma-leak:
- shard-glk: [FAIL][71] ([i915#644]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-glk9/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-glk2/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-skl: [DMESG-WARN][73] ([i915#716]) -> [PASS][74]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-skl8/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-skl6/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][75] ([i915#454]) -> [PASS][76]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb4/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb5/igt@[email protected]
* {igt@i915_pm_rc6_residency@rc6-idle}:
- shard-apl: [FAIL][77] ([i915#973]) -> [PASS][78]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-apl3/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-apl7/igt@[email protected]
* igt@i915_selftest@live_execlists:
- shard-kbl: [INCOMPLETE][79] ([fdo#103665] / [fdo#112175] / [fdo#112259]) -> [PASS][80]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-kbl6/igt@i915_selftest@live_execlists.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-kbl3/igt@i915_selftest@live_execlists.html
* igt@kms_color@pipe-b-ctm-blue-to-red:
- shard-skl: [DMESG-WARN][81] ([i915#109]) -> [PASS][82]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-skl3/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-skl2/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [DMESG-WARN][83] ([i915#180]) -> [PASS][84] +3 similar issues
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-kbl2/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-kbl2/igt@[email protected]
* igt@kms_flip@plain-flip-ts-check-interruptible:
- shard-skl: [FAIL][85] ([i915#34]) -> [PASS][86]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-skl9/igt@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-skl7/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-stridechange:
- shard-tglb: [FAIL][87] ([i915#49]) -> [PASS][88] +3 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-tglb5/igt@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-tglb4/igt@[email protected]
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes:
- shard-iclb: [INCOMPLETE][89] ([i915#140] / [i915#250]) -> [PASS][90]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb8/igt@[email protected]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb4/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min:
- shard-skl: [FAIL][91] ([fdo#108145]) -> [PASS][92] +1 similar issue
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-skl6/igt@[email protected]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-skl10/igt@[email protected]
* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [SKIP][93] ([fdo#109441]) -> [PASS][94] +3 similar issues
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb1/igt@kms_psr@psr2_cursor_mmap_cpu.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
* igt@perf_pmu@busy-no-semaphores-vcs1:
- shard-iclb: [SKIP][95] ([fdo#112080]) -> [PASS][96] +5 similar issues
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb6/igt@[email protected]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb1/igt@[email protected]
#### Warnings ####
* igt@gem_ctx_isolation@vcs1-nonpriv:
- shard-iclb: [FAIL][97] ([IGT#28]) -> [SKIP][98] ([fdo#109276] / [fdo#112080])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb4/igt@[email protected]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb5/igt@[email protected]
* igt@gem_ctx_isolation@vcs1-nonpriv-switch:
- shard-iclb: [SKIP][99] ([fdo#109276] / [fdo#112080]) -> [FAIL][100] ([IGT#28])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb6/igt@[email protected]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb1/igt@[email protected]
* igt@kms_dp_dsc@basic-dsc-enable-edp:
- shard-iclb: [SKIP][101] ([fdo#109349]) -> [DMESG-WARN][102] ([fdo#107724])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7758/shard-iclb1/igt@[email protected]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16141/shard-iclb2/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[IGT#28]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/28
[IGT#5]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/5
[fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109349]: https://bugs.freedesktop.org/show_bug.cgi?id=109349
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#111735]: https://bugs.freedesktop.org/show_bug.cgi?id=111735
[fdo#111736]: https://bugs.freedesktop.org/show_bug.cgi?id=111736
[fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080
[fdo#112126]: https://bugs.freedesktop.org/show_bug.cgi?id=112126
[fdo#112146]: https://bugs.freedesktop.org/show_bug.cgi?id=112146
[fdo#112175]: https://bugs.freedesktop.org/show_bug.cgi?id=112175
[fdo#112259]: https://bugs.freedesktop.org/show_bug.cgi?id=112259
[fdo#112271]: https://bugs.freedesktop.org/show_bug.cgi?id=112271
[i915#109]: https://gitlab.freedesktop.org/drm/intel/issues/109
[i915#140]: https://gitlab.freedesktop.org/drm/intel/issues/140
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#250]: https://gitlab.freedesktop.org/drm/intel/issues/250
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#34]: https://gitlab.freedesktop.org/drm/intel/issues/34
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#461]: https://gitlab.freedesktop.org/drm/intel/issues/461
[i915#463]: https://gitlab.freedesktop.org/drm/intel/issues/463
[i915#472]: https://gitlab.freedesktop.org/drm/intel/issues/472
[i915#476]: https://gitlab.freedesktop.org/drm/intel/issues/476
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#52]: https://gitlab.freedesktop.org/drm/intel/issues/52
[i915#530]: https://gitlab.freedesktop.org/drm/intel/issues/530
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#570]: https://gitlab.freedesktop.org/drm/intel/issues/570
[i915#644]: https://gitlab.freedesktop.org/drm/intel/issues/644
[i915#677]: https://gitlab.freedesktop.org/drm/intel/issues/677
[i915#679]: https://gitlab.freedesktop.org/drm/intel/issues/679
[i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69
[i915#697]: https://gitlab.freedesktop.org/drm/intel/issues/697
[i915#707]: https://gitlab.freedesktop.org/drm/intel/issues/707
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#84]: https://gitlab.freedesktop.org/drm/intel/issues/84
[i915#973]: https://gitlab.freedesktop.org/drm/intel/issues/973
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7758 -> Patchwork_16141
CI-20190529: 20190529
CI_DRM_7758: d19270ce1f367fbfc1ff3b539bcb50e11ded181f @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5371: 1b2816124ec3dbd53b81725d39292f45d41d895b @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_16141: cf6f7615d09af23b18c7b03fd4c7cb04fa96ecea @ 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_16141/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx