[Bug 102259] [CI][HSW] Failed assertion: !mismatch in igt at kms_cursor_legacy@flip-vs-cursor-busy-crc-(legacy|atomic)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Sep 14 12:54:30 UTC 2017


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

--- Comment #11 from Marta Löfstedt <marta.lofstedt at intel.com> ---
I have tested with Chris spinbatches cleanup patch, but I still see GPU_HANG on
my BDW NUCi5.

Also, I still believe that the GPU_HANG is during test execution and not
afterwards 

 static void stress(igt_display_t *display,
@@ -1376,7 +1400,7 @@ static void flip_vs_cursor_busy_crc(igt_display_t
*display, bool atomic)
                uint32_t *busy;

                busy = make_fb_busy(display->drm_fd, &fb_info[1]);
-
+               kmsg(KERN_DEBUG "--- AFTER BUSY ---");
                vblank_start = get_vblank(display->drm_fd, pipe,
DRM_VBLANK_NEXTONMISS);

                flip_nonblocking(display, pipe, atomic, &fb_info[1]);
@@ -1385,6 +1409,7 @@ static void flip_vs_cursor_busy_crc(igt_display_t
*display, bool atomic)
                igt_assert_eq(get_vblank(display->drm_fd, pipe, 0),
vblank_start);

                igt_pipe_crc_collect_crc(pipe_crc, &crcs[2]);
+               kmsg(KERN_DEBUG "--- BEFORE finish_fb_busy ---");

                finish_fb_busy(busy);

I added above to the test to insert kmsgs. The attached "dmesg snippets with
inserted kmsg from test *" shows that the GPU is reset after "AFTER BUSY", but
before "BEFORE finish_fb_busy". Also, I sometimes get message of timeout
fences:

"[   81.824182] [drm:missed_breadcrumb [i915]] rcs0 missed breadcrumb at
intel_breadcrumbs_hangcheck+0x61/0x80 [i915], irq posted? yes, current
seqno=f6, last=f7
[   88.800051] asynchronous wait on fence i915:kms_cursor_lega[1771]/0:11 timed
out
[   88.800056] asynchronous wait on fence i915:kms_cursor_lega[1771]/0:11 timed
out
[   94.791508] [drm] GPU HANG: ecode 8:0:0xe75ffefe, in kms_cursor_lega [1771],
reason: No progress on rcs0, action: reset".

Anyways, with this going on I am not surprised that the CRCs doesn't match.

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


More information about the intel-gfx-bugs mailing list