Summary: | [CI] igt@kms_cursor_crc@* - Failed CRC mismatch | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Martin Peres <martin.peres> | ||||||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
Status: | CLOSED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
Severity: | normal | ||||||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||||||
Version: | XOrg git | ||||||||||
Hardware: | Other | ||||||||||
OS: | All | ||||||||||
Whiteboard: | ReadyForDev | ||||||||||
i915 platform: | BXT, GLK | i915 features: | display/Other | ||||||||
Attachments: |
|
Description
Martin Peres
2018-01-15 17:13:38 UTC
Sorry, I forgot to include the backtrace: (kms_cursor_crc:1680) igt-debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file igt_debugfs.c:356: (kms_cursor_crc:1680) igt-debugfs-CRITICAL: Failed assertion: !mismatch Subtest cursor-64x64-suspend failed. This test has failing on GLK QA Tests List: igt@kms_cursor_crc@cursor-128x128-suspend IGT-Version: 1.21-gdd61508 (x86_64) (Linux: 4.16.0-rc1-drm-tip-ww8-commit-337c900+ x86_64) Output: . . . (kms_cursor_crc:1668) igt-debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file igt_debugfs.c:370: (kms_cursor_crc:1668) igt-debugfs-CRITICAL: Failed assertion: !mismatch Subtest cursor-128x128-suspend failed. . . . Created attachment 137507 [details]
otuput
Created attachment 137508 [details]
dmesg
Created attachment 137509 [details]
kernel log
Also seen on APL: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4376/shard-apl4/igt@kms_cursor_crc@cursor-256x256-dpms.html (kms_cursor_crc:1377) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:370: (kms_cursor_crc:1377) igt_debugfs-CRITICAL: Failed assertion: !mismatch Subtest cursor-256x256-dpms failed. We used to see this issue every week, and now we have not seen it in 15 weeks. Closing! |
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.