[Bug 104372] [IGT] prime_vgem at coherency-gtt failed assertion: gtt[1024*i] == ~i
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Apr 9 19:01:13 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=104372
Elizabeth <elizabethx.de.la.torre.mena at intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
i915 platform| |GLK, BSW/CHT, BYT
--- Comment #5 from Elizabeth <elizabethx.de.la.torre.mena at intel.com> ---
Still valid for BYT, BSW, BXT and GLK:
Results for igt at prime_vgem@coherency-gtt
Result: fail
gfx_stack gfx_stack_easy_bugs kernel_commit_information
Detail Value
Time 0.17 seconds
Returncode
99
Out
IGT-Version: 1.21-ge3a0ed9 (x86_64) (Linux:
4.16.0-rc7-drm-intel-qa-ww14-commit-c46052c+ x86_64)
Stack trace:
#0 [__igt_fail_assert+0x101]
#1 [__real_main757+0xbb8]
#2 [<unknown>+0xbb8]
Subtest coherency-gtt: FAIL (0.008s)
Test requirement not met in function __real_main757, file prime_vgem.c:849:
Test requirement: vgem_fence_has_flag(vgem, WIP_VGEM_FENCE_NOTIMEOUT)
Err
(prime_vgem:31066) CRITICAL: Test assertion failure function
test_gtt_interleaved, file prime_vgem.c:273:
(prime_vgem:31066) CRITICAL: Failed assertion: gtt[1024*i] == ~i
(prime_vgem:31066) CRITICAL: error: 0 != -1
Subtest coherency-gtt failed.
**** DEBUG ****
(prime_vgem:31066) CRITICAL: Test assertion failure function
test_gtt_interleaved, file prime_vgem.c:273:
(prime_vgem:31066) CRITICAL: Failed assertion: gtt[1024*i] == ~i
(prime_vgem:31066) CRITICAL: error: 0 != -1
(prime_vgem:31066) igt-core-INFO: Stack trace:
(prime_vgem:31066) igt-core-INFO: #0 [__igt_fail_assert+0x101]
(prime_vgem:31066) igt-core-INFO: #1 [__real_main757+0xbb8]
(prime_vgem:31066) igt-core-INFO: #2 [<unknown>+0xbb8]
**** END ****
--
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/20180409/d4affa8a/attachment.html>
More information about the intel-gfx-bugs
mailing list