[Bug 103167] [CI] igt at kms_frontbuffer_tracking@* - fail - CRC mismatch

[bugzilla-daemon at freedesktop.org]

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

Maarten Lankhorst <bugs at mblankhorst.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugs at mblankhorst.nl

--- Comment #66 from Maarten Lankhorst <bugs at mblankhorst.nl> ---
Created attachment 144360
  --> https://bugs.freedesktop.org/attachment.cgi?id=144360&action=edit
kms_draw_crc chamelium hack

I was able to reproduce it on ICL much better with a 3840x256 framebuffer.

This adds draw-dirtyfb-* to kms_draw_crc, based on how kms_frontbuffer_tracking
works.

After setup, it runs the following loop 25 times, and if a chamelium is
attached, dumps all (scaled to 1920x1080) frames to p$pid-frame-$n.png, with
the reference (3840x256) fb to p$pid-reference.png:

        for (i = 0; i < 5; i++) {
                rect = pat1_get_rect(&fb, i);

                igt_draw_rect_fb(drm_fd, bufmgr, NULL, &fb, method,
                                 rect.x, rect.y, rect.w, rect.h, rect.color);
                gem_set_domain(drm_fd, fb.gem_handle, I915_GEM_DOMAIN_GTT, 0);
                igt_dirty_fb(drm_fd, &fb);
                igt_wait_for_vblank(drm_fd, ms.pipe);

                igt_pipe_crc_collect_crc(pipe_crc, &crc);
                check_crc_equal(&ref_crc[i], &fb_ref[i], &crc, &fb, &display,
plane, &panic_fb);
        }

With this I can clearly see a black line on ICL for a few frames, presumably
when FBC gets enabled. The CRC mismatch doesn't occur without FBC. (echo 0 >
/sys/module/i915/parameters/enable_fbc)

-- 
You are receiving this mail because:
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/20190528/c3d32766/attachment.html>