[Intel-gfx] ✗ Fi.CI.BAT: failure for Clean up GuC CI failures, simplify locking, and kernel DOC (rev10)
== Series Details == Series: Clean up GuC CI failures, simplify locking, and kernel DOC (rev10) URL : https://patchwork.freedesktop.org/series/93704/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10550 -> Patchwork_20959 Summary --- **FAILURE** Serious unknown changes coming with Patchwork_20959 absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_20959, 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_20959/index.html Possible new issues --- Here are the unknown changes that may have been introduced in Patchwork_20959: ### IGT changes ### Possible regressions * igt@kms_flip@basic-flip-vs-dpms: - fi-rkl-11600: NOTRUN -> [SKIP][1] +1 similar issue [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20959/fi-rkl-11600/igt@kms_f...@basic-flip-vs-dpms.html * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c: - fi-rkl-11600: [PASS][2] -> [SKIP][3] [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-rkl-11600/igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-c.html [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20959/fi-rkl-11600/igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-c.html New tests - New tests have been introduced between CI_DRM_10550 and Patchwork_20959: ### New IGT tests (1) ### * igt@i915_selftest@live@guc: - Statuses : 37 pass(s) - Exec time: [0.40, 5.01] s Known issues Here are the changes found in Patchwork_20959 that come from known issues: ### IGT changes ### Issues hit * igt@amdgpu/amd_cs_nop@sync-fork-compute0: - fi-snb-2600:NOTRUN -> [SKIP][4] ([fdo#109271]) +17 similar issues [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20959/fi-snb-2600/igt@amdgpu/amd_cs_...@sync-fork-compute0.html * igt@fbdev@write: - fi-rkl-11600: [PASS][5] -> [SKIP][6] ([i915#2582]) +4 similar issues [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-rkl-11600/igt@fb...@write.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20959/fi-rkl-11600/igt@fb...@write.html * igt@i915_pm_rpm@basic-rte: - fi-rkl-11600: [PASS][7] -> [SKIP][8] ([fdo#109308]) +1 similar issue [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-rkl-11600/igt@i915_pm_...@basic-rte.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20959/fi-rkl-11600/igt@i915_pm_...@basic-rte.html * igt@i915_selftest@live@gt_heartbeat: - fi-tgl-y: [PASS][9] -> [DMESG-FAIL][10] ([i915#541]) [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-tgl-y/igt@i915_selftest@live@gt_heartbeat.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20959/fi-tgl-y/igt@i915_selftest@live@gt_heartbeat.html * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic: - fi-rkl-11600: [PASS][11] -> [SKIP][12] ([fdo#111825]) +7 similar issues [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-rkl-11600/igt@kms_cursor_leg...@basic-busy-flip-before-cursor-atomic.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20959/fi-rkl-11600/igt@kms_cursor_leg...@basic-busy-flip-before-cursor-atomic.html * igt@kms_flip@basic-flip-vs-modeset: - fi-rkl-11600: NOTRUN -> [SKIP][13] ([i915#3669]) +2 similar issues [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20959/fi-rkl-11600/igt@kms_f...@basic-flip-vs-modeset.html * igt@kms_frontbuffer_tracking@basic: - fi-rkl-11600: [PASS][14] -> [SKIP][15] ([i915#3180]) [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-rkl-11600/igt@kms_frontbuffer_track...@basic.html [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20959/fi-rkl-11600/igt@kms_frontbuffer_track...@basic.html * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-a: - fi-rkl-11600: [PASS][16] -> [SKIP][17] ([i915#3919]) +9 similar issues [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-rkl-11600/igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-a.html [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20959/fi-rkl-11600/igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-a.html * igt@prime_vgem@basic-fence-flip: - fi-rkl-11600: [PASS][18] -> [SKIP][19] ([i915#1845]) [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-rkl-11600/igt@prime_v...@basic-fence-flip.html [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20959/fi-rkl-11600/igt@prime_v...@basic-fence-flip.html Possible fixes * igt@i915_selftest@live@execlists: - fi-icl-y: [DMESG-FAIL][20]
[Intel-gfx] ✗ Fi.CI.BAT: failure for Clean up GuC CI failures, simplify locking, and kernel DOC (rev9)
== Series Details == Series: Clean up GuC CI failures, simplify locking, and kernel DOC (rev9) URL : https://patchwork.freedesktop.org/series/93704/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10550 -> Patchwork_20956 Summary --- **FAILURE** Serious unknown changes coming with Patchwork_20956 absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_20956, 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_20956/index.html Possible new issues --- Here are the unknown changes that may have been introduced in Patchwork_20956: ### IGT changes ### Possible regressions * igt@kms_flip@basic-flip-vs-dpms: - fi-rkl-11600: NOTRUN -> [SKIP][1] +1 similar issue [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20956/fi-rkl-11600/igt@kms_f...@basic-flip-vs-dpms.html * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c: - fi-rkl-11600: [PASS][2] -> [SKIP][3] [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-rkl-11600/igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-c.html [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20956/fi-rkl-11600/igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-c.html New tests - New tests have been introduced between CI_DRM_10550 and Patchwork_20956: ### New IGT tests (1) ### * igt@i915_selftest@live@guc: - Statuses : 36 pass(s) - Exec time: [0.40, 5.05] s Known issues Here are the changes found in Patchwork_20956 that come from known issues: ### IGT changes ### Issues hit * igt@amdgpu/amd_cs_nop@sync-fork-compute0: - fi-snb-2600:NOTRUN -> [SKIP][4] ([fdo#109271]) +17 similar issues [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20956/fi-snb-2600/igt@amdgpu/amd_cs_...@sync-fork-compute0.html * igt@fbdev@write: - fi-rkl-11600: [PASS][5] -> [SKIP][6] ([i915#2582]) +4 similar issues [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-rkl-11600/igt@fb...@write.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20956/fi-rkl-11600/igt@fb...@write.html * igt@i915_pm_rpm@basic-rte: - fi-rkl-11600: [PASS][7] -> [SKIP][8] ([fdo#109308]) +1 similar issue [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-rkl-11600/igt@i915_pm_...@basic-rte.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20956/fi-rkl-11600/igt@i915_pm_...@basic-rte.html * igt@i915_selftest@live@late_gt_pm: - fi-bsw-nick:[PASS][9] -> [DMESG-FAIL][10] ([i915#2927] / [i915#3428]) [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-bsw-nick/igt@i915_selftest@live@late_gt_pm.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20956/fi-bsw-nick/igt@i915_selftest@live@late_gt_pm.html * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic: - fi-rkl-11600: [PASS][11] -> [SKIP][12] ([fdo#111825]) +7 similar issues [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-rkl-11600/igt@kms_cursor_leg...@basic-busy-flip-before-cursor-atomic.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20956/fi-rkl-11600/igt@kms_cursor_leg...@basic-busy-flip-before-cursor-atomic.html * igt@kms_flip@basic-flip-vs-modeset: - fi-rkl-11600: NOTRUN -> [SKIP][13] ([i915#3669]) +2 similar issues [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20956/fi-rkl-11600/igt@kms_f...@basic-flip-vs-modeset.html * igt@kms_frontbuffer_tracking@basic: - fi-rkl-11600: [PASS][14] -> [SKIP][15] ([i915#3180]) [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-rkl-11600/igt@kms_frontbuffer_track...@basic.html [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20956/fi-rkl-11600/igt@kms_frontbuffer_track...@basic.html * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-a: - fi-rkl-11600: [PASS][16] -> [SKIP][17] ([i915#3919]) +9 similar issues [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-rkl-11600/igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-a.html [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20956/fi-rkl-11600/igt@kms_pipe_crc_ba...@compare-crc-sanitycheck-pipe-a.html * igt@prime_vgem@basic-fence-flip: - fi-rkl-11600: [PASS][18] -> [SKIP][19] ([i915#1845]) [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10550/fi-rkl-11600/igt@prime_v...@basic-fence-flip.html [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20956/fi-rkl-11600/igt@prime_v...@basic-fence-flip.html * igt@runner@aborted: - fi-bsw-nick:NOTRUN -> [FAIL][20] ([fdo#109271] / [i915#1436] /
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Clean up GuC CI failures, simplify locking, and kernel DOC (rev6)
On Thu, Aug 26, 2021 at 04:17:07PM +, Patchwork wrote: > Patch Details > > Series: Clean up GuC CI failures, simplify locking, and kernel DOC (rev6) > URL: https://patchwork.freedesktop.org/series/93704/ > State: failure > Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20904/index.html > > CI Bug Log - changes from CI_DRM_10525 -> Patchwork_20904 > > Summary > > FAILURE > > Serious unknown changes coming with Patchwork_20904 absolutely need to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_20904, 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_20904/ > index.html > > Possible new issues > > Here are the unknown changes that may have been introduced in Patchwork_20904: > > IGT changes > > Possible regressions > > • igt@i915_selftest@live@hangcheck: > □ fi-rkl-guc: PASS -> INCOMPLETE I've seen this locally before and after this series. I wouldn't hold of the merge of this series because of this as I don't believe it is a regression, just an existing instability in the stack. I haven't been able to root cause this yet, but my initial analysis points to the GuC losing a submission after the GuC has reset a context. Will dig into this and hopefully get a fix after I'm back from vacation on 9/7. Matt > > New tests > > New tests have been introduced between CI_DRM_10525 and Patchwork_20904: > > New IGT tests (1) > > • igt@i915_selftest@live@guc: > □ Statuses : 30 pass(s) > □ Exec time: [0.41, 5.26] s > > Known issues > > Here are the changes found in Patchwork_20904 that come from known issues: > > IGT changes > > Issues hit > > • igt@amdgpu/amd_cs_nop@sync-compute0: > > □ fi-kbl-soraka: NOTRUN -> SKIP (fdo#109271) +5 similar issues > • igt@runner@aborted: > > □ fi-rkl-guc: NOTRUN -> FAIL (i915#3928) > > {name}: This element is suppressed. This means it is ignored when computing > the status of the difference (SUCCESS, WARNING, or FAILURE). > > Participating hosts (40 -> 33) > > Missing (7): fi-ilk-m540 bat-adls-5 fi-hsw-4200u fi-tgl-1115g4 fi-bsw-cyan > fi-bdw-samus bat-jsl-1 > > Build changes > > • Linux: CI_DRM_10525 -> Patchwork_20904 > > CI-20190529: 20190529 > CI_DRM_10525: 059309d37ac2de5d93cf6d71fd7fe33c9c2c66ea @ git:// > anongit.freedesktop.org/gfx-ci/linux > IGT_6186: 250081b306c6fa8f95405fab6a7604f1968dd4ec @ https:// > gitlab.freedesktop.org/drm/igt-gpu-tools.git > Patchwork_20904: 0c1d27ac9fce7e231e7dddebcf56905e05302cae @ git:// > anongit.freedesktop.org/gfx-ci/linux > > == Linux commits == > > 0c1d27ac9fce drm/i915/guc: Drop static inline functions intel_guc_submission.c > 50ada01b3d95 drm/i915/guc: Add GuC kernel doc > 883eccfa8221 drm/i915/guc: Drop guc_active move everything into guc_state > fa075902c938 drm/i915/guc: Move fields protected by guc->contexts_lock into > sub > structure > a1c73c8c481a drm/i915/guc: Move GuC priority fields in context under > guc_active > f16c0554ae08 drm/i915/guc: Drop pin count check trick between sched_disable > and > re-pin > 42ac1b77a019 drm/i915/guc: Proper xarray usage for contexts_lookup > 9b9222998c83 drm/i915/guc: Rework and simplify locking > 244934484f63 drm/i915/guc: Move guc_blocked fence to struct guc_state > ba695a58136a drm/i915/guc: Release submit fence from an irq_work > 3bd5803d5e25 drm/i915/guc: Flush G2H work queue during reset > b87ba9121748 drm/i915: Allocate error capture in nowait context > adb35ad83c76 drm/i915/guc: Reset LRC descriptor if register returns -ENODEV > 97e616063006 drm/i915/guc: Don't touch guc_state.sched_state without a lock > 1ff99308ef88 drm/i915/guc: Take context ref when cancelling request > ff84f14ddceb drm/i915/selftests: Add initial GuC selftest for scrubbing lost > G2H > abd6a8884cf4 drm/i915/guc: Copy whole golden context, set engine state size of > subset > a19ba1f51009 drm/i915/guc: Don't enable scheduling on a banned context, guc_id > invalid, not registered > f29b2b338002 drm/i915/guc: Kick tasklet after queuing a request > f577a4fdeeab drm/i915/selftests: Add a cancel request selftest that triggers a > reset > da3d87dfe8c5 Revert "drm/i915/gt: Propagate change in error status to children > on unhold" > 25273a034c8d drm/i915/guc: Workaround reset G2H is received after schedule > done > G2H > c00d543957c2 drm/i915/guc: Process all G2H message at once in work queue > 5b7ff1fa9e43 drm/i915/guc: Don't drop ce->guc_active.lock when unwinding > context > 54cd904fa232 drm/i915/guc: Unwind context requests in reverse order > 593f21493fda drm/i915/guc: Fix outstanding G2H accounting > 6b511953d015 drm/i915/guc: Fix blocked context accounting > > SECURITY NOTE: file ~/.netrc must not be accessible by others
[Intel-gfx] ✗ Fi.CI.BAT: failure for Clean up GuC CI failures, simplify locking, and kernel DOC (rev6)
== Series Details == Series: Clean up GuC CI failures, simplify locking, and kernel DOC (rev6) URL : https://patchwork.freedesktop.org/series/93704/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10525 -> Patchwork_20904 Summary --- **FAILURE** Serious unknown changes coming with Patchwork_20904 absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_20904, 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_20904/index.html Possible new issues --- Here are the unknown changes that may have been introduced in Patchwork_20904: ### IGT changes ### Possible regressions * igt@i915_selftest@live@hangcheck: - fi-rkl-guc: [PASS][1] -> [INCOMPLETE][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10525/fi-rkl-guc/igt@i915_selftest@l...@hangcheck.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20904/fi-rkl-guc/igt@i915_selftest@l...@hangcheck.html New tests - New tests have been introduced between CI_DRM_10525 and Patchwork_20904: ### New IGT tests (1) ### * igt@i915_selftest@live@guc: - Statuses : 30 pass(s) - Exec time: [0.41, 5.26] s Known issues Here are the changes found in Patchwork_20904 that come from known issues: ### IGT changes ### Issues hit * igt@amdgpu/amd_cs_nop@sync-compute0: - fi-kbl-soraka: NOTRUN -> [SKIP][3] ([fdo#109271]) +5 similar issues [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20904/fi-kbl-soraka/igt@amdgpu/amd_cs_...@sync-compute0.html * igt@runner@aborted: - fi-rkl-guc: NOTRUN -> [FAIL][4] ([i915#3928]) [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20904/fi-rkl-guc/igt@run...@aborted.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 [i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982 [i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411 [i915#3928]: https://gitlab.freedesktop.org/drm/intel/issues/3928 Participating hosts (40 -> 33) -- Missing(7): fi-ilk-m540 bat-adls-5 fi-hsw-4200u fi-tgl-1115g4 fi-bsw-cyan fi-bdw-samus bat-jsl-1 Build changes - * Linux: CI_DRM_10525 -> Patchwork_20904 CI-20190529: 20190529 CI_DRM_10525: 059309d37ac2de5d93cf6d71fd7fe33c9c2c66ea @ git://anongit.freedesktop.org/gfx-ci/linux IGT_6186: 250081b306c6fa8f95405fab6a7604f1968dd4ec @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git Patchwork_20904: 0c1d27ac9fce7e231e7dddebcf56905e05302cae @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == 0c1d27ac9fce drm/i915/guc: Drop static inline functions intel_guc_submission.c 50ada01b3d95 drm/i915/guc: Add GuC kernel doc 883eccfa8221 drm/i915/guc: Drop guc_active move everything into guc_state fa075902c938 drm/i915/guc: Move fields protected by guc->contexts_lock into sub structure a1c73c8c481a drm/i915/guc: Move GuC priority fields in context under guc_active f16c0554ae08 drm/i915/guc: Drop pin count check trick between sched_disable and re-pin 42ac1b77a019 drm/i915/guc: Proper xarray usage for contexts_lookup 9b9222998c83 drm/i915/guc: Rework and simplify locking 244934484f63 drm/i915/guc: Move guc_blocked fence to struct guc_state ba695a58136a drm/i915/guc: Release submit fence from an irq_work 3bd5803d5e25 drm/i915/guc: Flush G2H work queue during reset b87ba9121748 drm/i915: Allocate error capture in nowait context adb35ad83c76 drm/i915/guc: Reset LRC descriptor if register returns -ENODEV 97e616063006 drm/i915/guc: Don't touch guc_state.sched_state without a lock 1ff99308ef88 drm/i915/guc: Take context ref when cancelling request ff84f14ddceb drm/i915/selftests: Add initial GuC selftest for scrubbing lost G2H abd6a8884cf4 drm/i915/guc: Copy whole golden context, set engine state size of subset a19ba1f51009 drm/i915/guc: Don't enable scheduling on a banned context, guc_id invalid, not registered f29b2b338002 drm/i915/guc: Kick tasklet after queuing a request f577a4fdeeab drm/i915/selftests: Add a cancel request selftest that triggers a reset da3d87dfe8c5 Revert "drm/i915/gt: Propagate change in error status to children on unhold" 25273a034c8d drm/i915/guc: Workaround reset G2H is received after schedule done G2H c00d543957c2 drm/i915/guc: Process all G2H message at once in work queue 5b7ff1fa9e43 drm/i915/guc: Don't drop ce->guc_active.lock when unwinding context 54cd904fa232 drm/i915/guc: Unwind context requests in reverse order 593f21493fda drm/i915/guc: Fix outstanding G2H
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Clean up GuC CI failures, simplify locking, and kernel DOC
On Sun, Aug 15, 2021 at 09:15:31PM +, Patchwork wrote: > Patch Details > > Series: Clean up GuC CI failures, simplify locking, and kernel DOC > URL: https://patchwork.freedesktop.org/series/93704/ > State: failure > Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20826/index.html > > CI Bug Log - changes from CI_DRM_10484 -> Patchwork_20826 > > Summary > > FAILURE > > Serious unknown changes coming with Patchwork_20826 absolutely need to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_20826, 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_20826/ > index.html > > Possible new issues > > Here are the unknown changes that may have been introduced in Patchwork_20826: > > IGT changes > > Possible regressions > > • igt@i915_selftest@live@requests: > > □ fi-cfl-guc: PASS -> DMESG-FAIL > New selftext, __cancel_reset, is exposing a bug (or at minimum different behavior) in the execlists implementation for canceling requests. Will fix in new rev. Matt > □ fi-kbl-soraka: PASS -> DMESG-FAIL > > □ fi-bxt-dsi: PASS -> DMESG-FAIL > > □ fi-tgl-1115g4: PASS -> DMESG-FAIL > > □ fi-cml-u2: PASS -> DMESG-FAIL > > □ fi-kbl-8809g: PASS -> DMESG-FAIL > > □ fi-cfl-8700k: PASS -> DMESG-FAIL > > □ fi-cfl-8109u: PASS -> DMESG-FAIL > > □ fi-icl-u2: PASS -> DMESG-FAIL > > □ fi-kbl-7500u: PASS -> DMESG-FAIL > > □ fi-bsw-nick: PASS -> DMESG-FAIL > > □ fi-icl-y: PASS -> DMESG-FAIL > > □ fi-kbl-guc: PASS -> DMESG-FAIL > > □ fi-kbl-7567u: PASS -> DMESG-FAIL > > □ fi-skl-guc: PASS -> DMESG-FAIL > > □ fi-bdw-5557u: PASS -> DMESG-FAIL > > □ fi-glk-dsi: PASS -> DMESG-FAIL > > □ fi-bsw-kefka: PASS -> DMESG-FAIL > > □ fi-skl-6700k2: PASS -> DMESG-FAIL > > Warnings > > • igt@i915_selftest@live@workarounds: > □ fi-rkl-guc: DMESG-FAIL (i915#3928) -> INCOMPLETE > > Suppressed > > The following results come from untrusted machines, tests, or statuses. > They do not affect the overall result. > > • igt@i915_selftest@live@requests: > > □ {fi-tgl-dsi}: PASS -> DMESG-FAIL > > □ {fi-jsl-1}: PASS -> DMESG-FAIL > > □ {fi-ehl-2}: PASS -> DMESG-FAIL > > New tests > > New tests have been introduced between CI_DRM_10484 and Patchwork_20826: > > New IGT tests (1) > > • igt@i915_selftest@live@guc: > □ Statuses : 30 pass(s) > □ Exec time: [0.42, 5.06] s > > Known issues > > Here are the changes found in Patchwork_20826 that come from known issues: > > IGT changes > > Issues hit > > • igt@i915_module_load@reload: > > □ fi-kbl-soraka: PASS -> DMESG-WARN (i915#1982) > • igt@i915_selftest@live@execlists: > > □ fi-icl-y: PASS -> DMESG-FAIL (i915#1993) > > Possible fixes > > • igt@i915_module_load@reload: > □ {fi-tgl-dsi}: DMESG-WARN (i915#1982 / k.org#205379) -> PASS > > {name}: This element is suppressed. This means it is ignored when computing > the status of the difference (SUCCESS, WARNING, or FAILURE). > > Participating hosts (37 -> 34) > > Missing (3): fi-bdw-samus fi-bsw-cyan bat-jsl-1 > > Build changes > > • Linux: CI_DRM_10484 -> Patchwork_20826 > > CI-20190529: 20190529 > CI_DRM_10484: 7de02d5cb1f35bd3f068237444063844dea47ddc @ git:// > anongit.freedesktop.org/gfx-ci/linux > IGT_6175: c91f99c74b966f635d7e2eb898bf0f78383d281b @ https:// > gitlab.freedesktop.org/drm/igt-gpu-tools.git > Patchwork_20826: f7ff315bfe3a76713c1f0a16cd92b0908d28e4c6 @ git:// > anongit.freedesktop.org/gfx-ci/linux > > == Linux commits == > > f7ff315bfe3a drm/i915/guc: Add GuC kernel doc > af14e3698d19 drm/i915/guc: Move GuC priority fields in context under > guc_active > eb8a352e7c1f drm/i915/guc: Drop pin count check trick between sched_disable > and > re-pin > 7057a0daff8c drm/i915/guc: Proper xarray usage for contexts_lookup > d97ab34c8bac drm/i915/guc: Rework and simplify locking > 4c980575f7af drm/i915/guc: Move guc_blocked fence to struct guc_state > 1c2b4c0ac62a drm/i915/guc: Release submit fence from an IRQ > 14dc302536e1 drm/i915/guc: Flush G2H work queue during reset > c0ad63d810e6 drm/i915: Allocate error capture in atomic context > 6c1c488a3654 drm/i915/guc: Reset LRC descriptor if register returns -ENODEV > 025e88fa74d3 drm/i915/guc: Don't touch guc_state.sched_state without a lock > b929abcf3b59 drm/i915/guc: Take context ref when cancelling request > b5e8c08dff35 drm/i915/selftests: Add initial GuC selftest for scrubbing lost > G2H > cddf94c9bda0 drm/i915/selftests: Fix memory corruption in live_lrc_isolation > c18da32e671c drm/i915/guc: Don't enable scheduling on a banned context, guc_id > invalid, not registered > 0c0928ba1ba8 drm/i915/selftests: Add a cancel request selftest that
[Intel-gfx] ✗ Fi.CI.BAT: failure for Clean up GuC CI failures, simplify locking, and kernel DOC
== Series Details == Series: Clean up GuC CI failures, simplify locking, and kernel DOC URL : https://patchwork.freedesktop.org/series/93704/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10484 -> Patchwork_20826 Summary --- **FAILURE** Serious unknown changes coming with Patchwork_20826 absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_20826, 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_20826/index.html Possible new issues --- Here are the unknown changes that may have been introduced in Patchwork_20826: ### IGT changes ### Possible regressions * igt@i915_selftest@live@requests: - fi-cfl-guc: [PASS][1] -> [DMESG-FAIL][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10484/fi-cfl-guc/igt@i915_selftest@l...@requests.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20826/fi-cfl-guc/igt@i915_selftest@l...@requests.html - fi-kbl-soraka: [PASS][3] -> [DMESG-FAIL][4] [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10484/fi-kbl-soraka/igt@i915_selftest@l...@requests.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20826/fi-kbl-soraka/igt@i915_selftest@l...@requests.html - fi-bxt-dsi: [PASS][5] -> [DMESG-FAIL][6] [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10484/fi-bxt-dsi/igt@i915_selftest@l...@requests.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20826/fi-bxt-dsi/igt@i915_selftest@l...@requests.html - fi-tgl-1115g4: [PASS][7] -> [DMESG-FAIL][8] [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10484/fi-tgl-1115g4/igt@i915_selftest@l...@requests.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20826/fi-tgl-1115g4/igt@i915_selftest@l...@requests.html - fi-cml-u2: [PASS][9] -> [DMESG-FAIL][10] [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10484/fi-cml-u2/igt@i915_selftest@l...@requests.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20826/fi-cml-u2/igt@i915_selftest@l...@requests.html - fi-kbl-8809g: [PASS][11] -> [DMESG-FAIL][12] [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10484/fi-kbl-8809g/igt@i915_selftest@l...@requests.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20826/fi-kbl-8809g/igt@i915_selftest@l...@requests.html - fi-cfl-8700k: [PASS][13] -> [DMESG-FAIL][14] [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10484/fi-cfl-8700k/igt@i915_selftest@l...@requests.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20826/fi-cfl-8700k/igt@i915_selftest@l...@requests.html - fi-cfl-8109u: [PASS][15] -> [DMESG-FAIL][16] [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10484/fi-cfl-8109u/igt@i915_selftest@l...@requests.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20826/fi-cfl-8109u/igt@i915_selftest@l...@requests.html - fi-icl-u2: [PASS][17] -> [DMESG-FAIL][18] [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10484/fi-icl-u2/igt@i915_selftest@l...@requests.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20826/fi-icl-u2/igt@i915_selftest@l...@requests.html - fi-kbl-7500u: [PASS][19] -> [DMESG-FAIL][20] [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10484/fi-kbl-7500u/igt@i915_selftest@l...@requests.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20826/fi-kbl-7500u/igt@i915_selftest@l...@requests.html - fi-bsw-nick:[PASS][21] -> [DMESG-FAIL][22] [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10484/fi-bsw-nick/igt@i915_selftest@l...@requests.html [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20826/fi-bsw-nick/igt@i915_selftest@l...@requests.html - fi-icl-y: [PASS][23] -> [DMESG-FAIL][24] [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10484/fi-icl-y/igt@i915_selftest@l...@requests.html [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20826/fi-icl-y/igt@i915_selftest@l...@requests.html - fi-kbl-guc: [PASS][25] -> [DMESG-FAIL][26] [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10484/fi-kbl-guc/igt@i915_selftest@l...@requests.html [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20826/fi-kbl-guc/igt@i915_selftest@l...@requests.html - fi-kbl-7567u: [PASS][27] -> [DMESG-FAIL][28] [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10484/fi-kbl-7567u/igt@i915_selftest@l...@requests.html [28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20826/fi-kbl-7567u/igt@i915_selftest@l...@requests.html - fi-skl-guc: [PASS][29] -> [DMESG-FAIL][30] [29]: