Bug 108134

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4981/shard-skl3/igt@kms_flip_tiling@flip-to-x-tiled.html

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4677/shard-skl3/igt@kms_flip_tiling@flip-to-x-tiled.html

Starting subtest: flip-to-X-tiled
(kms_flip_tiling:975) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:392:
(kms_flip_tiling:975) igt_debugfs-CRITICAL: Failed assertion: !mismatch
Subtest flip-to-X-tiled failed.

KBL results are here
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_133/fi-kbl-soraka/igt@kms_flip_tiling@flip-to-x-tiled.html

Starting subtest: flip-to-X-tiled
(kms_flip_tiling:1192) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:392:
(kms_flip_tiling:1192) igt_debugfs-CRITICAL: Failed assertion: !mismatch
Subtest flip-to-X-tiled failed.

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_134/fi-icl-u/igt@kms_flip_tiling@flip-to-x-tiled.html

Starting subtest: flip-to-X-tiled
(kms_flip_tiling:2755) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:419:
(kms_flip_tiling:2755) igt_debugfs-CRITICAL: Failed assertion: !mismatch
Subtest flip-to-X-tiled failed.

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_142/fi-byt-clapper/igt@kms_flip_tiling@flip-to-x-tiled.html

Starting subtest: flip-to-X-tiled
(kms_flip_tiling:1323) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:419:
(kms_flip_tiling:1323) igt_debugfs-CRITICAL: Failed assertion: !mismatch
Subtest flip-to-X-tiled failed.

This seems similar as for example the following bugs with failure crc mismatch

https://bugs.freedesktop.org/show_bug.cgi?id=103166
https://bugs.freedesktop.org/show_bug.cgi?id=103191

Maybe we could mark these as duplicates even though bug #103166 is tagged to CFL?

Assigning this bug to myself

Note that the history of this tests was because the old command submission page flip could change tiling (but not much else). With atomic this is all done by the atomic pageflip code, so might indicate some larger issue with atomic flips.

Seems like we have a similar filing for Y and Yf tilings:
https://bugs.freedesktop.org/show_bug.cgi?id=107931

Same, very low, reproduction rate and the issue seems to be as elusive. We should probably combine those.

(In reply to Daniel Vetter from comment #7)
> Note that the history of this tests was because the old command submission
> page flip could change tiling (but not much else). With atomic this is all
> done by the atomic pageflip code, so might indicate some larger issue with
> atomic flips.

The reproduction rate does not look uniform, which could indicate that the ordering of the test is somewhat important, meaning that one test would leak some state onto the other one.

I suggest using cibuglog's Known Failure view with the following "issue_id=775 AND machine_tag = 'ICL'" query in order to start investigating this issue, looking at which tests were executed in the shard, but bear in mind that shards machines do not always reboot between shards, inside the same run (so also check the tests executed in the previous shard ids). Enjoy!

As for the customer impact, as per Daniel's comment, this might lead to flickering or garbled display, which would make the computer unusable depending on the tiling format of the framebuffer (expected to be stable between driver updates).

*** Bug 107931 has been marked as a duplicate of this bug. ***

A CI Bug Log filter associated to this bug has been updated:

{- BYT BDW SKL KBL ICL: igt@kms_flip_tiling@flip-to-x-tiled - fail - Failed assertion: !mismatch -}
{+ BYT BDW SKL KBL ICL: igt@kms_flip_tiling@flip-to-(x|y|yf)-tiled - fail - Failed assertion: !mismatch +}

 No new failures caught with the new filter

A CI Bug Log filter associated to this bug has been updated:

{- BYT BDW SKL KBL ICL: igt@kms_flip_tiling@flip-to-(x|y|yf)-tiled - fail - Failed assertion: !mismatch -}
{+ BYT BDW SKL KBL WHL ICL: igt@kms_flip_tiling@flip-to-(x|y|yf)-tiled - fail - Failed assertion: !mismatch +}

 No new failures caught with the new filter

A CI Bug Log filter associated to this bug has been updated:

{- BYT BDW SKL KBL WHL ICL: igt@kms_flip_tiling@flip-to-(x|y|yf)-tiled - fail - Failed assertion: !mismatch -}
{+ BYT BDW SKL KBL GLK WHL ICL: igt@kms_flip_tiling@flip-to-(x|y|yf)-tiled - fail - Failed assertion: !mismatch +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_252/fi-glk-dsi/igt@kms_flip_tiling@flip-to-yf-tiled.html

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_253/fi-glk-dsi/igt@kms_flip_tiling@flip-to-x-tiled.html

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_254/fi-glk-dsi/igt@kms_flip_tiling@flip-to-x-tiled.html

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_255/fi-glk-dsi/igt@kms_flip_tiling@flip-to-yf-tiled.html

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_255/fi-glk-dsi/igt@kms_flip_tiling@flip-to-x-tiled.html

The test is failing when trying to flip from tiling none to x, y, or yf tiling.

The worst case scenario for user perspective is corrupted screen when tiling fails to produce correct image.

#assessment

This issue now seen last time 3 weeks ago. So I guess we could lower priority.

Not seen now ~2 weeks, BIOS was updated on shards, I guess lowering priority this would be right measure

(In reply to Jani Saarinen from comment #16)
> Not seen now ~2 weeks, BIOS was updated on shards, I guess lowering priority
> this would be right measure

This occurred one day ago 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6113/shard-iclb8/igt@kms_flip_tiling@flip-to-x-tiled.html

With the best known BIOS version?

Currently, we have BIOS ICLSFWR1.R00.3175.A00.1904261428 04/26/2019

latest we have is: R00.3183. That is partly updated on shards too.

This hasn't been seen in last 66 runs. Can we close this bug?

Dropping priority due to low reproducible rate .

-- 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/167.