Summary: | [CI][SHARDS] igt@kms_* - fail - Failed assertion: !mismatch | ||
---|---|---|---|
Product: | DRI | Reporter: | Martin Peres <martin.peres> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | RESOLVED MOVED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | high | CC: | intel-gfx-bugs, matthew.d.roper |
Version: | XOrg git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | BYT, SKL | i915 features: | display/Other |
Description
Martin Peres
2018-09-03 15:23:52 UTC
Also seen on SKL: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4984/shard-skl6/igt@kms_atomic_transition@1x-modeset-transitions.html Starting subtest: 1x-modeset-transitions (kms_atomic_transition:1239) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:392: (kms_atomic_transition:1239) igt_debugfs-CRITICAL: Failed assertion: !mismatch (kms_atomic_transition:1239) igt_debugfs-CRITICAL: Last errno: 25, Inappropriate ioctl for device Subtest 1x-modeset-transitions failed. A CI Bug Log filter associated to this bug has been updated: {- BYT SKL: all tests - fail - Failed assertion: !mismatch, Last errno: 25, Inappropriate ioctl for device -} {+ BYT SKL: all tests - fail - Failed assertion: !mismatch +} No new failures caught with the new filter We should probably update the CIbuglog filter for this defect; there are some seemingly legitimate CRC mismatches here, but they're lost in the noise due to a huge number of hits for kms_plane_alpha_blend on gen9. Due to a hardware defect in plane blending, those blending tests are expected to fail on all gen9 platforms. It might be worth adding some kind of debugfs node that indicates whether plane blending is broken; kms_plane_alpha_blend could use that as a hint on whether to skip those tests or not. -- 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/153. |
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.