* [PATCH i-g-t] i915/gem_ctx_engine: Prevent preemption
@ 2019-06-18 20:21 Chris Wilson
2019-06-18 21:07 ` ✓ Fi.CI.BAT: success for " Patchwork
` (2 more replies)
0 siblings, 3 replies; 7+ messages in thread
From: Chris Wilson @ 2019-06-18 20:21 UTC (permalink / raw)
To: intel-gfx
In order to pin the engine as busy, we have to prevent the kernel from
executing other independent work ahead of our plug, so tell the spinner
to not allow preemption.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
---
tests/i915/gem_ctx_engines.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tests/i915/gem_ctx_engines.c b/tests/i915/gem_ctx_engines.c
index 3ecade417..d47cbdd7c 100644
--- a/tests/i915/gem_ctx_engines.c
+++ b/tests/i915/gem_ctx_engines.c
@@ -283,7 +283,8 @@ static void execute_one(int i915)
spin = igt_spin_new(i915,
.ctx = param.ctx_id,
- .engine = 0);
+ .engine = 0,
+ .flags = IGT_SPIN_NO_PREEMPTION);
igt_debug("Testing with map of %d engines\n", i + 1);
memset(&engines.engines, -1, sizeof(engines.engines));
--
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] 7+ messages in thread* ✓ Fi.CI.BAT: success for i915/gem_ctx_engine: Prevent preemption 2019-06-18 20:21 [PATCH i-g-t] i915/gem_ctx_engine: Prevent preemption Chris Wilson @ 2019-06-18 21:07 ` Patchwork 2019-06-19 6:32 ` [PATCH i-g-t] " Tvrtko Ursulin 2019-06-19 16:06 ` ✓ Fi.CI.IGT: success for " Patchwork 2 siblings, 0 replies; 7+ messages in thread From: Patchwork @ 2019-06-18 21:07 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: i915/gem_ctx_engine: Prevent preemption URL : https://patchwork.freedesktop.org/series/62342/ State : success == Summary == CI Bug Log - changes from CI_DRM_6299 -> IGTPW_3174 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://patchwork.freedesktop.org/api/1.0/series/62342/revisions/1/mbox/ Known issues ------------ Here are the changes found in IGTPW_3174 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_basic@create-fd-close: - fi-icl-u3: [PASS][1] -> [DMESG-WARN][2] ([fdo#107724]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/fi-icl-u3/igt@gem_basic@create-fd-close.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/fi-icl-u3/igt@gem_basic@create-fd-close.html * igt@gem_ctx_switch@basic-default: - fi-icl-guc: [PASS][3] -> [INCOMPLETE][4] ([fdo#107713] / [fdo#108569]) [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/fi-icl-guc/igt@gem_ctx_switch@basic-default.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/fi-icl-guc/igt@gem_ctx_switch@basic-default.html #### Possible fixes #### * igt@gem_cpu_reloc@basic: - fi-icl-dsi: [INCOMPLETE][5] ([fdo#107713] / [fdo#110246]) -> [PASS][6] [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/fi-icl-dsi/igt@gem_cpu_reloc@basic.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/fi-icl-dsi/igt@gem_cpu_reloc@basic.html * igt@gem_sync@basic-store-each: - fi-kbl-7567u: [FAIL][7] -> [PASS][8] [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/fi-kbl-7567u/igt@gem_sync@basic-store-each.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/fi-kbl-7567u/igt@gem_sync@basic-store-each.html * igt@i915_module_load@reload: - fi-blb-e6850: [INCOMPLETE][9] ([fdo#107718]) -> [PASS][10] [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/fi-blb-e6850/igt@i915_module_load@reload.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/fi-blb-e6850/igt@i915_module_load@reload.html * igt@i915_pm_rpm@module-reload: - fi-skl-6770hq: [FAIL][11] ([fdo#108511]) -> [PASS][12] [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html * igt@kms_frontbuffer_tracking@basic: - fi-hsw-peppy: [DMESG-WARN][13] ([fdo#102614]) -> [PASS][14] [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html - fi-icl-u3: [FAIL][15] ([fdo#103167]) -> [PASS][16] [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/fi-icl-u3/igt@kms_frontbuffer_tracking@basic.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/fi-icl-u3/igt@kms_frontbuffer_tracking@basic.html [fdo#102614]: https://bugs.freedesktop.org/show_bug.cgi?id=102614 [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167 [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718 [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724 [fdo#108511]: https://bugs.freedesktop.org/show_bug.cgi?id=108511 [fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569 [fdo#110246]: https://bugs.freedesktop.org/show_bug.cgi?id=110246 Participating hosts (44 -> 35) ------------------------------ Additional (1): fi-bdw-5557u Missing (10): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-icl-u2 fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus fi-snb-2600 Build changes ------------- * IGT: IGT_5059 -> IGTPW_3174 CI_DRM_6299: 2a6cf9f4dc05b77beab4b7d9d1c9f16c7e55a001 @ git://anongit.freedesktop.org/gfx-ci/linux IGTPW_3174: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/ IGT_5059: 1f67ee0d09d6513f487f2be74aae9700e755258a @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/ _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH i-g-t] i915/gem_ctx_engine: Prevent preemption 2019-06-18 20:21 [PATCH i-g-t] i915/gem_ctx_engine: Prevent preemption Chris Wilson 2019-06-18 21:07 ` ✓ Fi.CI.BAT: success for " Patchwork @ 2019-06-19 6:32 ` Tvrtko Ursulin 2019-06-19 8:34 ` Chris Wilson 2019-06-19 16:06 ` ✓ Fi.CI.IGT: success for " Patchwork 2 siblings, 1 reply; 7+ messages in thread From: Tvrtko Ursulin @ 2019-06-19 6:32 UTC (permalink / raw) To: Chris Wilson, intel-gfx On 18/06/2019 21:21, Chris Wilson wrote: > In order to pin the engine as busy, we have to prevent the kernel from > executing other independent work ahead of our plug, so tell the spinner > to not allow preemption. > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > --- > tests/i915/gem_ctx_engines.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/tests/i915/gem_ctx_engines.c b/tests/i915/gem_ctx_engines.c > index 3ecade417..d47cbdd7c 100644 > --- a/tests/i915/gem_ctx_engines.c > +++ b/tests/i915/gem_ctx_engines.c > @@ -283,7 +283,8 @@ static void execute_one(int i915) > > spin = igt_spin_new(i915, > .ctx = param.ctx_id, > - .engine = 0); > + .engine = 0, > + .flags = IGT_SPIN_NO_PREEMPTION); > > igt_debug("Testing with map of %d engines\n", i + 1); > memset(&engines.engines, -1, sizeof(engines.engines)); > The no-op batch preempts the spinner? How does that affect the busy check on the no-op batch? Regards, Tvrtko _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH i-g-t] i915/gem_ctx_engine: Prevent preemption 2019-06-19 6:32 ` [PATCH i-g-t] " Tvrtko Ursulin @ 2019-06-19 8:34 ` Chris Wilson 2019-06-19 8:44 ` Tvrtko Ursulin 0 siblings, 1 reply; 7+ messages in thread From: Chris Wilson @ 2019-06-19 8:34 UTC (permalink / raw) To: Tvrtko Ursulin, intel-gfx Quoting Tvrtko Ursulin (2019-06-19 07:32:05) > > On 18/06/2019 21:21, Chris Wilson wrote: > > In order to pin the engine as busy, we have to prevent the kernel from > > executing other independent work ahead of our plug, so tell the spinner > > to not allow preemption. > > > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > > --- > > tests/i915/gem_ctx_engines.c | 3 ++- > > 1 file changed, 2 insertions(+), 1 deletion(-) > > > > diff --git a/tests/i915/gem_ctx_engines.c b/tests/i915/gem_ctx_engines.c > > index 3ecade417..d47cbdd7c 100644 > > --- a/tests/i915/gem_ctx_engines.c > > +++ b/tests/i915/gem_ctx_engines.c > > @@ -283,7 +283,8 @@ static void execute_one(int i915) > > > > spin = igt_spin_new(i915, > > .ctx = param.ctx_id, > > - .engine = 0); > > + .engine = 0, > > + .flags = IGT_SPIN_NO_PREEMPTION); > > > > igt_debug("Testing with map of %d engines\n", i + 1); > > memset(&engines.engines, -1, sizeof(engines.engines)); > > > > The no-op batch preempts the spinner? How does that affect the busy > check on the no-op batch? We are checking the second batch in the pipeline, expecting it to be blocked by the already executing spinner on the engine of interest. There is no dependency between the two batches, just order of submission, hence the kernel ends up executing the second no-op batch after the first batch's timeslice expired. -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH i-g-t] i915/gem_ctx_engine: Prevent preemption 2019-06-19 8:34 ` Chris Wilson @ 2019-06-19 8:44 ` Tvrtko Ursulin 2019-06-19 8:46 ` Chris Wilson 0 siblings, 1 reply; 7+ messages in thread From: Tvrtko Ursulin @ 2019-06-19 8:44 UTC (permalink / raw) To: Chris Wilson, intel-gfx On 19/06/2019 09:34, Chris Wilson wrote: > Quoting Tvrtko Ursulin (2019-06-19 07:32:05) >> >> On 18/06/2019 21:21, Chris Wilson wrote: >>> In order to pin the engine as busy, we have to prevent the kernel from >>> executing other independent work ahead of our plug, so tell the spinner >>> to not allow preemption. >>> >>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> >>> --- >>> tests/i915/gem_ctx_engines.c | 3 ++- >>> 1 file changed, 2 insertions(+), 1 deletion(-) >>> >>> diff --git a/tests/i915/gem_ctx_engines.c b/tests/i915/gem_ctx_engines.c >>> index 3ecade417..d47cbdd7c 100644 >>> --- a/tests/i915/gem_ctx_engines.c >>> +++ b/tests/i915/gem_ctx_engines.c >>> @@ -283,7 +283,8 @@ static void execute_one(int i915) >>> >>> spin = igt_spin_new(i915, >>> .ctx = param.ctx_id, >>> - .engine = 0); >>> + .engine = 0, >>> + .flags = IGT_SPIN_NO_PREEMPTION); >>> >>> igt_debug("Testing with map of %d engines\n", i + 1); >>> memset(&engines.engines, -1, sizeof(engines.engines)); >>> >> >> The no-op batch preempts the spinner? How does that affect the busy >> check on the no-op batch? > > We are checking the second batch in the pipeline, expecting it to be > blocked by the already executing spinner on the engine of interest. > There is no dependency between the two batches, just order of > submission, hence the kernel ends up executing the second no-op batch > after the first batch's timeslice expired. Yes of course.. but even without timeslicing I think we could have this assumption spinner plugs in a lot of places. Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Regards, Tvrtko _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH i-g-t] i915/gem_ctx_engine: Prevent preemption 2019-06-19 8:44 ` Tvrtko Ursulin @ 2019-06-19 8:46 ` Chris Wilson 0 siblings, 0 replies; 7+ messages in thread From: Chris Wilson @ 2019-06-19 8:46 UTC (permalink / raw) To: Tvrtko Ursulin, intel-gfx Quoting Tvrtko Ursulin (2019-06-19 09:44:18) > > On 19/06/2019 09:34, Chris Wilson wrote: > > Quoting Tvrtko Ursulin (2019-06-19 07:32:05) > >> > >> On 18/06/2019 21:21, Chris Wilson wrote: > >>> In order to pin the engine as busy, we have to prevent the kernel from > >>> executing other independent work ahead of our plug, so tell the spinner > >>> to not allow preemption. > >>> > >>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > >>> --- > >>> tests/i915/gem_ctx_engines.c | 3 ++- > >>> 1 file changed, 2 insertions(+), 1 deletion(-) > >>> > >>> diff --git a/tests/i915/gem_ctx_engines.c b/tests/i915/gem_ctx_engines.c > >>> index 3ecade417..d47cbdd7c 100644 > >>> --- a/tests/i915/gem_ctx_engines.c > >>> +++ b/tests/i915/gem_ctx_engines.c > >>> @@ -283,7 +283,8 @@ static void execute_one(int i915) > >>> > >>> spin = igt_spin_new(i915, > >>> .ctx = param.ctx_id, > >>> - .engine = 0); > >>> + .engine = 0, > >>> + .flags = IGT_SPIN_NO_PREEMPTION); > >>> > >>> igt_debug("Testing with map of %d engines\n", i + 1); > >>> memset(&engines.engines, -1, sizeof(engines.engines)); > >>> > >> > >> The no-op batch preempts the spinner? How does that affect the busy > >> check on the no-op batch? > > > > We are checking the second batch in the pipeline, expecting it to be > > blocked by the already executing spinner on the engine of interest. > > There is no dependency between the two batches, just order of > > submission, hence the kernel ends up executing the second no-op batch > > after the first batch's timeslice expired. > > Yes of course.. but even without timeslicing I think we could have this > assumption spinner plugs in a lot of places. Yes. In the places where I've thought about this plugging issue, we issue BIGNUM high priority requests. However, this is the only consistent failure atm, no doubt more will turn up. -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 7+ messages in thread
* ✓ Fi.CI.IGT: success for i915/gem_ctx_engine: Prevent preemption 2019-06-18 20:21 [PATCH i-g-t] i915/gem_ctx_engine: Prevent preemption Chris Wilson 2019-06-18 21:07 ` ✓ Fi.CI.BAT: success for " Patchwork 2019-06-19 6:32 ` [PATCH i-g-t] " Tvrtko Ursulin @ 2019-06-19 16:06 ` Patchwork 2 siblings, 0 replies; 7+ messages in thread From: Patchwork @ 2019-06-19 16:06 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: i915/gem_ctx_engine: Prevent preemption URL : https://patchwork.freedesktop.org/series/62342/ State : success == Summary == CI Bug Log - changes from CI_DRM_6299_full -> IGTPW_3174_full ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://patchwork.freedesktop.org/api/1.0/series/62342/revisions/1/mbox/ Known issues ------------ Here are the changes found in IGTPW_3174_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing: - shard-snb: [PASS][1] -> [DMESG-WARN][2] ([fdo#110789] / [fdo#110913 ]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-snb1/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-snb1/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html * igt@gem_userptr_blits@map-fixed-invalidate-busy: - shard-apl: [PASS][3] -> [DMESG-WARN][4] ([fdo#110913 ]) +3 similar issues [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-apl6/igt@gem_userptr_blits@map-fixed-invalidate-busy.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-apl7/igt@gem_userptr_blits@map-fixed-invalidate-busy.html * igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup: - shard-kbl: [PASS][5] -> [DMESG-WARN][6] ([fdo#110913 ]) +4 similar issues [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-kbl2/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-kbl2/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html * igt@i915_selftest@live_evict: - shard-kbl: [PASS][7] -> [INCOMPLETE][8] ([fdo#103665] / [fdo#110938]) [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-kbl7/igt@i915_selftest@live_evict.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-kbl7/igt@i915_selftest@live_evict.html * igt@i915_suspend@debugfs-reader: - shard-kbl: [PASS][9] -> [INCOMPLETE][10] ([fdo#103665]) [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-kbl7/igt@i915_suspend@debugfs-reader.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-kbl2/igt@i915_suspend@debugfs-reader.html * igt@kms_flip@2x-plain-flip-interruptible: - shard-hsw: [PASS][11] -> [SKIP][12] ([fdo#109271]) +26 similar issues [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-hsw4/igt@kms_flip@2x-plain-flip-interruptible.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-hsw1/igt@kms_flip@2x-plain-flip-interruptible.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt: - shard-kbl: [PASS][13] -> [FAIL][14] ([fdo#103167]) [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-kbl6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-kbl4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-pwrite: - shard-iclb: [PASS][15] -> [FAIL][16] ([fdo#103167]) +8 similar issues [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-iclb7/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-pwrite.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-iclb2/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-pwrite.html * igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a: - shard-snb: [PASS][17] -> [SKIP][18] ([fdo#109271]) +1 similar issue [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-snb6/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-snb7/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a.html * igt@kms_psr@psr2_cursor_plane_onoff: - shard-iclb: [PASS][19] -> [SKIP][20] ([fdo#109441]) +1 similar issue [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-iclb2/igt@kms_psr@psr2_cursor_plane_onoff.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-iclb6/igt@kms_psr@psr2_cursor_plane_onoff.html * igt@kms_vblank@pipe-c-ts-continuation-suspend: - shard-apl: [PASS][21] -> [DMESG-WARN][22] ([fdo#108566]) +2 similar issues [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-apl7/igt@kms_vblank@pipe-c-ts-continuation-suspend.html [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-apl2/igt@kms_vblank@pipe-c-ts-continuation-suspend.html #### Possible fixes #### * igt@gem_mmap_gtt@hang: - shard-kbl: [DMESG-WARN][23] ([fdo#110913 ]) -> [PASS][24] +3 similar issues [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-kbl3/igt@gem_mmap_gtt@hang.html [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-kbl6/igt@gem_mmap_gtt@hang.html * igt@gem_persistent_relocs@forked-thrashing: - shard-apl: [DMESG-WARN][25] ([fdo#110913 ]) -> [PASS][26] +2 similar issues [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-apl3/igt@gem_persistent_relocs@forked-thrashing.html [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-apl5/igt@gem_persistent_relocs@forked-thrashing.html * igt@gem_sync@basic-store-all: - shard-apl: [INCOMPLETE][27] ([fdo#103927]) -> [PASS][28] [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-apl6/igt@gem_sync@basic-store-all.html [28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-apl3/igt@gem_sync@basic-store-all.html * igt@gem_userptr_blits@map-fixed-invalidate-busy-gup: - shard-snb: [DMESG-WARN][29] ([fdo#110913 ]) -> [PASS][30] [29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-snb5/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html [30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-snb2/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html * igt@i915_pm_rpm@universal-planes-dpms: - shard-kbl: [DMESG-WARN][31] ([fdo#103313] / [fdo#105345]) -> [PASS][32] [31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-kbl2/igt@i915_pm_rpm@universal-planes-dpms.html [32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-kbl4/igt@i915_pm_rpm@universal-planes-dpms.html * igt@i915_suspend@fence-restore-untiled: - shard-apl: [DMESG-WARN][33] ([fdo#108566]) -> [PASS][34] +2 similar issues [33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-apl6/igt@i915_suspend@fence-restore-untiled.html [34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-apl3/igt@i915_suspend@fence-restore-untiled.html * igt@kms_cursor_crc@pipe-b-cursor-suspend: - shard-kbl: [INCOMPLETE][35] ([fdo#103665]) -> [PASS][36] [35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-kbl3/igt@kms_cursor_crc@pipe-b-cursor-suspend.html [36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-kbl6/igt@kms_cursor_crc@pipe-b-cursor-suspend.html * igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic: - shard-hsw: [SKIP][37] ([fdo#109271]) -> [PASS][38] +16 similar issues [37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-hsw1/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html [38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-hsw6/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html * igt@kms_flip@flip-vs-suspend: - shard-snb: [INCOMPLETE][39] ([fdo#105411]) -> [PASS][40] [39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-snb1/igt@kms_flip@flip-vs-suspend.html [40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-snb4/igt@kms_flip@flip-vs-suspend.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-plflip-blt: - shard-iclb: [FAIL][41] ([fdo#103167]) -> [PASS][42] +6 similar issues [41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-iclb5/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-plflip-blt.html [42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-plflip-blt.html * igt@kms_plane_lowres@pipe-a-tiling-y: - shard-iclb: [FAIL][43] ([fdo#103166]) -> [PASS][44] [43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-iclb5/igt@kms_plane_lowres@pipe-a-tiling-y.html [44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-iclb5/igt@kms_plane_lowres@pipe-a-tiling-y.html * igt@kms_psr2_su@page_flip: - shard-iclb: [SKIP][45] ([fdo#109642]) -> [PASS][46] [45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-iclb7/igt@kms_psr2_su@page_flip.html [46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-iclb2/igt@kms_psr2_su@page_flip.html #### Warnings #### * igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend: - shard-snb: [SKIP][47] ([fdo#109271] / [fdo#109278]) -> [SKIP][48] ([fdo#109271]) [47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6299/shard-snb1/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html [48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/shard-snb1/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html [fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166 [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167 [fdo#103313]: https://bugs.freedesktop.org/show_bug.cgi?id=103313 [fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665 [fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927 [fdo#105345]: https://bugs.freedesktop.org/show_bug.cgi?id=105345 [fdo#105411]: https://bugs.freedesktop.org/show_bug.cgi?id=105411 [fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566 [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271 [fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278 [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441 [fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642 [fdo#110789]: https://bugs.freedesktop.org/show_bug.cgi?id=110789 [fdo#110913 ]: https://bugs.freedesktop.org/show_bug.cgi?id=110913 [fdo#110938]: https://bugs.freedesktop.org/show_bug.cgi?id=110938 Participating hosts (10 -> 6) ------------------------------ Missing (4): pig-skl-6260u shard-skl pig-hsw-4770r pig-glk-j5005 Build changes ------------- * IGT: IGT_5059 -> IGTPW_3174 * Piglit: piglit_4509 -> None CI_DRM_6299: 2a6cf9f4dc05b77beab4b7d9d1c9f16c7e55a001 @ git://anongit.freedesktop.org/gfx-ci/linux IGTPW_3174: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/ IGT_5059: 1f67ee0d09d6513f487f2be74aae9700e755258a @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3174/ _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2019-06-19 16:06 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2019-06-18 20:21 [PATCH i-g-t] i915/gem_ctx_engine: Prevent preemption Chris Wilson 2019-06-18 21:07 ` ✓ Fi.CI.BAT: success for " Patchwork 2019-06-19 6:32 ` [PATCH i-g-t] " Tvrtko Ursulin 2019-06-19 8:34 ` Chris Wilson 2019-06-19 8:44 ` Tvrtko Ursulin 2019-06-19 8:46 ` Chris Wilson 2019-06-19 16:06 ` ✓ Fi.CI.IGT: success for " Patchwork
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox