[Bug 108932] New: [CI][DRMTIP] igt at kms_atomic_transition@1x-modeset-transitions-fencing - fail - HDMI-A-2 and eDP-1 are both trying to use pipe C

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Dec 3 17:25:08 UTC 2018


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

            Bug ID: 108932
           Summary: [CI][DRMTIP]
                    igt at kms_atomic_transition@1x-modeset-transitions-fenci
                    ng - fail - HDMI-A-2 and eDP-1 are both trying to use
                    pipe C
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: martin.peres at free.fr
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_153/fi-icl-u3/igt@kms_atomic_transition@1x-modeset-transitions-fencing.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_152/fi-icl-u3/igt@kms_atomic_transition@1x-modeset-transitions-fencing.html

Starting subtest: 1x-modeset-transitions-fencing
(kms_atomic_transition:1959) igt_kms-CRITICAL: Test assertion failure function
igt_display_refresh, file ../lib/igt_kms.c:2202:
(kms_atomic_transition:1959) igt_kms-CRITICAL: Failed assertion:
output->pending_pipe != b->pending_pipe
(kms_atomic_transition:1959) igt_kms-CRITICAL: Last errno: 25, Inappropriate
ioctl for device
(kms_atomic_transition:1959) igt_kms-CRITICAL: HDMI-A-2 and eDP-1 are both
trying to use pipe C
Subtest 1x-modeset-transitions-fencing failed.

-- 
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/20181203/a6d64891/attachment.html>


More information about the intel-gfx-bugs mailing list