[Bug 100020] New: [igt]kms_frontbuffer_tracking at fbc-suspend fails

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Mar 1 12:36:44 UTC 2017


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

            Bug ID: 100020
           Summary: [igt]kms_frontbuffer_tracking at fbc-suspend fails
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: dorota.czaplejewicz at collabora.co.uk
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 130000
  --> https://bugs.freedesktop.org/attachment.cgi?id=130000&action=edit
Full log of the test

The test consistently fails, complaining about assertion failure. Happens every
time.

To reproduce: ./kms_frontbuffer_tracking --r fbc-suspend

The test should SKIP if the hardware doesn't support FBC.

IGT-Version: 1.17-geb53664 (x86_64) (Linux: 4.10.0-CI-CI_DRM_2243_15ccc64+
x86_64)
Primary screen: HDMI-A 1280x1024, crtc 31
FBC last action not supported
Can't test PSR: no usable eDP screen.
Sink CRC not supported: primary screen is not eDP
FBC status:
FBC disabled: no suitable CRTC for FBC

(kms_frontbuffer_tracking:2397) CRITICAL: Test assertion failure function
enable_prim_screen_and_wait, file kms_frontbuffer_tracking.c:1752:
(kms_frontbuffer_tracking:2397) CRITICAL: Failed assertion: false
(kms_frontbuffer_tracking:2397) CRITICAL: FBC disabled

CPU: HSW-4770R
Display: DVI, connected to HDMI port.
OS: Fedora 24
kernel: drm-tip: 2017y-02m-27d-07h-11m-41s

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


More information about the intel-gfx-bugs mailing list