https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_129/fi-bxt-dsi/igt@kms_atomic_transition@1x-modeset-transitions.html Starting subtest: 1x-modeset-transitions (kms_atomic_transition:1314) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:392: (kms_atomic_transition:1314) igt_debugfs-CRITICAL: Failed assertion: !mismatch Subtest 1x-modeset-transitions failed.
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4683/shard-skl6/igt@kms_atomic_transition@1x-modeset-transitions.html Starting subtest: 1x-modeset-transitions (kms_atomic_transition:1231) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:392: (kms_atomic_transition:1231) igt_debugfs-CRITICAL: Failed assertion: !mismatch Subtest 1x-modeset-transitions failed.
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4995/shard-skl6/igt@kms_atomic_transition@1x-modeset-transitions-fencing.html Starting subtest: 1x-modeset-transitions-fencing (kms_atomic_transition:1340) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:392: (kms_atomic_transition:1340) igt_debugfs-CRITICAL: Failed assertion: !mismatch Subtest 1x-modeset-transitions-fencing failed.
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5054/shard-kbl4/igt@kms_atomic_transition@1x-modeset-transitions-nonblocking-fencing.html Starting subtest: 1x-modeset-transitions-nonblocking-fencing (kms_atomic_transition:1117) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:419: (kms_atomic_transition:1117) igt_debugfs-CRITICAL: Failed assertion: !mismatch Subtest 1x-modeset-transitions-nonblocking-fencing failed.
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_150/fi-whl-u/igt@kms_atomic_transition@1x-modeset-transitions-nonblocking.html Starting subtest: 1x-modeset-transitions-nonblocking (kms_atomic_transition:1630) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:419: (kms_atomic_transition:1630) igt_debugfs-CRITICAL: Failed assertion: !mismatch Subtest 1x-modeset-transitions-nonblocking failed.
A CI Bug Log filter associated to this bug has been updated: {- BXT SKL KBL WHL: igt@kms_atomic_transition@1x-modeset-transitions-* - fail - Failed assertion: !mismatch -} {+ BYT BXT SKL KBL GLK WHL: igt@kms_atomic_transition@1x-modeset-transitions-* - fail - Failed assertion: !mismatch +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_253/fi-byt-clapper/igt@kms_atomic_transition@1x-modeset-transitions.html
A CI Bug Log filter associated to this bug has been updated: {- BYT BXT SKL KBL GLK WHL: igt@kms_atomic_transition@1x-modeset-transitions-* - fail - Failed assertion: !mismatch -} {+ BYT BXT SKL KBL GLK WHL: igt@kms_atomic_transition@(1|2)x-modeset-transitions-* - fail - Failed assertion: !mismatch +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_292/fi-icl-u3/igt@kms_atomic_transition@2x-modeset-transitions.html
A CI Bug Log filter associated to this bug has been updated: {- BYT BXT SKL KBL GLK WHL: igt@kms_atomic_transition@(1|2)x-modeset-transitions-* - fail - Failed assertion: !mismatch -} {+ BYT BXT SKL KBL GLK WHL ICL: igt@kms_atomic_transition@(1|2)x-modeset-transitions-* - fail - Failed assertion: !mismatch +} No new failures caught with the new filter
The test case checks if all possible plane combination transitions work as expected. Initially it determines the maximum amount of planes on each pipe by using try_commit, then checks all possible plane transitions. The crc mismatches can be related to bandwidth/watermark issue when we are testing maximum amount of planes per pipe with 4K resolution.
94% of the failures are occurring on SKL and these failures on SKL used to occur on every run till CI_DRM_5776. But last seen on SKL is (2 months, 1 week old). This concludes that this issue is fixed on SKL. 5% of the failures are on BYT where the reproduction rate is once in 6 8 drmtip runs and last seen on BYT is drmtip 270. 1% on ICL, occurred only once (drmtip_292).
The worst possible outcome would be corrupt/flickering picture.
A CI Bug Log filter associated to this bug has been updated: {- BYT BXT SKL KBL GLK WHL ICL: igt@kms_atomic_transition@(1|2)x-modeset-transitions-* - fail - Failed assertion: !mismatch -} {+ BYT BXT SKL KBL GLK WHL ICL: igt@kms_atomic_transition@(1|2|3)x-modeset-transitions-* - fail - Failed assertion: !mismatch +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_299/fi-icl-u3/igt@kms_atomic_transition@3x-modeset-transitions-fencing.html
Stan's and Lakshmi's assessment looks correct. The reproduction history of this bug is quite interesting. We had a short period where the issue was seen every 4 runs on icl-u3 but it's gone now for 12 runs. Still 28 more runs to assume it may have been fixed. There was also a period where byt-clapper was failing consistently about a month ago. The following 40 drm-tip runs came out clean. This seems fixed. The issue was not seen on any shards since 3 months ago. I am taking off the bug off BYT platform and adding ICL for now.
Still not seen on ICL at drmtip-321. Lowering priority while we continue to watch this until drmtip-339, when we should be able to close if no reproduction occurs
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/176.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.