<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI] igt@kms_color@pipe-[abc]-*gamma - fail - CRC mismatch"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104782#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI] igt@kms_color@pipe-[abc]-*gamma - fail - CRC mismatch"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104782">bug 104782</a>
from <span class="vcard"><a class="email" href="mailto:cibuglog@gmail.com" title="CI Bug Log <cibuglog@gmail.com>"> <span class="fn">CI Bug Log</span></a>
</span></b>
<pre>A CI Bug Log filter associated to this bug has been updated:
{- BSW BXT APL SKL KBL GLK CFL WHL ICL: igt@kms_color@pipe-[abc]-*gamma* -
Failed assertion: !mismatch -}
{+ BYT BSW BXT APL SKL KBL GLK CFL WHL ICL: igt@kms_color@pipe-[abc]-*gamma* -
Failed assertion: !mismatch +}
New failures caught by the filter:
*
<a href="https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_249/fi-byt-clapper/igt@kms_color@pipe-a-legacy-gamma.html">https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_249/fi-byt-clapper/igt@kms_color@pipe-a-legacy-gamma.html</a></pre>
</div>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI] igt@kms_color@pipe-[abc]-*gamma - fail - CRC mismatch"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104782#c15">Comment # 15</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI] igt@kms_color@pipe-[abc]-*gamma - fail - CRC mismatch"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104782">bug 104782</a>
from <span class="vcard"><a class="email" href="mailto:uma.shankar@intel.com" title="Uma Shankar <uma.shankar@intel.com>"> <span class="fn">Uma Shankar</span></a>
</span></b>
<pre>This issue is happening due to pipe rounding (an expected behaviour in such
scenario, confirmed with hw architect Runyan, Art as well) causing crc to
mismatch. Unfortunately the test relies on the crc.
But checked on simulation and dump the pipe bmp output and compared bit by bit
with the expected output. The data was matching perfectly. There will no
visible impact to user as the framebuffer content is perfect, so user will not
be able to see any issues.
Future actions planned is :
- Use pipe writeback to get the framebuffer and check the pixel values
directly (need to implement it first)
- Use chamelium as a workaround for the lack of pipe writeback
All this will need significant implementation on driver side and even the tests
need to re-written to align this. We will work on it separately.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>