<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [CI] igt@kms_pipe_crc_basic@* - fail - CRC mismatch" href="https://bugs.freedesktop.org/show_bug.cgi?id=103191#c41">Comment # 41</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [CI] igt@kms_pipe_crc_basic@* - fail - CRC mismatch" href="https://bugs.freedesktop.org/show_bug.cgi?id=103191">bug 103191</a> from <a class="email" href="mailto:harish.chegondi@intel.com" title="harish.chegondi@intel.com">harish.chegondi@intel.com</a> <pre>(In reply to Lakshmi from <a href="show_bug.cgi?id=103191#c40">comment #40</a>) > @Harish, Currently this is an Highest priority bug which needs an update > everyday (SLA for for highest priority bug is 1 day). > > Any updates here? Is the priority and severity correct here? if not can you > update? @Lakshmi, Earlier, I posted a patch to fix these CRC failures on BYT Chromebook. The link is posted in <a href="show_bug.cgi?id=103191#c36">comment # 36</a>. The patch was Acked-by: Jani Nikula, but didn't get a Reviewed-by tag. I should have followed up with the reviewers few days later. While the patch skips two invalid CRCs on BYT making the test pass, the underlying problem of why the first two CRCs are invalid still needs to be investigated which I think is a bigger problem. So, my patch is kind of a workaround on top of already existing workarounds in the code. May be I should rebase my patch on drm-tip and re-send the patch to bring up the discussion again on the mailing list. This bug should have similar priority (medium) to the other CRC mismatch bugs and all CRC mismatch bugs should be under this parent CRC mismatch bug: Bug 105978 - [META] CRC mismatch.</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>