[Bug 92845] [BYT clflush] gem_exec_flush stress tests fail

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Mar 28 12:31:02 UTC 2017


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

--- Comment #23 from Jari Tahvanainen <jari.tahvanainen at intel.com> ---
Does this help to figure out what is the problem in BYT? For some reason dmesg
is not available for this particular run ...

Results for igt at gem_partial_pwrite_pread@reads
IGT-Version: 1.18-g0aef486 (x86_64) (Linux: 4.11.0-rc3-tip-201703201600+
x86_64)
checking partial reads
Stack trace:
  #0 [__igt_fail_assert+0xf1]
  #1 [intel_batchbuffer_flush_on_ring+0xc5]
  #2 [do_tests+0x1ac]
  #3 [__real_main250+0x120]
  #4 [main+0x35]
  #5 [__libc_start_main+0xf0]
  #6 [_start+0x29]
  #7 [<unknown>+0x29]
Subtest reads: FAIL (0.186s)
(gem_partial_pwrite_pread:17828) intel-batchbuffer-CRITICAL: Test assertion
failure function intel_batchbuffer_flush_on_ring, file intel_batchbuffer.c:184:
(gem_partial_pwrite_pread:17828) intel-batchbuffer-CRITICAL: Failed assertion:
(drm_intel_gem_bo_context_exec(batch->bo, ctx, used, ring)) == 0
(gem_partial_pwrite_pread:17828) intel-batchbuffer-CRITICAL: Last errno: 5,
Input/output error
Subtest reads failed.
**** DEBUG ****
(gem_partial_pwrite_pread:17828) INFO: checking partial reads
(gem_partial_pwrite_pread:17828) intel-batchbuffer-CRITICAL: Test assertion
failure function intel_batchbuffer_flush_on_ring, file intel_batchbuffer.c:184:
(gem_partial_pwrite_pread:17828) intel-batchbuffer-CRITICAL: Failed assertion:
(drm_intel_gem_bo_context_exec(batch->bo, ctx, used, ring)) == 0
(gem_partial_pwrite_pread:17828) intel-batchbuffer-CRITICAL: Last errno: 5,
Input/output error
****  END  ****

-- 
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/20170328/01d22ffd/attachment.html>


More information about the intel-gfx-bugs mailing list