lrc selftest fixes
Subsystems (2)
v3 cover lrc selftest fixes
Few bug fixes for lrc selftest.
v3:
Extending the first patch for gen8
Chris Wilson (4):
drm/i915/gt: Explicitly clear BB_OFFSET for new contexts drm/i915/selftests: Check for incomplete LRI from the context image drm/i915/selftest: Always cancel semaphore on error drm/i915/selftest: Clear the output buffers before GPU writes
drivers/gpu/drm/i915/gt/intel_engine_regs.h | 1 + drivers/gpu/drm/i915/gt/intel_lrc.c | 19 ++++ drivers/gpu/drm/i915/gt/selftest_lrc.c | 115 ++++++++++++++++---- 3 files changed, 115 insertions(+), 20 deletions(-)
Signature · 1 line
2.20.1
PATCH v3 1/4 drm/i915/gt: Explicitly clear BB_OFFSET for new contexts
From: Chris Wilson <[email protected]>
Even though the initial protocontext we load onto HW has the register cleared, by the time we save it into the default image, BB_OFFSET has had the enable bit set. Reclear BB_OFFSET for each new context.
Testcase: igt/i915_selftests/gt_lrc
v2:
Extend it for gen8.
--- drivers/gpu/drm/i915/gt/intel_engine_regs.h | 1 + drivers/gpu/drm/i915/gt/intel_lrc.c | 19 +++++++++++++++++++ drivers/gpu/drm/i915/gt/selftest_lrc.c | 5 +++++ 3 files changed, 25 insertions(+)
drivers/gpu/drm/i915/gt/intel_engine_regs.h +1 -0
@@ -109,6 +109,7 @@#define RING_SBBSTATE (base) _MMIO((base) + 0x118)/* hsw+ */ #define RING_SBBADDR_UDW (base) _MMIO((base) + 0x11c)/* gen8+ */ #define RING_BBADDR (base) _MMIO((base) + 0x140) +#define RING_BB_OFFSET (base) _MMIO((base) + 0x158)#define RING_BBADDR_UDW (base) _MMIO((base) + 0x168)/* gen8+ */ #define CCID (base) _MMIO((base) + 0x180)#define CCID_EN BIT(0)
drivers/gpu/drm/i915/gt/intel_lrc.c +19 -0
@@ -662,6 +662,20 @@ static int lrc_ring_mi_mode(const struct intel_engine_cs *engine)return -1 ; } +static int lrc_ring_bb_offset (const struct intel_engine_cs *engine) +{ +if (GRAPHICS_VER_FULL (engine->i915) >=IP_VER (12 ,50 )) +return 0x80 ; +else if (GRAPHICS_VER (engine->i915) >=12 ) +return 0x70 ; +else if (GRAPHICS_VER (engine->i915) >=9 ) +return 0x64 ; +else if (GRAPHICS_VER (engine->i915) >=8 ) +return 0xc4 ; +else +return -1 ; +} +static int lrc_ring_gpr0 (const struct intel_engine_cs *engine) {if (GRAPHICS_VER_FULL (engine->i915) >=IP_VER (12 ,50 ))
@@ -768,6 +782,7 @@ static void init_common_regs(u32 * const regs, bool inhibit) {u32 ctl; +int loc; ctl =_MASKED_BIT_ENABLE (CTX_CTRL_INHIBIT_SYN_CTX_SWITCH ); ctl |=_MASKED_BIT_DISABLE (CTX_CTRL_ENGINE_CTX_RESTORE_INHIBIT );
@@ -779,6 +794,10 @@ static void init_common_regs(u32 * const regs, regs[CTX_CONTEXT_CONTROL ] = ctl; regs[CTX_TIMESTAMP ] = ce->stats.runtime.last; + + loc =lrc_ring_bb_offset (engine); +if (loc !=-1 ) + regs[loc +1 ] =0 ; } static void init_wa_bb_regs(u32 * const regs,
drivers/gpu/drm/i915/gt/selftest_lrc.c +5 -0
@@ -323,6 +323,11 @@ static int live_lrc_fixed(void *arg) lrc_ring_cmd_buf_cctl(engine), "RING_CMD_BUF_CCTL" }, + { +i915_mmio_reg_offset (RING_BB_OFFSET (engine->mmio_base)), +lrc_ring_bb_offset (engine), +"RING_BB_OFFSET" + }, { }, }, *t;u32 *hw;
Signature · 1 line
2.20.1
PATCH v3 2/4 drm/i915/selftests: Check for incomplete LRI from the context image
In reply to Ramalingam CFrom: Chris Wilson <[email protected]>
In order to keep the context image parser simple, we assume that all commands follow a similar format. A few, especially not MI commands on the render engines, have fixed lengths not encoded in a length field. This caused us to incorrectly skip over 3D state commands, and start interpreting context data as instructions. Eventually, as Daniele discovered, this would lead us to find addition LRI as part of the data and mistakenly add invalid LRI commands to the context probes.
Stop parsing after we see the first !MI command, as we know we will have seen all the context registers by that point. (Mostly true for all gen so far, though the render context does have LRI after the first page that we have been ignoring so far. It would be useful to extract those as well so that we have the full list of user accessible registers.)
Similarly, emit a warning if we do try to emit an invalid zero-length LRI.
--- drivers/gpu/drm/i915/gt/selftest_lrc.c | 61 +++++++++++++++++++++++--- 1 file changed, 54 insertions(+), 7 deletions(-)
drivers/gpu/drm/i915/gt/selftest_lrc.c +54 -7
@@ -27,6 +27,9 @@#define NUM_GPR 16#define NUM_GPR_DW (NUM_GPR * 2)/* each GPR is 2 dwords */ +#define LRI_HEADER MI_INSTR(0x22, 0) +#define LRI_LENGTH_MASK GENMASK(7, 0) +static struct i915_vma *create_scratch (struct intel_gt *gt) {return __vm_create_scratch_for_read_pinned (>->ggtt->vm,PAGE_SIZE );
@@ -180,7 +183,7 @@ static int live_lrc_layout(void *arg)continue ; } -if ((lri &GENMASK (31 ,23 )) !=MI_INSTR (0x22 ,0 )) { +if ((lri &GENMASK (31 ,23 )) !=LRI_HEADER ) {pr_err ("%s: Expected LRI command at dword %d, found %08x\n" , engine->name, dw, lri); err = -EINVAL ;
@@ -945,18 +948,40 @@ store_context(struct intel_context *ce, struct i915_vma *scratch) hw = defaults; hw +=LRC_STATE_OFFSET /sizeof (*hw); do { - u32 len = hw[dw] & 0x7f; + u32 len = hw[dw] & LRI_LENGTH_MASK; + + /* + * Keep it simple, skip parsing complex commands + * + * At present, there are no more MI_LOAD_REGISTER_IMM + * commands after the first 3D state command. Rather + * than include a table (see i915_cmd_parser.c) of all + * the possible commands and their instruction lengths + * (or mask for variable length instructions), assume + * we have gathered the complete list of registers and + * bail out. + */ + if ((hw[dw] >> INSTR_CLIENT_SHIFT) != INSTR_MI_CLIENT) + break; if (hw[dw] == 0) { dw++; continue; } - if ((hw[dw] & GENMASK(31, 23)) != MI_INSTR(0x22, 0)) { + if ((hw[dw] & GENMASK(31, 23)) != LRI_HEADER) { + /* Assume all other MI commands match LRI length mask */ dw += len + 2; continue; } + if (!len) { + pr_err("%s: invalid LRI found in context image\n", + ce->engine->name); + igt_hexdump(defaults, PAGE_SIZE); + break; + } + dw++; len = (len + 1) / 2; while (len--) {
@@ -1108,18 +1133,29 @@ static struct i915_vma *load_context(struct intel_context *ce, u32 poison) hw = defaults; hw +=LRC_STATE_OFFSET /sizeof (*hw); do { - u32 len = hw[dw] & 0x7f; + u32 len = hw[dw] & LRI_LENGTH_MASK; + + /* For simplicity, break parsing at the first complex command */ + if ((hw[dw] >> INSTR_CLIENT_SHIFT) != INSTR_MI_CLIENT) + break; if (hw[dw] == 0) { dw++; continue; } - if ((hw[dw] & GENMASK(31, 23)) != MI_INSTR(0x22, 0)) { + if ((hw[dw] & GENMASK(31, 23)) != LRI_HEADER) { dw += len + 2; continue; } + if (!len) { + pr_err("%s: invalid LRI found in context image\n", + ce->engine->name); + igt_hexdump(defaults, PAGE_SIZE); + break; + } + dw++; len = (len + 1) / 2; *cs++ = MI_LOAD_REGISTER_IMM(len);
@@ -1248,18 +1284,29 @@ static int compare_isolation(struct intel_engine_cs *engine, hw = defaults; hw +=LRC_STATE_OFFSET /sizeof (*hw); do { - u32 len = hw[dw] & 0x7f; + u32 len = hw[dw] & LRI_LENGTH_MASK; + + /* For simplicity, break parsing at the first complex command */ + if ((hw[dw] >> INSTR_CLIENT_SHIFT) != INSTR_MI_CLIENT) + break; if (hw[dw] == 0) { dw++; continue; } - if ((hw[dw] & GENMASK(31, 23)) != MI_INSTR(0x22, 0)) { + if ((hw[dw] & GENMASK(31, 23)) != LRI_HEADER) { dw += len + 2; continue; } + if (!len) { + pr_err("%s: invalid LRI found in context image\n", + engine->name); + igt_hexdump(defaults, PAGE_SIZE); + break; + } + dw++; len = (len + 1) / 2; while (len--) {
Signature · 1 line
2.20.1
PATCH v3 3/4 drm/i915/selftest: Always cancel semaphore on error
In reply to Ramalingam CFrom: Chris Wilson <[email protected]>
Ensure that we always signal the semaphore when timing out, so that if it happens to be stuck waiting for the semaphore we will quickly recover without having to wait for a reset.
--- drivers/gpu/drm/i915/gt/selftest_lrc.c | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-)
drivers/gpu/drm/i915/gt/selftest_lrc.c +8 -9
@@ -1411,18 +1411,17 @@ static int __lrc_isolation(struct intel_engine_cs *engine, u32 poison) } err =poison_registers (B , poison, sema); -if (err) { -WRITE_ONCE (*sema,-1 ); -i915_request_put (rq); - goto err_result1; - } - -if (i915_request_wait (rq,0 ,HZ /2 ) <0 ) { -i915_request_put (rq); +if (err ==0 &&i915_request_wait (rq,0 ,HZ /2 ) <0 ) { +pr_err ("%s(%s): wait for results timed out\n" , + __func__, engine->name); err = -ETIME ; - goto err_result1; } + +/* Always cancel the semaphore wait, just in case the GPU gets stuck */ +WRITE_ONCE (*sema,-1 );i915_request_put (rq); +if (err) + goto err_result1; err =compare_isolation (engine, ref, result,A , poison);
Signature · 1 line
2.20.1
PATCH v3 4/4 drm/i915/selftest: Clear the output buffers before GPU writes
In reply to Ramalingam CFrom: Chris Wilson <[email protected]>
When testing whether we can get the GPU to leak information about non-privileged state, we first need to ensure that the output buffer is set to a known value as the HW may opt to skip the write into memory for a non-privileged read of a sensitive register. We chose POISON_INUSE (0x5a) so that is both non-zero and distinct from the poison values used during the test.
v2:
Use i915_gem_object_pin_map_unlocked
--- drivers/gpu/drm/i915/gt/selftest_lrc.c | 32 ++++++++++++++++++++++---- 1 file changed, 28 insertions(+), 4 deletions(-)
drivers/gpu/drm/i915/gt/selftest_lrc.c +28 -4
@@ -1346,6 +1346,30 @@ static int compare_isolation(struct intel_engine_cs *engine,return err; } +static struct i915_vma * +create_result_vma (struct i915_address_space *vm,unsigned long sz) +{ +struct i915_vma *vma; +void *ptr; + + vma =create_user_vma (vm, sz); +if (IS_ERR (vma)) +return vma; + +/* Set the results to a known value distinct from the poison */ + ptr =i915_gem_object_pin_map_unlocked (vma->obj,I915_MAP_WC ); +if (IS_ERR (ptr)) { +i915_vma_put (vma); +return ERR_CAST (ptr); + } + +memset (ptr,POISON_INUSE , vma->size); +i915_gem_object_flush_map (vma->obj); +i915_gem_object_unpin_map (vma->obj); + +return vma; +} +static int __lrc_isolation (struct intel_engine_cs *engine,u32 poison) {u32 *sema =memset32 (engine->status_page.addr +1000 ,0 ,1 );
@@ -1364,13 +1388,13 @@ static int __lrc_isolation(struct intel_engine_cs *engine, u32 poison) goto err_A; } - ref[0 ] =create_user_vma (A ->vm,SZ_64K ); + ref[0 ] =create_result_vma (A ->vm,SZ_64K );if (IS_ERR (ref[0 ])) { err =PTR_ERR (ref[0 ]); goto err_B; } - ref[1 ] =create_user_vma (A ->vm,SZ_64K ); + ref[1 ] =create_result_vma (A ->vm,SZ_64K );if (IS_ERR (ref[1 ])) { err =PTR_ERR (ref[1 ]); goto err_ref0;
@@ -1392,13 +1416,13 @@ static int __lrc_isolation(struct intel_engine_cs *engine, u32 poison) }i915_request_put (rq); - result[0 ] =create_user_vma (A ->vm,SZ_64K ); + result[0 ] =create_result_vma (A ->vm,SZ_64K );if (IS_ERR (result[0 ])) { err =PTR_ERR (result[0 ]); goto err_ref1; } - result[1 ] =create_user_vma (A ->vm,SZ_64K ); + result[1 ] =create_result_vma (A ->vm,SZ_64K );if (IS_ERR (result[1 ])) { err =PTR_ERR (result[1 ]); goto err_result0;
Signature · 1 line
2.20.1
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for lrc selftest fixes (rev5)
In reply to Ramalingam C== Series Details ==
== Series Details ==
Series: lrc selftest fixes (rev5)
URL : https://patchwork.freedesktop.org/series/101353/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
-+drivers/gpu/drm/i915/gt/intel_engine_stats.h:28:9: warning: trying to copy expression type 31 +drivers/gpu/drm/i915/gt/intel_engine_stats.h:28:9: warning: trying to copy expression type 31 +drivers/gpu/drm/i915/gt/intel_engine_stats.h:28:9: warning: trying to copy expression type 31 +drivers/gpu/drm/i915/gt/intel_engine_stats.h:33:9: warning: trying to copy expression type 31 +drivers/gpu/drm/i915/gt/intel_engine_stats.h:33:9: warning: trying to copy expression type 31 +drivers/gpu/drm/i915/gt/intel_engine_stats.h:51:9: warning: trying to copy expression type 31 +drivers/gpu/drm/i915/gt/intel_engine_stats.h:51:9: warning: trying to copy expression type 31 +drivers/gpu/drm/i915/gt/intel_engine_stats.h:51:9: warning: trying to copy expression type 31 +drivers/gpu/drm/i915/gt/intel_engine_stats.h:57:9: warning: trying to copy expression type 31 +drivers/gpu/drm/i915/gt/intel_engine_stats.h:57:9: warning: trying to copy expression type 31 +drivers/gpu/drm/i915/gt/intel_reset.c:1391:5: warning: context imbalance in 'intel_gt_reset_trylock' - different lock contexts for basic block +./include/linux/find.h:40:31: warning: shift count is negative (-24)+./include/linux/find.h:40:31: warning: shift count is negative (-24)+./include/linux/find.h:40:31: warning: shift count is negative (-24)+./include/linux/find.h:40:31: warning: shift count is negative (-24)+./include/linux/find.h:40:31: warning: shift count is negative (-448)+./include/linux/find.h:40:31: warning: shift count is negative (-448)+./include/linux/spinlock.h:404:9: warning: context imbalance in 'fwtable_read16' - different lock contexts for basic block +./include/linux/spinlock.h:404:9: warning: context imbalance in 'fwtable_read32' - different lock contexts for basic block +./include/linux/spinlock.h:404:9: warning: context imbalance in 'fwtable_read64' - different lock contexts for basic block +./include/linux/spinlock.h:404:9: warning: context imbalance in 'fwtable_read8' - different lock contexts for basic block +./include/linux/spinlock.h:404:9: warning: context imbalance in 'fwtable_write16' - different lock contexts for basic block +./include/linux/spinlock.h:404:9: warning: context imbalance in 'fwtable_write32' - different lock contexts for basic block +./include/linux/spinlock.h:404:9: warning: context imbalance in 'fwtable_write8' - different lock contexts for basic block +./include/linux/spinlock.h:404:9: warning: context imbalance in 'gen6_write16' - different lock contexts for basic block +./include/linux/spinlock.h:404:9: warning: context imbalance in 'gen6_write32' - different lock contexts for basic block +./include/linux/spinlock.h:404:9: warning: context imbalance in 'gen6_write8' - different lock contexts for basic block
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BAT: failure for lrc selftest fixes (rev5)
In reply to Ramalingam C== Series Details ==
== Series Details ==
Series: lrc selftest fixes (rev5)
URL : https://patchwork.freedesktop.org/series/101353/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11582 -> Patchwork_101353v5
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_101353v5 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_101353v5, 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_101353v5/index.html
Participating hosts (43 -> 41)
------------------------------
Additional (1): fi-rkl-11600
Missing (3): fi-bsw-cyan fi-hsw-4770 fi-icl-u2
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_101353v5:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live@gt_lrc:
- fi-bsw-n3050: [PASS][1] -> [DMESG-FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11582/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html
- fi-bsw-kefka: [PASS][3] -> [DMESG-FAIL][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11582/fi-bsw-kefka/igt@i915_selftest@live@gt_lrc.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-bsw-kefka/igt@i915_selftest@live@gt_lrc.html
- fi-bdw-gvtdvm: [PASS][5] -> [DMESG-FAIL][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11582/fi-bdw-gvtdvm/igt@i915_selftest@live@gt_lrc.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-bdw-gvtdvm/igt@i915_selftest@live@gt_lrc.html
- fi-bsw-nick: [PASS][7] -> [DMESG-FAIL][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11582/fi-bsw-nick/igt@i915_selftest@live@gt_lrc.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-bsw-nick/igt@i915_selftest@live@gt_lrc.html
- fi-bdw-5557u: [PASS][9] -> [DMESG-FAIL][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11582/fi-bdw-5557u/igt@i915_selftest@live@gt_lrc.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-bdw-5557u/igt@i915_selftest@live@gt_lrc.html
* igt@i915_selftest@live@memory_region:
- fi-cfl-8109u: [PASS][11] -> [DMESG-WARN][12] +11 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11582/fi-cfl-8109u/igt@i915_selftest@live@memory_region.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-cfl-8109u/igt@i915_selftest@live@memory_region.html
Known issues
------------
Here are the changes found in Patchwork_101353v5 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_huc_copy@huc-copy:
- fi-rkl-11600: NOTRUN -> [SKIP][13] ([i915#2190])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-rkl-11600/igt@[email protected]
* igt@gem_lmem_swapping@basic:
- fi-rkl-11600: NOTRUN -> [SKIP][14] ([i915#4613]) +3 similar issues
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-rkl-11600/igt@[email protected]
* igt@gem_tiled_pread_basic:
- fi-rkl-11600: NOTRUN -> [SKIP][15] ([i915#3282])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-rkl-11600/igt@gem_tiled_pread_basic.html
* igt@i915_pm_backlight@basic-brightness:
- fi-rkl-11600: NOTRUN -> [SKIP][16] ([i915#3012])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-rkl-11600/igt@[email protected]
* igt@i915_pm_rpm@module-reload:
- fi-cfl-8109u: [PASS][17] -> [DMESG-FAIL][18] ([i915#62])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11582/fi-cfl-8109u/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-cfl-8109u/igt@[email protected]
* igt@i915_selftest@live@hangcheck:
- fi-bdw-5557u: NOTRUN -> [INCOMPLETE][19] ([i915#3921])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-bdw-5557u/igt@i915_selftest@[email protected]
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-snb-2600: NOTRUN -> [SKIP][20] ([fdo#109271] / [fdo#111827])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-snb-2600/igt@[email protected]
* igt@kms_chamelium@dp-crc-fast:
- fi-rkl-11600: NOTRUN -> [SKIP][21] ([fdo#111827]) +8 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-rkl-11600/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-rkl-11600: NOTRUN -> [SKIP][22] ([i915#4070] / [i915#4103]) +1 similar issue
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-rkl-11600/igt@[email protected]
* igt@kms_force_connector_basic@force-load-detect:
- fi-rkl-11600: NOTRUN -> [SKIP][23] ([fdo#109285] / [i915#4098])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-rkl-11600/igt@[email protected]
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-b:
- fi-cfl-8109u: [PASS][24] -> [DMESG-WARN][25] ([i915#62]) +15 similar issues
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11582/fi-cfl-8109u/igt@[email protected]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-cfl-8109u/igt@[email protected]
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-rkl-11600: NOTRUN -> [SKIP][26] ([i915#4070] / [i915#533])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-rkl-11600/igt@[email protected]
* igt@kms_psr@primary_mmap_gtt:
- fi-rkl-11600: NOTRUN -> [SKIP][27] ([i915#1072]) +3 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-rkl-11600/igt@kms_psr@primary_mmap_gtt.html
* igt@kms_setmode@basic-clone-single-crtc:
- fi-rkl-11600: NOTRUN -> [SKIP][28] ([i915#3555] / [i915#4098])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-rkl-11600/igt@[email protected]
* igt@prime_vgem@basic-userptr:
- fi-rkl-11600: NOTRUN -> [SKIP][29] ([i915#3301] / [i915#3708])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-rkl-11600/igt@[email protected]
* igt@prime_vgem@basic-write:
- fi-rkl-11600: NOTRUN -> [SKIP][30] ([i915#3291] / [i915#3708]) +2 similar issues
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-rkl-11600/igt@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@gt_lrc:
- {fi-tgl-dsi}: [DMESG-FAIL][31] ([i915#2373]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11582/fi-tgl-dsi/igt@i915_selftest@live@gt_lrc.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-tgl-dsi/igt@i915_selftest@live@gt_lrc.html
* igt@i915_selftest@live@hangcheck:
- fi-snb-2600: [INCOMPLETE][33] ([i915#3921]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11582/fi-snb-2600/igt@i915_selftest@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-snb-2600/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@mman:
- fi-bdw-5557u: [INCOMPLETE][35] ([i915#5704]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11582/fi-bdw-5557u/igt@i915_selftest@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-bdw-5557u/igt@i915_selftest@[email protected]
#### Warnings ####
* igt@debugfs_test@read_all_entries:
- fi-apl-guc: [DMESG-WARN][37] ([i915#5595]) -> [DMESG-WARN][38] ([i915#1610])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11582/fi-apl-guc/igt@debugfs_test@read_all_entries.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/fi-apl-guc/igt@debugfs_test@read_all_entries.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1610]: https://gitlab.freedesktop.org/drm/intel/issues/1610
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2373]: https://gitlab.freedesktop.org/drm/intel/issues/2373
[i915#3012]: https://gitlab.freedesktop.org/drm/intel/issues/3012
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3576]: https://gitlab.freedesktop.org/drm/intel/issues/3576
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921
[i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070
[i915#4098]: https://gitlab.freedesktop.org/drm/intel/issues/4098
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#5270]: https://gitlab.freedesktop.org/drm/intel/issues/5270
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5356]: https://gitlab.freedesktop.org/drm/intel/issues/5356
[i915#5595]: https://gitlab.freedesktop.org/drm/intel/issues/5595
[i915#5704]: https://gitlab.freedesktop.org/drm/intel/issues/5704
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
Build changes
-------------
* Linux: CI_DRM_11582 -> Patchwork_101353v5
CI-20190529: 20190529
CI_DRM_11582: 4c61a333113eb2bfd41c9e735fc4307f5e14646b @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6463: 0793746970d24ee41d5cfe9905e7532ea1530721 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_101353v5: 4c61a333113eb2bfd41c9e735fc4307f5e14646b @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
65753e12cb5d drm/i915/selftest: Clear the output buffers before GPU writes 9fb97deaf9b3 drm/i915/selftest: Always cancel semaphore on error 9766d3787030 drm/i915/selftests: Check for incomplete LRI from the context image daa486f45fbe drm/i915/gt: Explicitly clear BB_OFFSET for new contexts
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101353v5/index.html