<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [CI] igt@kms_plane_scaling - Test assertion failure function igt_drm_plane_commit Failed assertion: ret == 0" href="https://bugs.freedesktop.org/show_bug.cgi?id=103159#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [CI] igt@kms_plane_scaling - Test assertion failure function igt_drm_plane_commit Failed assertion: ret == 0" href="https://bugs.freedesktop.org/show_bug.cgi?id=103159">bug 103159</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 krisman from <a href="show_bug.cgi?id=103159#c6">comment #6</a>) > (In reply to Jani Saarinen from <a href="show_bug.cgi?id=103159#c4">comment #4</a>) > > One patch merged, does this help thing? > > <a href="https://cgit.freedesktop.org/xorg/app/intel-gpu-tools/commit/">https://cgit.freedesktop.org/xorg/app/intel-gpu-tools/commit/</a> > > ?id=bde7d72f58df18f86127b5b7fdcb89b64ee1a1d2 > > Yes. It fixes the following kind of failure on KBL (See <a href="show_bug.cgi?id=103159#c3">comment 3</a>): > > > > [drm:__setplane_internal] Invalid pixel format XR24 little-endian > > > (0x34325258) > > The other issue (below) is with the Pixel clock rate calculation, which I'm > working on the driver-side for a fix. > > > [drm:skl_check_pipe_max_pixel_rate [i915]] Max supported pixel clock with > > scaling exceeded See for instance the following test: <a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3317/shard-kbl6/igt@kms_plane_scaling.html">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3317/shard-kbl6/igt@kms_plane_scaling.html</a> Which no longer hits the invalid pixel format error but bails out on the pixel rate verification.</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>