Bug 112326

Summary: [CI][DRMTIP]igt@gem_wait@* - fail - Failed assertion: __gem_wait(fd, &wait) == -\d+
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: not set    
Priority: not set CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: BDW, BSW/CHT i915 features: GEM/Other

Description Lakshmi 2019-11-18 18:32:20 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bdw-5557u/igt@gem_wait@await-vcs0.html
Starting subtest: await-vcs0
(gem_wait:1280) CRITICAL: Test assertion failure function basic, file ../tests/i915/gem_wait.c:112:
(gem_wait:1280) CRITICAL: Failed assertion: __gem_wait(fd, &wait) == -62
(gem_wait:1280) CRITICAL: error: 0 != -62
Subtest await-vcs0 failed.
**** DEBUG ****
(gem_wait:1280) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(gem_wait:1280) drmtest-DEBUG: Test requirement passed: !(fd<0)
(gem_wait:1280) igt_dummyload-DEBUG: Test requirement passed: vgem_has_fences(cork->vgem.device)
(gem_wait:1280) drmtest-DEBUG: Test requirement passed: is_i915_device(fd) && has_known_intel_chipset(fd)
(gem_wait:1280) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(gem_wait:1280) ioctl_wrappers-DEBUG: Test requirement passed: dir >= 0
(gem_wait:1280) ioctl_wrappers-DEBUG: Test requirement passed: err == 0
(gem_wait:1280) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_wait:1280) CRITICAL: Test assertion failure function basic, file ../tests/i915/gem_wait.c:112:
(gem_wait:1280) CRITICAL: Failed assertion: __gem_wait(fd, &wait) == -62
(gem_wait:1280) CRITICAL: error: 0 != -62
(gem_wait:1280) igt_core-INFO: Stack trace:
(gem_wait:1280) igt_core-INFO:   #0 ../lib/igt_core.c:1716 __igt_fail_assert()
(gem_wait:1280) igt_core-INFO:   #1 ../tests/i915/gem_wait.c:105 basic()
(gem_wait:1280) igt_core-INFO:   #2 [<unknown>+0x0]
(gem_wait:1280) igt_core-INFO:   #3 [<unknown>+0x29508ba0]
****  END  ****
Subtest await-vcs0: FAIL (0.610s)
Comment 1 CI Bug Log 2019-11-18 18:33:09 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* BSW BDW: igt@gem_wait@* - fail - Failed assertion: __gem_wait(fd, &amp;wait) == -\d+
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bdw-5557u/igt@gem_wait@await-vcs0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bdw-5557u/igt@gem_wait@write-wait-vcs1.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bdw-5557u/igt@gem_wait@await-vcs1.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bdw-5557u/igt@gem_wait@write-busy-vcs0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bdw-5557u/igt@gem_wait@busy-vcs1.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bdw-5557u/igt@gem_wait@write-busy-vcs1.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bdw-5557u/igt@gem_wait@write-wait-vcs0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bsw-kefka/igt@gem_wait@await-vcs0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bsw-kefka/igt@gem_wait@write-busy-vcs0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bsw-kefka/igt@gem_wait@write-wait-vcs0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bsw-n3050/igt@gem_wait@await-vcs0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bsw-n3050/igt@gem_wait@write-busy-vcs0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bsw-n3050/igt@gem_wait@write-wait-vcs0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bsw-nick/igt@gem_wait@await-vcs0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bsw-nick/igt@gem_wait@write-busy-vcs0.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_404/fi-bsw-nick/igt@gem_wait@write-wait-vcs0.html
Comment 2 Chris Wilson 2019-11-18 20:33:26 UTC
Bad igt.

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.