Bug 110909

Summary:	[CI][DRMTIP] igt@gem_vm_create@isolation - fail - Failed assertion: result == 1, error: 0 != 1
Product:	DRI	Reporter:	Lakshmi <lakshminarayana.vudum>
Component:	DRM/Intel	Assignee:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Status:	RESOLVED MOVED	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	normal
Priority:	medium	CC:	intel-gfx-bugs
Version:	DRI git
Hardware:	Other
OS:	All
Whiteboard:	ReadyForDev
i915 platform:	BXT, BYT	i915 features:	GEM/Other

Description Lakshmi 2019-06-13 05:25:44 UTC

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_305/fi-byt-j1900/igt@gem_vm_create@isolation.html

Starting subtest: isolation
(gem_vm_create:1133) CRITICAL: Test assertion failure function isolation, file ../tests/i915/gem_vm_create.c:329:
(gem_vm_create:1133) CRITICAL: Failed assertion: result == 1
(gem_vm_create:1133) CRITICAL: error: 0 != 1
Subtest isolation failed.
**** DEBUG ****
(gem_vm_create:1133) CRITICAL: Test assertion failure function isolation, file ../tests/i915/gem_vm_create.c:329:
(gem_vm_create:1133) CRITICAL: Failed assertion: result == 1
(gem_vm_create:1133) CRITICAL: error: 0 != 1
(gem_vm_create:1133) igt_core-INFO: Stack trace:
(gem_vm_create:1133) igt_core-INFO:   #0 ../lib/igt_core.c:1514 __igt_fail_assert()
(gem_vm_create:1133) igt_core-INFO:   #1 ../tests/i915/gem_vm_create.c:166 __real_main375()
(gem_vm_create:1133) igt_core-INFO:   #2 [<unknown>+0x0]
****  END  ****
Subtest isolation: FAIL (0.024s)

Comment 1 CI Bug Log 2019-06-13 05:27:51 UTC

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

### New filters associated

* BYT: igt@gem_vm_create@isolation - fail - Failed assertion: result == 1, error: 0 != 1
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_305/fi-byt-j1900/igt@gem_vm_create@isolation.html

Comment 2 Chris Wilson 2019-06-13 06:11:56 UTC

Another case where I shouldn't have used gem_read() because we are lying to the kernel about write hazards, I think.

Comment 3 Francesco Balestrieri 2019-07-30 04:28:55 UTC

> Another case where I shouldn't have used gem_read() because we are lying to 
> the kernel about write hazards, I think.

Was there a fix? It hasn't happened again, although there have only been a few runs.

Comment 4 Chris Wilson 2019-08-03 11:11:52 UTC

Nope, I haven't sent a patch for this yet. It will just take a perfect storm to detect.

Comment 5 CI Bug Log 2019-11-20 07:15:54 UTC

A CI Bug Log filter associated to this bug has been updated:

{- BYT: igt@gem_vm_create@isolation - fail - Failed assertion: result == 1, error: 0 != 1 -}
{+ APL BYT: igt@gem_vm_create@isolation - fail - Failed assertion: result == 1, error: 0 != 1 +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7373/shard-apl4/igt@gem_vm_create@isolation.html

Comment 6 Martin Peres 2019-11-29 19:09:55 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/314.

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.