https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4664/shard-skl5/igt@kms_flip_tiling@flip-changes-tiling-yf.html https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4664/shard-skl9/igt@kms_pwrite_crc.html https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4664/shard-skl9/igt@kms_mmap_write_crc.html https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4664/shard-skl7/igt@kms_color@pipe-c-gamma.html https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4664/shard-skl9/igt@kms_atomic_transition@1x-modeset-transitions-nonblocking.html Starting subtest: 1x-modeset-transitions-nonblocking (kms_atomic_transition:1103) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:392: (kms_atomic_transition:1103) igt_debugfs-CRITICAL: Failed assertion: !mismatch Subtest 1x-modeset-transitions-nonblocking failed. I am filing one single bug because all of these failed only once on the same run, and not after... This seems super suspicious.
The original logs for this bug aren't available anymore, but based on the description is sounds like CRC's just completely stopped working properly on one specific run at the time this was filed (which is indeed very suspicious). Looking through the CI bug log results, it doesn't appear that we've had another instance of everything breaking at once. The buglog filter for this ticket is currently matching any kind of CRC mismatch that happens on a SKL platform, which is probably catching things that really should be broken out into separate bugs that can be analyzed independently. Going through the recent failures caught by the filter I see: * failures of igt@kms_flip_tiling@flip-changes-tiling-yf used to happen periodically, but those are now captured more precisely by bug 108303 (CI issue 786) * failures of igt@kms_atomic_transition@1x-modeset-transitions-nonblocking happened six months ago, but should probably be re-assigned to bug 105703 (CI issue 284) instead of this one. * failures for kms_color@pipe-[abc]-gamma (most recent 6 months ago), but should be re-assigned to bug 104782 (CI issue 185), although it sounds like that bug itself may need to be split into separate ICL and non-ICL bugs * kms_mmap_write_crc --- same story; see fdo bug 103286 Given that we only seem to be catching items that should really be picked up by the filters for other defects, I think it makes sense to close down this bug so that we'll have more fine-grained bug filtering for CRC mismatches on SKL.
(In reply to Matt Roper from comment #1) > The original logs for this bug aren't available anymore, but based on the > description is sounds like CRC's just completely stopped working properly on > one specific run at the time this was filed (which is indeed very > suspicious). Looking through the CI bug log results, it doesn't appear that > we've had another instance of everything breaking at once. > > The buglog filter for this ticket is currently matching any kind of CRC > mismatch that happens on a SKL platform, which is probably catching things > that really should be broken out into separate bugs that can be analyzed > independently. Going through the recent failures caught by the filter I see: > * failures of igt@kms_flip_tiling@flip-changes-tiling-yf used to happen > periodically, but those are now captured more precisely by bug 108303 (CI > issue 786) > * failures of igt@kms_atomic_transition@1x-modeset-transitions-nonblocking > happened six months ago, but should probably be re-assigned to bug 105703 > (CI issue 284) instead of this one. > * failures for kms_color@pipe-[abc]-gamma (most recent 6 months ago), but > should be re-assigned to bug 104782 (CI issue 185), although it sounds like > that bug itself may need to be split into separate ICL and non-ICL bugs > * kms_mmap_write_crc --- same story; see fdo bug 103286 > > Given that we only seem to be catching items that should really be picked up > by the filters for other defects, I think it makes sense to close down this > bug so that we'll have more fine-grained bug filtering for CRC mismatches on > SKL. Thanks for looking in to this bug. I have updated CI bug log filters so that all the failures in this bug are split in to 108303, 105703, 104782, 103286 and 107805. Closing and archiving this bug.
The CI Bug Log issue associated to this bug has been archived. New failures matching the above filters will not be associated to this bug anymore.
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.