Bug 110873

Summary:	[CI][DRMTIP] igt@gem_ctx_isolation@rcs0-dirty-switch - fail - Failed assertion: !"GPU hung"
Product:	DRI	Reporter:	Lakshmi <lakshminarayana.vudum>
Component:	DRM/Intel	Assignee:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Status:	RESOLVED WORKSFORME	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:	I965G	i915 features:	GPU hang

Description Lakshmi 2019-06-10 10:24:27 UTC

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_302/fi-bwr-2160/igt@gem_ctx_isolation@rcs0-dirty-switch.html

	
Starting subtest: rcs0-dirty-switch
(gem_ctx_isolation:1223) igt_aux-CRITICAL: Test assertion failure function sig_abort, file ../lib/igt_aux.c:502:
(gem_ctx_isolation:1223) igt_aux-CRITICAL: Failed assertion: !"GPU hung"
Subtest rcs0-dirty-switch failed.
**** DEBUG ****
(gem_ctx_isolation:1223) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(gem_ctx_isolation:1223) drmtest-DEBUG: Test requirement passed: is_i915_device(fd) && has_known_intel_chipset(fd)
(gem_ctx_isolation:1223) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(gem_ctx_isolation:1223) ioctl_wrappers-DEBUG: Test requirement passed: dir >= 0
(gem_ctx_isolation:1223) ioctl_wrappers-DEBUG: Test requirement passed: err == 0
(gem_ctx_isolation:1223) ioctl_wrappers-DEBUG: Test requirement passed: gem_has_ring(fd, ring)
(gem_ctx_isolation:1223) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_ctx_isolation:1223) DEBUG: isolation[0]: Setting all registers of ctx 1 to 0xffffffff
(gem_ctx_isolation:1223) igt_aux-CRITICAL: Test assertion failure function sig_abort, file ../lib/igt_aux.c:502:
(gem_ctx_isolation:1223) igt_aux-CRITICAL: Failed assertion: !"GPU hung"
(gem_ctx_isolation:1223) igt_core-INFO: Stack trace:
(gem_ctx_isolation:1223) igt_core-INFO:   #0 ../lib/igt_core.c:1509 __igt_fail_assert()
(gem_ctx_isolation:1223) igt_core-INFO:   #1 [sig_abort+0x3a]
(gem_ctx_isolation:1223) igt_core-INFO:   #2 [killpg+0x40]
(gem_ctx_isolation:1223) igt_core-INFO:   #3 ../sysdeps/unix/syscall-template.S:78 ioctl()
(gem_ctx_isolation:1223) igt_core-INFO:   #4 /home/cidrm/libdrm/xf86drm.c:191 drmIoctl()
(gem_ctx_isolation:1223) igt_core-INFO:   #5 ../lib/ioctl_wrappers.c:591 __gem_execbuf()
(gem_ctx_isolation:1223) igt_core-INFO:   #6 ../lib/ioctl_wrappers.c:609 gem_execbuf()
(gem_ctx_isolation:1223) igt_core-INFO:   #7 ../tests/i915/gem_ctx_isolation.c:327 read_regs.isra.5()
(gem_ctx_isolation:1223) igt_core-INFO:   #8 ../tests/i915/gem_ctx_isolation.c:658 isolation()
(gem_ctx_isolation:1223) igt_core-INFO:   #9 ../tests/i915/gem_ctx_isolation.c:847 __real_main809()
(gem_ctx_isolation:1223) igt_core-INFO:   #10 ../tests/i915/gem_ctx_isolation.c:809 main()
(gem_ctx_isolation:1223) igt_core-INFO:   #11 ../csu/libc-start.c:344 __libc_start_main()
(gem_ctx_isolation:1223) igt_core-INFO:   #12 [_start+0x2a]
****  END  ****
Subtest rcs0-dirty-switch: FAIL (15.957s)

Comment 1 CI Bug Log 2019-06-10 10:26:14 UTC

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

### New filters associated

* BWR: igt@gem_ctx_isolation@rcs0-dirty-switch - fail - Failed assertion: !&quot;GPU hung&quot;
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_302/fi-bwr-2160/igt@gem_ctx_isolation@rcs0-dirty-switch.html

Comment 2 Chris Wilson 2019-06-10 10:40:46 UTC

First drm-tip with this test enabled on brw. I may have used illegal commands for brw -- or the context switch may truly be snafu.

Comment 3 Chris Wilson 2019-06-17 11:16:51 UTC

Seems to work on my T61 (crestline), so not a simple case of broken GPU commands. I will leave it in a loop, just in case.

Comment 4 Chris Wilson 2019-07-12 14:29:47 UTC

It doesn't seem to be consistent (i.e. it doesn't seem to happen on every run, or even again). Pretending it doesn't exist until it happens again and we can perhaps establish a pattern.

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.