Created attachment 124582 [details] Dmesg The following subcases are failing: igt@gem_ctx_create@active-bsd igt@gem_ctx_create@forked-active-default igt@gem_ctx_create@active-vebox igt@gem_ctx_create@active-default igt@gem_ctx_create@forked-active-vebox igt@gem_ctx_create@active-blt igt@gem_ctx_create@forked-active-bsd igt@gem_ctx_create@active-render igt@gem_ctx_create@forked-active-blt Dmesg error: [ 203.808488] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create req: -28 root@gfx-Inspiron-15-3552:/home/gfx/intel-graphics/intel-gpu-tools/tests# ./gem_ctx_create --run-subtest forked-active-blt IGT-Version: 1.15-g3ce58b6 (x86_64) (Linux: 4.7.0-040700rc2-generic x86_64) (gem_ctx_create:1255) ioctl-wrappers-CRITICAL: Test assertion failure function gem_execbuf, file ioctl_wrappers.c:589: (gem_ctx_create:1255) ioctl-wrappers-CRITICAL: Failed assertion: __gem_execbuf(fd, execbuf) == 0 (gem_ctx_create:1255) ioctl-wrappers-CRITICAL: error: -22 != 0 Stack trace: (gem_ctx_create:1256) ioctl-wrappers-CRITICAL: Test assertion failure function gem_execbuf, file ioctl_wrappers.c:589: (gem_ctx_create:1256) ioctl-wrappers-CRITICAL: Failed assertion: __gem_execbuf(fd, execbuf) == 0 #0 [__igt_fail_assert+0x101] (gem_ctx_create:1256) ioctl-wrappers-CRITICAL: error: -22 != 0 Stack trace: #1 [gem_execbuf+0x44] #0 [__igt_fail_assert+0x101] #2 [active.constprop.1+0x12b] (gem_ctx_create:1257) ioctl-wrappers-CRITICAL: Test assertion failure function gem_execbuf, file ioctl_wrappers.c:589: (gem_ctx_create:1257) ioctl-wrappers-CRITICAL: Failed assertion: __gem_execbuf(fd, execbuf) == 0 (gem_ctx_create:1257) ioctl-wrappers-CRITICAL: error: -22 != 0 Stack trace: #1 [gem_execbuf+0x44] (gem_ctx_create:1258) ioctl-wrappers-CRITICAL: Test assertion failure function gem_execbuf, file ioctl_wrappers.c:589: #3 [__real_main140+0x1fa] (gem_ctx_create:1258) ioctl-wrappers-CRITICAL: Failed assertion: __gem_execbuf(fd, execbuf) == 0 (gem_ctx_create:1258) ioctl-wrappers-CRITICAL: error: -22 != 0 Stack trace: #2 [active.constprop.1+0x12b] #4 [main+0x23] #0 [__igt_fail_assert+0x101] #3 [__real_main140+0x1fa] #5 [__libc_start_main+0xf0] #0 [__igt_fail_assert+0x101] #4 [main+0x23] #1 [gem_execbuf+0x44] #6 [_start+0x29] #1 [gem_execbuf+0x44] #5 [__libc_start_main+0xf0] #2 [active.constprop.1+0x12b] #6 [_start+0x29] #2 [active.constprop.1+0x12b] #3 [__real_main140+0x1fa] #7 [<unknown>+0x29] #7 [<unknown>+0x29] #4 [main+0x23] #3 [__real_main140+0x1fa] #5 [__libc_start_main+0xf0] #4 [main+0x23] #6 [_start+0x29] child 1 failed with exit status 99 Subtest forked-active-blt failed. **** DEBUG **** (gem_ctx_create:1253) ioctl-wrappers-DEBUG: Test requirement passed: gem_has_ring(fd, ring) **** END **** Subtest forked-active-blt: FAIL (0.012s) Configuration: Configuration: ============================================ Kernel version : 4.7.0-040700rc2-generic Linux distribution : Ubuntu 16.04 LTS Architecture : 64-bit Mesa version : 11.2.2 xf86-video-intel version : 2.99.917 Xorg-Xserver version : 1.18.3 DRM version : 2.4.67 VAAPI version : Intel i965 driver for Intel(R) CherryView - 1.7.0 Cairo version : [1m[1;31mNot found[0m Intel GPU Tools version : 1.15-1 <-- [1;33mThis is a generic version of IGT[0m Kernel driver in use : [1m[1;32mi915[0m Hardware acceleration : Bios revision : 4.0 KSC revision : [1m[1;31mNot found[0m <-- [1;33mmaybe the DUT doesn't has this firmware[0m [1m[1;34mHardware information[0m ============================================ Platform : Motherboard model : Inspiron 15-3552 Motherboard type : 0T14MC Portable Motherboard manufacturer : Dell Inc. CPU family : Pentium CPU information : Intel(R) Pentium(R) CPU N3700 @ 1.60GHz GPU Card : Intel Corporation Device 22b1 (rev 21) (prog-if 00 [VGA controller]) Memory ram : 4 GB Maximum memory ram allowed : 8 GB Display resolution : CPU's number : 4 Hard drive Capacity : 128 GB
\o/ That's the bug the test was trying to demonstrate!
So, in this case if the Failure = pass , should we block those test cases or include them in the blacklist?
This failure is a failure, since it can easily impact userspace (and cause loss of data). If you include them in the blacklist how will you know when I fixed them... (The patch is to both to fix the use of the shrinker to reclaim contexts and to reduce aperture pressure by using WC rather than GTT.)
(In reply to Chris Wilson from comment #3) > This failure is a failure, since it can easily impact userspace (and cause > loss of data). If you include them in the blacklist how will you know when I > fixed them... (The patch is to both to fix the use of the shrinker to > reclaim contexts and to reduce aperture pressure by using WC rather than > GTT.) Good to know, we will wait for the patch in order to close the bug, thanks
commit 9d80841ea4c9df420da3f9a61a819d09a03f2161 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Thu Aug 18 17:16:56 2016 +0100 drm/i915: Allow ringbuffers to be bound anywhere
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.