Bug 111646 - [CI][RESUME] igt@gem_exec_schedule@deep-* - fail - Failed assertion: __vgem_fence_signal(fd, fence) == 0, error: -110 != 0
Summary: [CI][RESUME] igt@gem_exec_schedule@deep-* - fail - Failed assertion: __vgem_f...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: high not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-11 07:42 UTC by Martin Peres
Modified: 2019-09-11 07:53 UTC (History)
1 user (show)

See Also:
i915 platform: TGL
i915 features: GEM/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2019-09-11 07:42:47 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-tgl-u/igt@gem_exec_schedule@deep-bsd2.html

Starting subtest: deep-bsd2
(gem_exec_schedule:2746) igt_vgem-CRITICAL: Test assertion failure function vgem_fence_signal, file ../lib/igt_vgem.c:193:
(gem_exec_schedule:2746) igt_vgem-CRITICAL: Failed assertion: __vgem_fence_signal(fd, fence) == 0
(gem_exec_schedule:2746) igt_vgem-CRITICAL: error: -110 != 0
Comment 2 Chris Wilson 2019-09-11 07:53:52 UTC
Of the few remaining vgem fences in here, you had to go and hit it. This is likely just because tgl is not using rps yet and so is too slow.


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.