This appear to have started on drmtip_12, the oldest machine I get data from is ILK but you can also see this in drmtip visialization: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip.html for CTG and ELK https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-650/igt@gem_eio@in-flight-suspend.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-m540/igt@gem_eio@in-flight-suspend.html (gem_eio:2563) ioctl_wrappers-CRITICAL: Test assertion failure function gem_execbuf_wr, file ../lib/ioctl_wrappers.c:634: (gem_eio:2563) ioctl_wrappers-CRITICAL: Failed assertion: __gem_execbuf_wr(fd, execbuf) == 0 (gem_eio:2563) ioctl_wrappers-CRITICAL: error: -1 != 0 Subtest in-flight-suspend failed. Some more links: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-650/igt@gem_eio@in-flight-external.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-m540/igt@gem_eio@in-flight-external.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-650/igt@gem_eio@wait-1us.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-m540/igt@gem_eio@wait-1us.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-650/igt@gem_eio@wait-immediate.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-m540/igt@gem_eio@wait-immediate.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-650/igt@gem_eio@wait-10ms.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-m540/igt@gem_eio@wait-10ms.html
Also, on some perf_pmu: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-650/igt@perf_pmu@render-node-busy-vcs0.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-m540/igt@perf_pmu@render-node-busy-vcs0.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-650/igt@perf_pmu@render-node-busy-rcs0.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-m540/igt@perf_pmu@render-node-busy-rcs0.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-650/igt@perf_pmu@render-node-busy-idle-vcs0.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-m540/igt@perf_pmu@render-node-busy-idle-vcs0.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-650/igt@perf_pmu@render-node-busy-idle-rcs0.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-ilk-m540/igt@perf_pmu@render-node-busy-idle-rcs0.html
commit a86714b95838dd20a091b04f8c4139d0acf7f16b (HEAD, upstream/master) Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Thu Apr 5 19:41:32 2018 +0100 igt/gem_eio: Drop DRM_MASTER so we can reacquire it in the subtests As we reopen the fd for each subtest, and we need a DRM_MASTER, we need to drop master on the original before we are allowed to claim DRM_MASTER on the second. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105922 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Need more drmtip runs to close this
Looks green on drmtip_13 and forward
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.