* [Intel-gfx] [CI 1/2] drm/i915: Disable semaphore inter-engine sync without timeslicing @ 2020-05-21 14:06 Chris Wilson 2020-05-21 14:06 ` [Intel-gfx] [CI 2/2] drm/i915: Avoid using rq->engine after free during i915_fence_release Chris Wilson ` (3 more replies) 0 siblings, 4 replies; 5+ messages in thread From: Chris Wilson @ 2020-05-21 14:06 UTC (permalink / raw) To: intel-gfx Since the removal of the no-semaphore boosting, we rely on timeslicing to reorder passed inter-dependency hogs across the engines. However, we require preemption to support timeslicing into user payloads, and not all machine support preemption so we do not universally enable timeslicing, even when it would correctly preempt our own inter-engine semaphores. Since timeslicing and semaphore priority deboosting is now disabled on Broadwell/Braswell, we have to follow suite and not use semaphores. Testcase: igt/gem_exec_schedule/semaphore-codependency # bdw/bsw Fixes: 18e4af04d218 ("drm/i915: Drop no-semaphore boosting") Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> --- drivers/gpu/drm/i915/gem/i915_gem_context.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/i915/gem/i915_gem_context.c b/drivers/gpu/drm/i915/gem/i915_gem_context.c index 900ea8b7fc8f..f5d59d18cd5b 100644 --- a/drivers/gpu/drm/i915/gem/i915_gem_context.c +++ b/drivers/gpu/drm/i915/gem/i915_gem_context.c @@ -230,7 +230,7 @@ static void intel_context_set_gem(struct intel_context *ce, ce->timeline = intel_timeline_get(ctx->timeline); if (ctx->sched.priority >= I915_PRIORITY_NORMAL && - intel_engine_has_semaphores(ce->engine)) + intel_engine_has_timeslices(ce->engine)) __set_bit(CONTEXT_USE_SEMAPHORES, &ce->flags); } @@ -1969,7 +1969,7 @@ static int __apply_priority(struct intel_context *ce, void *arg) { struct i915_gem_context *ctx = arg; - if (!intel_engine_has_semaphores(ce->engine)) + if (!intel_engine_has_timeslices(ce->engine)) return 0; if (ctx->sched.priority >= I915_PRIORITY_NORMAL) -- 2.20.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 5+ messages in thread
* [Intel-gfx] [CI 2/2] drm/i915: Avoid using rq->engine after free during i915_fence_release 2020-05-21 14:06 [Intel-gfx] [CI 1/2] drm/i915: Disable semaphore inter-engine sync without timeslicing Chris Wilson @ 2020-05-21 14:06 ` Chris Wilson 2020-05-21 15:44 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/2] drm/i915: Disable semaphore inter-engine sync without timeslicing Patchwork ` (2 subsequent siblings) 3 siblings, 0 replies; 5+ messages in thread From: Chris Wilson @ 2020-05-21 14:06 UTC (permalink / raw) To: intel-gfx In order to be valid to dereference during the i915_fence_release, after retiring the fence and releasing its refererences, we assume that rq->engine can only be a real engine (that stay intact until the device is shutdown after all fences have been flushed). However, due to a quirk of preempt-to-busy, we may retire a request that still belongs to a virtual engine and so eventually free it with rq->engine being invalid. To avoid dereferencing that invalid engine, we look at the execution_mask which if it indicates it may be executed on more than one engine, we know it originated on a virtual engine and may still be on one. Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/1906 Fixes: 43acd6516ca9 ("drm/i915: Keep a per-engine request pool") Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> --- drivers/gpu/drm/i915/i915_request.c | 35 +++++++++++++++++++++++++++-- 1 file changed, 33 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c index 526c1e9acbd5..c282719ad3ac 100644 --- a/drivers/gpu/drm/i915/i915_request.c +++ b/drivers/gpu/drm/i915/i915_request.c @@ -121,8 +121,39 @@ static void i915_fence_release(struct dma_fence *fence) i915_sw_fence_fini(&rq->submit); i915_sw_fence_fini(&rq->semaphore); - /* Keep one request on each engine for reserved use under mempressure */ - if (!cmpxchg(&rq->engine->request_pool, NULL, rq)) + /* + * Keep one request on each engine for reserved use under mempressure + * + * We do not hold a reference to the engine here and so have to be + * very careful in what rq->engine we poke. The virtual engine is + * referenced via the rq->context and we released that ref during + * i915_request_retire(), ergo we must not dereference a virtual + * engine here. Not that we would want to, as the only consumer of + * the reserved engine->request_pool is the power management parking, + * which must-not-fail, and that is only run on the physical engines. + * + * Since the request must have been executed to be have completed, + * we know that it will have been processed by the HW and will + * not be unsubmitted again, so rq->engine and rq->execution_mask + * at this point is stable. rq->execution_mask will be a single + * bit if the last and _only_ engine it could execution on was a + * physical engine, if it's multiple bits then it started on and + * could still be on a virtual engine. Thus if the mask is not a + * power-of-two we assume that rq->engine may still be a virtual + * engine and so a dangling invalid pointer that we cannot dereference + * + * For example, consider the flow of a bonded request through a virtual + * engine. The request is created with a wide engine mask (all engines + * that we might execute on). On processing the bond, the request mask + * is reduced to one or more engines. If the request is subsequently + * bound to a single engine, it will then be constrained to only + * execute on that engine and never returned to the virtual engine + * after timeslicing away, see __unwind_incomplete_requests(). Thus we + * know that if the rq->execution_mask is a single bit, rq->engine + * can be a physical engine with the exact corresponding mask. + */ + if (is_power_of_2(rq->execution_mask) && + !cmpxchg(&rq->engine->request_pool, NULL, rq)) return; kmem_cache_free(global.slab_requests, rq); -- 2.20.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 5+ messages in thread
* [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/2] drm/i915: Disable semaphore inter-engine sync without timeslicing 2020-05-21 14:06 [Intel-gfx] [CI 1/2] drm/i915: Disable semaphore inter-engine sync without timeslicing Chris Wilson 2020-05-21 14:06 ` [Intel-gfx] [CI 2/2] drm/i915: Avoid using rq->engine after free during i915_fence_release Chris Wilson @ 2020-05-21 15:44 ` Patchwork 2020-05-21 16:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2020-05-22 9:36 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork 3 siblings, 0 replies; 5+ messages in thread From: Patchwork @ 2020-05-21 15:44 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: series starting with [CI,1/2] drm/i915: Disable semaphore inter-engine sync without timeslicing URL : https://patchwork.freedesktop.org/series/77512/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.0 Fast mode used, each commit won't be checked separately. - +drivers/gpu/drm/i915/gem/i915_gem_context.c:2274:17: error: bad integer constant expression +drivers/gpu/drm/i915/gem/i915_gem_context.c:2275:17: error: bad integer constant expression +drivers/gpu/drm/i915/gem/i915_gem_context.c:2276:17: error: bad integer constant expression +drivers/gpu/drm/i915/gem/i915_gem_context.c:2277:17: error: bad integer constant expression +drivers/gpu/drm/i915/gem/i915_gem_context.c:2278:17: error: bad integer constant expression +drivers/gpu/drm/i915/gem/i915_gem_context.c:2279:17: error: bad integer constant expression _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [CI,1/2] drm/i915: Disable semaphore inter-engine sync without timeslicing 2020-05-21 14:06 [Intel-gfx] [CI 1/2] drm/i915: Disable semaphore inter-engine sync without timeslicing Chris Wilson 2020-05-21 14:06 ` [Intel-gfx] [CI 2/2] drm/i915: Avoid using rq->engine after free during i915_fence_release Chris Wilson 2020-05-21 15:44 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/2] drm/i915: Disable semaphore inter-engine sync without timeslicing Patchwork @ 2020-05-21 16:05 ` Patchwork 2020-05-22 9:36 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork 3 siblings, 0 replies; 5+ messages in thread From: Patchwork @ 2020-05-21 16:05 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: series starting with [CI,1/2] drm/i915: Disable semaphore inter-engine sync without timeslicing URL : https://patchwork.freedesktop.org/series/77512/ State : success == Summary == CI Bug Log - changes from CI_DRM_8518 -> Patchwork_17751 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/index.html Known issues ------------ Here are the changes found in Patchwork_17751 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@i915_selftest@live@client: - fi-bwr-2160: [PASS][1] -> [INCOMPLETE][2] ([i915#489]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/fi-bwr-2160/igt@i915_selftest@live@client.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/fi-bwr-2160/igt@i915_selftest@live@client.html [i915#489]: https://gitlab.freedesktop.org/drm/intel/issues/489 Participating hosts (47 -> 42) ------------------------------ Missing (5): fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus Build changes ------------- * Linux: CI_DRM_8518 -> Patchwork_17751 CI-20190529: 20190529 CI_DRM_8518: 869a68b66e355733cbebd96443ed56bbf57d7040 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5668: 00d214488f7361c7eceaa8a4a960031f4b467bd5 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_17751: c5572b7c8726df714c8de7e782c57d76c930b6a8 @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == c5572b7c8726 drm/i915: Avoid using rq->engine after free during i915_fence_release 97a3a7ab6a8b drm/i915: Disable semaphore inter-engine sync without timeslicing == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/index.html _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [CI,1/2] drm/i915: Disable semaphore inter-engine sync without timeslicing 2020-05-21 14:06 [Intel-gfx] [CI 1/2] drm/i915: Disable semaphore inter-engine sync without timeslicing Chris Wilson ` (2 preceding siblings ...) 2020-05-21 16:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork @ 2020-05-22 9:36 ` Patchwork 3 siblings, 0 replies; 5+ messages in thread From: Patchwork @ 2020-05-22 9:36 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: series starting with [CI,1/2] drm/i915: Disable semaphore inter-engine sync without timeslicing URL : https://patchwork.freedesktop.org/series/77512/ State : failure == Summary == CI Bug Log - changes from CI_DRM_8518_full -> Patchwork_17751_full ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with Patchwork_17751_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_17751_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. Possible new issues ------------------- Here are the unknown changes that may have been introduced in Patchwork_17751_full: ### IGT changes ### #### Possible regressions #### * igt@gem_eio@in-flight-suspend: - shard-apl: [PASS][1] -> [TIMEOUT][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-apl6/igt@gem_eio@in-flight-suspend.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-apl2/igt@gem_eio@in-flight-suspend.html * igt@kms_plane_scaling@pipe-b-scaler-with-pixel-format: - shard-apl: [PASS][3] -> [FAIL][4] +7 similar issues [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-apl6/igt@kms_plane_scaling@pipe-b-scaler-with-pixel-format.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-apl2/igt@kms_plane_scaling@pipe-b-scaler-with-pixel-format.html Known issues ------------ Here are the changes found in Patchwork_17751_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_ctx_persistence@engines-hostile@rcs0: - shard-iclb: [PASS][5] -> [FAIL][6] ([i915#1622]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-iclb8/igt@gem_ctx_persistence@engines-hostile@rcs0.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-iclb7/igt@gem_ctx_persistence@engines-hostile@rcs0.html - shard-kbl: [PASS][7] -> [FAIL][8] ([i915#1622]) [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-kbl2/igt@gem_ctx_persistence@engines-hostile@rcs0.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-kbl4/igt@gem_ctx_persistence@engines-hostile@rcs0.html * igt@kms_cursor_crc@pipe-a-cursor-64x64-random: - shard-skl: [PASS][9] -> [FAIL][10] ([i915#54]) [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-skl4/igt@kms_cursor_crc@pipe-a-cursor-64x64-random.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-skl9/igt@kms_cursor_crc@pipe-a-cursor-64x64-random.html * igt@kms_cursor_crc@pipe-b-cursor-suspend: - shard-apl: [PASS][11] -> [DMESG-WARN][12] ([i915#180]) [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-apl6/igt@kms_cursor_crc@pipe-b-cursor-suspend.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-apl4/igt@kms_cursor_crc@pipe-b-cursor-suspend.html * igt@kms_cursor_legacy@pipe-c-torture-move: - shard-tglb: [PASS][13] -> [DMESG-WARN][14] ([i915#128]) [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-tglb1/igt@kms_cursor_legacy@pipe-c-torture-move.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-tglb3/igt@kms_cursor_legacy@pipe-c-torture-move.html * igt@kms_hdr@bpc-switch-suspend: - shard-kbl: [PASS][15] -> [DMESG-WARN][16] ([i915#180]) +1 similar issue [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-kbl6/igt@kms_hdr@bpc-switch-suspend.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-kbl4/igt@kms_hdr@bpc-switch-suspend.html * igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min: - shard-skl: [PASS][17] -> [FAIL][18] ([fdo#108145] / [i915#265]) [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-skl1/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-skl10/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html * igt@kms_psr@psr2_primary_mmap_cpu: - shard-iclb: [PASS][19] -> [SKIP][20] ([fdo#109441]) +1 similar issue [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-iclb1/igt@kms_psr@psr2_primary_mmap_cpu.html * igt@kms_vblank@pipe-b-ts-continuation-idle-hang: - shard-apl: [PASS][21] -> [SKIP][22] ([fdo#109271]) +6 similar issues [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-apl6/igt@kms_vblank@pipe-b-ts-continuation-idle-hang.html [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-apl2/igt@kms_vblank@pipe-b-ts-continuation-idle-hang.html #### Possible fixes #### * {igt@gem_ctx_isolation@preservation-s3@vecs0}: - shard-skl: [INCOMPLETE][23] ([i915#198]) -> [PASS][24] [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-skl10/igt@gem_ctx_isolation@preservation-s3@vecs0.html [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-skl1/igt@gem_ctx_isolation@preservation-s3@vecs0.html * igt@gem_ctx_persistence@engines-hostile@vecs0: - shard-iclb: [FAIL][25] ([i915#1622]) -> [PASS][26] [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-iclb8/igt@gem_ctx_persistence@engines-hostile@vecs0.html [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-iclb7/igt@gem_ctx_persistence@engines-hostile@vecs0.html * {igt@gem_exec_balancer@bonded-true-hang}: - shard-tglb: [TIMEOUT][27] -> [PASS][28] [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-tglb3/igt@gem_exec_balancer@bonded-true-hang.html [28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-tglb2/igt@gem_exec_balancer@bonded-true-hang.html * igt@gem_softpin@noreloc-s3: - shard-skl: [INCOMPLETE][29] ([i915#69]) -> [PASS][30] [29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-skl6/igt@gem_softpin@noreloc-s3.html [30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-skl5/igt@gem_softpin@noreloc-s3.html * igt@i915_suspend@forcewake: - shard-kbl: [DMESG-WARN][31] ([i915#180]) -> [PASS][32] +2 similar issues [31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-kbl1/igt@i915_suspend@forcewake.html [32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-kbl3/igt@i915_suspend@forcewake.html * igt@kms_big_fb@linear-32bpp-rotate-0: - shard-kbl: [FAIL][33] ([i915#1119] / [i915#93] / [i915#95]) -> [PASS][34] [33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-kbl3/igt@kms_big_fb@linear-32bpp-rotate-0.html [34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-kbl7/igt@kms_big_fb@linear-32bpp-rotate-0.html * {igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1}: - shard-skl: [FAIL][35] ([i915#79]) -> [PASS][36] [35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-skl9/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1.html [36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-skl7/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1.html * {igt@kms_flip@flip-vs-suspend-interruptible@c-dp1}: - shard-apl: [DMESG-WARN][37] ([i915#180]) -> [PASS][38] +2 similar issues [37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-apl8/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html [38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-apl2/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html * {igt@kms_flip@plain-flip-fb-recreate@b-edp1}: - shard-skl: [FAIL][39] ([i915#1883]) -> [PASS][40] [39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-skl7/igt@kms_flip@plain-flip-fb-recreate@b-edp1.html [40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-skl8/igt@kms_flip@plain-flip-fb-recreate@b-edp1.html * igt@kms_hdr@bpc-switch-dpms: - shard-skl: [FAIL][41] ([i915#1188]) -> [PASS][42] [41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-skl1/igt@kms_hdr@bpc-switch-dpms.html [42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-skl2/igt@kms_hdr@bpc-switch-dpms.html * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c: - shard-skl: [FAIL][43] ([i915#53]) -> [PASS][44] [43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-skl5/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html [44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-skl7/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html * igt@kms_plane_alpha_blend@pipe-c-coverage-7efc: - shard-skl: [FAIL][45] ([fdo#108145] / [i915#265]) -> [PASS][46] [45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-skl5/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html [46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-skl7/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html * igt@kms_psr@psr2_dpms: - shard-iclb: [SKIP][47] ([fdo#109441]) -> [PASS][48] +1 similar issue [47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-iclb3/igt@kms_psr@psr2_dpms.html [48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-iclb2/igt@kms_psr@psr2_dpms.html #### Warnings #### * igt@kms_content_protection@atomic-dpms: - shard-apl: [FAIL][49] ([fdo#110321] / [fdo#110336]) -> [TIMEOUT][50] ([i915#1319]) [49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-apl7/igt@kms_content_protection@atomic-dpms.html [50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-apl6/igt@kms_content_protection@atomic-dpms.html * igt@kms_content_protection@uevent: - shard-apl: [FAIL][51] ([i915#357] / [i915#95]) -> [FAIL][52] ([i915#357]) [51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-apl6/igt@kms_content_protection@uevent.html [52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-apl2/igt@kms_content_protection@uevent.html * igt@kms_fbcon_fbt@fbc: - shard-apl: [FAIL][53] ([i915#1121] / [i915#95]) -> [FAIL][54] ([i915#1525]) [53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8518/shard-apl6/igt@kms_fbcon_fbt@fbc.html [54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17751/shard-apl2/igt@kms_fbcon_fbt@fbc.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145 [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271 [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441 [fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321 [fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336 [i915#1119]: https://gitlab.freedesktop.org/drm/intel/issues/1119 [i915#1121]: https://gitlab.freedesktop.org/drm/intel/issues/1121 [i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188 [i915#128]: https://gitlab.freedesktop.org/drm/intel/issues/128 [i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319 [i915#1525]: https://gitlab.freedesktop.org/drm/intel/issues/1525 [i915#1622]: https://gitlab.freedesktop.org/drm/intel/issues/1622 [i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180 [i915#1883]: https://gitlab.freedesktop.org/drm/intel/issues/1883 [i915#198]: https://gitlab.freedesktop.org/drm/intel/issues/198 [i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265 [i915#357]: https://gitlab.freedesktop.org/drm/intel/issues/357 [i915#53]: https://gitlab.freedesktop.org/drm/intel/issues/53 [i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54 [i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69 [i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79 [i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93 [i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95 Participating hosts (11 -> 11) ------------------------------ No changes in participating hosts Build changes ------------- * Linux: CI_DRM_8518 -> Patchwork_17751 CI-20190529: 20190529 CI_DRM_8518: 869a68b66e355733cbebd96443ed56bbf57d7040 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5668: 00d214488f7361c7eceaa8a4a960031f4b467bd5 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_17751: c5572b7c8726df714c8de7e782c57d76c930b6a8 @ 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_17751/index.html _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-05-22 9:36 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2020-05-21 14:06 [Intel-gfx] [CI 1/2] drm/i915: Disable semaphore inter-engine sync without timeslicing Chris Wilson 2020-05-21 14:06 ` [Intel-gfx] [CI 2/2] drm/i915: Avoid using rq->engine after free during i915_fence_release Chris Wilson 2020-05-21 15:44 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/2] drm/i915: Disable semaphore inter-engine sync without timeslicing Patchwork 2020-05-21 16:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2020-05-22 9:36 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).