Bug 110284

Summary:	[CI] igt@gem_exec_reloc@basic-cpu-read-active - fail - Failed assertion: gem_bo_busy(fd, obj.handle)
Product:	DRI	Reporter:	Martin Peres <martin.peres>
Component:	DRM/Intel	Assignee:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Status:	CLOSED WORKSFORME	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	normal
Priority:	medium	CC:	intel-gfx-bugs
Version:	XOrg git
Hardware:	Other
OS:	All
Whiteboard:	ReadyForDev
i915 platform:	BSW/CHT	i915 features:	GEM/Other

Description Martin Peres 2019-03-29 16:30:10 UTC

https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2723/fi-bsw-kefka/igt@gem_exec_reloc@basic-cpu-read-active.html

Starting subtest: basic-cpu-read-active
(gem_exec_reloc:2167) CRITICAL: Test assertion failure function basic_reloc, file ../tests/i915/gem_exec_reloc.c:396:
(gem_exec_reloc:2167) CRITICAL: Failed assertion: gem_bo_busy(fd, obj.handle)
Subtest basic-cpu-read-active failed.

Comment 1 CI Bug Log 2019-03-29 16:30:37 UTC

The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* BSW: igt@gem_exec_reloc@basic-cpu-read-active - fail - Failed assertion: gem_bo_busy(fd, obj.handle)
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2723/fi-bsw-kefka/igt@gem_exec_reloc@basic-cpu-read-active.html

Comment 2 Chris Wilson 2019-03-29 16:38:00 UTC

The dictionary definition of an impossible bug. The spinner was reported as having completed with nary a sign of a hang. Not strictly the spinner though, the write-target of the spinner -- could it be we failed to set the fence? Did we fail to see the fence inside GEM_BUSY?

Comment 3 Francesco Balestrieri 2019-04-08 11:56:02 UTC

No other occurrence so far (actually non in CI buglog, but that's probably a reporting error). Changing to medium.

Comment 4 Francesco Balestrieri 2019-06-03 06:43:00 UTC

Still not seen, closing.

Comment 5 CI Bug Log 2019-07-31 11:45:17 UTC

The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.

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.