Attachment 127062 Details for Bug 98109 – BYT__gem_exec_flush__basic-uc-prw-default__output

BYT__gem_exec_flush__basic-uc-prw-default__output

BYT__gem_exec_flush__basic-uc-prw-default__output.txt (text/plain), 1.48 KB, created by cprigent on 2016-10-06 13:14:52 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: cprigent

Created: 2016-10-06 13:14:52 UTC

Size: 1.48 KB

patch

obsolete

>root@BYT2:/opt/X11R7/src/intel-gpu-tools/tests# ./gem_exec_flush --r basic-uc-prw-default
>IGT-Version: 1.16-g1a76d88 (x86_64) (Linux: 4.8.0-nightly+ x86_64)
>Has LLC? no
>CPU features: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2
>(gem_exec_flush:3188) CRITICAL: Test assertion failure function run, file gem_exec_flush.c:278:
>(gem_exec_flush:3188) CRITICAL: Failed assertion: val == i
>(gem_exec_flush:3188) CRITICAL: error: 0xabcdabcd != 0x10
>Stack trace:
>(gem_exec_flush:3189) CRITICAL: Test assertion failure function run, file gem_exec_flush.c:276:
>(gem_exec_flush:3189) CRITICAL: Failed assertion: val == i ^ 0xffffffff
>(gem_exec_flush:3189) CRITICAL: error: 0xdeadbeef != 0xffffffdf
>Stack trace:
>  #0 [__igt_fail_assert+0xf1]
>  #0 [__igt_fail_assert+0xf1]
>  #1 [run+0x9e8]
>  #1 [run+0x891]
>  #2 [__real_main533+0xb11]
>  #3 [main+0x29]
>  #2 [__real_main533+0xb11]
>  #4 [__libc_start_main+0xf0]
>  #5 [_start+0x29]
>  #3 [main+0x29]
>  #6 [<unknown>+0x29]
>  #4 [__libc_start_main+0xf0]
>child 3 failed with exit status 99
>Subtest basic-uc-prw-default failed.
>No log.
>Subtest basic-uc-prw-default: FAIL (0.008s)
>Test requirement not met in function gem_require_ring, file ioctl_wrappers.c:1443:
>Test requirement: gem_has_ring(fd, ring)
>Test requirement not met in function gem_require_ring, file ioctl_wrappers.c:1443:
>Test requirement: gem_has_ring(fd, ring)
>Test requirement not met in function gem_require_ring, file ioctl_wrappers.c:1443:
>Test requirement: gem_has_ring(fd, ring)

Actions: View

Attachments on bug 98109: 127062 | 127063

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.