[Bug 103159] [CI] igt at kms_plane_scaling - Test assertion failure function igt_drm_plane_commit Failed assertion: ret == 0

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=103159

krisman at collabora.co.uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|intel-gfx-bugs at lists.freede |krisman at collabora.co.uk
                   |sktop.org                   |

--- Comment #2 from krisman at collabora.co.uk ---
Hi, 

By reviewing the logs, I see two kinds of failures:

On the CI APL and GLK:

[drm:skl_check_pipe_max_pixel_rate [i915]] Max supported pixel clock with
scaling exceeded

And on the CI KBL:

[drm:__setplane_internal] Invalid pixel format XR24 little-endian (0x34325258)

On my personal system, which is an APL, I get the second kind of error.  It is
due the attempt to use that pixel format on a cursor plane, which apparently is
not supported.  Since we blindly fetch a plane, we could avoid that error with
something like:  

--- a/tests/kms_plane_scaling.c
+++ b/tests/kms_plane_scaling.c
@@ -215,7 +215,7 @@ static void test_plane_scaling(data_t *d)
                }

                /* Set up fb2->plane2 mapping. */
-               d->plane2 = igt_output_get_plane(output, 2);
+               d->plane2 = igt_output_get_plane_type(output,
DRM_PLANE_TYPE_OVERLAY);
                igt_plane_set_fb(d->plane2, &d->fb2);

                /* 2nd plane windowed */


That said, once I prevent that issue, I can hit the second error on my APL lake
too:

[drm:skl_check_pipe_max_pixel_rate [i915]] Max supported pixel clock with
scaling exceeded

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20171021/fcd89fdb/attachment.html>