<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@kms_flip_tiling@flip-to-x-tiled - fail - Failed assertion: !mismatch" href="https://bugs.freedesktop.org/show_bug.cgi?id=108134#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@kms_flip_tiling@flip-to-x-tiled - fail - Failed assertion: !mismatch" href="https://bugs.freedesktop.org/show_bug.cgi?id=108134">bug 108134</a> from <a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> Martin Peres</a> <pre>(In reply to Daniel Vetter from <a href="show_bug.cgi?id=108134#c7">comment #7</a>) > 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).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>