<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [IGT][BDW] kms_frontbuffer_tracking@fbc-*draw* has inconsistent results - FBC disabled" href="https://bugs.freedesktop.org/show_bug.cgi?id=101623#c25">Comment # 25</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [IGT][BDW] kms_frontbuffer_tracking@fbc-*draw* has inconsistent results - FBC disabled" href="https://bugs.freedesktop.org/show_bug.cgi?id=101623">bug 101623</a> from <a class="email" href="mailto:krisman@collabora.co.uk" title="krisman@collabora.co.uk">krisman@collabora.co.uk</a> <pre>(In reply to Elizabeth from <a href="show_bug.cgi?id=101623#c21">comment #21</a>) > Sorry for the spam. I mean the "FBC disabled" in KBL, but I need to retest > 100020 to be sure if it is still reproducible. > (In reply to Marta Löfstedt from <a href="show_bug.cgi?id=101623#c17">comment #17</a>) > > Note we are still seeing "FBC disabled" on KBL-shards: > > <a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3016/shard-kbl2/">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3016/shard-kbl2/</a> > > igt@<a href="mailto:kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-blt.html">kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-blt.html</a> 100020 is very specific to a workaround applied only to hsw and it is due the poor status reporting interface in fbc. but I can see the FBC disabled happening on other platforms for unrelated reasons. It still triggers on HSW, btw. This mentions an underrun detection as the cause of failure. It is good to see if the underrun is the actual error or a side effect of the fbc status being overwritten after the actual failure. How hard is it to reproduce on any KBL? I can give it a try too.</pre> </div> <hr> You are receiving this mail because: <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>