Bug 100055

Summary: [BAT] [IVB] igt@gem_sync@basic-all fails
Product: DRI Reporter: Dorota Czaplejewicz <dorota.czaplejewicz>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: dorota.czaplejewicz, intel-gfx-bugs
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: IVB i915 features:

Description Dorota Czaplejewicz 2017-03-03 18:34:47 UTC 
The test igt@gem_sync@basic-all fails on IVB-3770 about 17% of the time (22 of 128).

CPU: IVB-3770
Kernel: drm-tip: 2017y-02m-27d-07h-11m-41s
OS: Fedora 24

Log:
$ sudo ./gem_sync --r basic-all
IGT-Version: 1.17-gd91fec7 (x86_64) (Linux: 4.10.0-CI-CI_DRM_2269_f889c7b+ x86_64)
Using Legacy submission , with semaphores
Completed 54272 cycles: 92.290 us
(gem_sync:10391) CRITICAL: Test assertion failure function sync_all, file gem_sync.c:570:
(gem_sync:10391) CRITICAL: Failed assertion: intel_detect_and_clear_missed_interrupts(fd) == 0
(gem_sync:10391) CRITICAL: error: 4 != 0
Stack trace:
  #0 [__igt_fail_assert+0xf1]
  #1 [sync_all+0x2ba]
  #2 [__real_main722+0x2f3]
  #3 [main+0x33]
  #4 [__libc_start_main+0xf1]
  #5 [_start+0x29]
  #6 [<unknown>+0x29]
Subtest basic-all failed.
**** DEBUG ****
(gem_sync:10391) DEBUG: Test requirement passed: num_engines
(gem_sync:10391) CRITICAL: Test assertion failure function sync_all, file gem_sync.c:570:
(gem_sync:10391) CRITICAL: Failed assertion: intel_detect_and_clear_missed_interrupts(fd) == 0
(gem_sync:10391) CRITICAL: error: 4 != 0
****  END  ****
Subtest basic-all: FAIL (5.047s)
Comment 1 Chris Wilson 2017-03-03 18:36:47 UTC 
Essentially the same as bug 100052. Not sure if it worth two opens, the patch (if any) will be the same.
Comment 2 Chris Wilson 2017-03-18 17:36:55 UTC 

*** This bug has been marked as a duplicate of bug 100052 ***

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.