[Bug 110391] [CI][RESUME] igt at kms_setmode@invalid-clone-single-crtc-stealing - fail - Failed assertion: ret == 0, Last errno: 22, Invalid argument

[bugzilla-daemon at freedesktop.org]

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

Arek Hiler <arkadiusz.hiler at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|high                        |medium

--- Comment #3 from Arek Hiler <arkadiusz.hiler at intel.com> ---
The failure is likely caused by this function that gets mode to set on all
connectors:

static void get_mode_for_crtc(struct crtc_config *crtc,
                              drmModeModeInfo *mode_ret)
{
        drmModeModeInfo mode;
        int i;

        /*
         * First try to select a default mode that is supported by all
         * connectors.
         */
        for (i = 0; i < crtc->connector_count; i++) {
                mode = crtc->cconfs[i].default_mode;
                if (crtc_supports_mode(crtc, &mode))
                        goto found;
        }

        /*
         * Then just fall back to find any that is supported by all
         * connectors.
         */
        for (i = 0; i < crtc->cconfs[0].connector->count_modes; i++) {
                mode = crtc->cconfs[0].connector->modes[i];
                if (crtc_supports_mode(crtc, &mode))
                        goto found;
        }

        /*
         * If none is found then just pick the default mode of the first
         * connector and hope the other connectors can support it by scaling
         * etc.
         */
        mode = crtc->cconfs[0].default_mode;
found:
        *mode_ret = mode;
}

eDP quite likely supports 36bpp but DP does not. Because of the wrong
assumptions above we try to set this 36bpp mode on the DP connector, failing on
the first drmModeSetCrtc().

The test should be fixed by being more clever about mode selection or just
skipping if connector happens to not support given mode, instead of asserting
straight away.

Dropping priority to medium, as this is a test issue.

-- 
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/20190425/1f7b75b3/attachment.html>