Bug 110192 - [CI][DRMTIP] igt@gem_ctx_switch@basic-all-heavy - fail - Failed assertion: !"GPU hung"
Summary: [CI][DRMTIP] igt@gem_ctx_switch@basic-all-heavy - fail - Failed assertion: !"...
Status: RESOLVED DUPLICATE of bug 109960
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-19 10:09 UTC by Lakshmi
Modified: 2019-03-20 17:33 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Lakshmi 2019-03-19 10:09:00 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_245/fi-icl-y/igt@gem_ctx_switch@basic-all-heavy.html

Starting subtest: basic-all-heavy
(gem_ctx_switch:1178) igt_aux-CRITICAL: Test assertion failure function sig_abort, file ../lib/igt_aux.c:500:
(gem_ctx_switch:1178) igt_aux-CRITICAL: Failed assertion: !"GPU hung"
Subtest basic-all-heavy failed.
**** DEBUG ****
(gem_ctx_switch:1178) DEBUG: Test requirement passed: nengine
(gem_ctx_switch:1178) DEBUG: Test requirement passed: __gem_execbuf(fd, &execbuf) == 0
(gem_ctx_switch:1178) DEBUG: Estimated qlen: {min:253, max:269}
(gem_ctx_switch:1178) INFO: Using timing depth of 253 batches
(gem_ctx_switch:1178) igt_aux-CRITICAL: Test assertion failure function sig_abort, file ../lib/igt_aux.c:500:
(gem_ctx_switch:1178) igt_aux-CRITICAL: Failed assertion: !"GPU hung"
(gem_ctx_switch:1178) igt_core-INFO: Stack trace:
(gem_ctx_switch:1178) igt_core-INFO:   #0 ../lib/igt_core.c:1474 __igt_fail_assert()
(gem_ctx_switch:1178) igt_core-INFO:   #1 ../lib/igt_aux.c:504 igt_fork_hang_detector()
(gem_ctx_switch:1178) igt_core-INFO:   #2 [killpg+0x40]
(gem_ctx_switch:1178) igt_core-INFO:   #3 ../sysdeps/unix/sysv/linux/wait.c:29 wait()
(gem_ctx_switch:1178) igt_core-INFO:   #4 ../lib/igt_core.c:1755 __igt_waitchildren()
(gem_ctx_switch:1178) igt_core-INFO:   #5 ../lib/igt_core.c:1806 igt_waitchildren()
(gem_ctx_switch:1178) igt_core-INFO:   #6 ../tests/i915/gem_ctx_switch.c:257 all()
(gem_ctx_switch:1178) igt_core-INFO:   #7 ../tests/i915/gem_ctx_switch.c:341 __real_main297()
(gem_ctx_switch:1178) igt_core-INFO:   #8 ../tests/i915/gem_ctx_switch.c:297 main()
(gem_ctx_switch:1178) igt_core-INFO:   #9 ../csu/libc-start.c:344 __libc_start_main()
(gem_ctx_switch:1178) igt_core-INFO:   #10 [_start+0x2a]
****  END  ****
Subtest basic-all-heavy: FAIL (78.316s)
gem_ctx_switch: ../lib/igt_core.c:1530: igt_exit: Assertion `!num_test_children' failed.
Received signal SIGABRT.
Stack trace: 
 #0 [fatal_sig_handler+0xd5]
 #1 [killpg+0x40]
 #2 [gsignal+0xc7]
 #3 [abort+0x141]
 #4 [uselocale+0x33a]
 #5 [__assert_fail+0x42]
 #6 [igt_exit+0x1e6]
 #7 [main+0x49]
 #8 [__libc_start_main+0xe7]
 #9 [_start+0x2a]
Comment 1 CI Bug Log 2019-03-19 10:10:18 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* ICL: igt@gem_ctx_switch@basic-all-heavy - fail - Failed assertion: !"GPU hung"
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_245/fi-icl-y/igt@gem_ctx_switch@basic-all-heavy.html
Comment 2 Chris Wilson 2019-03-19 10:11:35 UTC
An icl gpu hang doing virtually nothing, you don't say!!! Oh, look it's Mika favourite vcs0.
Comment 3 Chris Wilson 2019-03-19 10:11:55 UTC
<7> [284.754536] hangcheck vcs0
<7> [284.754544] hangcheck 	Hangcheck ad6a22ec:be8e06fe [4032 ms]
<7> [284.754549] hangcheck 	Reset count: 1 (global 0)
<7> [284.754554] hangcheck 	Requests:
<7> [284.754563] hangcheck 		first   17c:8a*+  prio=5 @ 5089ms: gem_ctx_switch[1178]/1d
<7> [284.754572] hangcheck 		last    137:3996  prio=4 @ 5114ms: gem_ctx_switch[1178]/1
<7> [284.754584] hangcheck 		active  17c:8a*+  prio=5 @ 5089ms: gem_ctx_switch[1178]/1d
<7> [284.754589] hangcheck 		ring->start:  0x00d7f000
<7> [284.754593] hangcheck 		ring->head:   0x00001d90
<7> [284.754598] hangcheck 		ring->tail:   0x00001e30
<7> [284.754602] hangcheck 		ring->emit:   0x00001e30
<7> [284.754606] hangcheck 		ring->space:  0x00003c10
<7> [284.754611] hangcheck 		ring->hwsp:   0xffb50a00
<7> [284.754617] hangcheck [head 1dc0, postfix 1e00, tail 1e30, batch 0x00000000_00000000]:
<7> [284.754639] hangcheck [0000] 13244082 00000204 00000000 00000000 02800000 00000000 10400002 ffb50a00
<7> [284.754646] hangcheck [0020] 00000000 00000089 04000001 18800101 00000000 00000000 04000000 00000000
<7> [284.754653] hangcheck [0040] 13004002 ffb50a04 00000000 0000008a 13004002 fffd70d4 00000000 bdc8c15b
<7> [284.754659] hangcheck [0060] 01000000 04000001 02800000 00000000
<7> [284.754679] hangcheck 	RING_START: 0x00d7f000
<7> [284.754686] hangcheck 	RING_HEAD:  0x00001df8
<7> [284.754693] hangcheck 	RING_TAIL:  0x00001e30
<7> [284.754701] hangcheck 	RING_CTL:   0x00003001
<7> [284.754710] hangcheck 	RING_MODE:  0x00000000
<7> [284.754717] hangcheck 	RING_IMR: 00000000
<7> [284.754728] hangcheck 	ACTHD:  0x00000000_0010d044
<7> [284.754739] hangcheck 	BBADDR: 0x00000000_0010d045
<7> [284.754750] hangcheck 	DMA_FADDR: 0x00000000_0010d240
<7> [284.754757] hangcheck 	IPEIR: 0x00000000
<7> [284.754763] hangcheck 	IPEHR: 0x80000000
<7> [284.754772] hangcheck 	Execlist status: 0x00202098 200003c0
<7> [284.754780] hangcheck 	Execlist CSB read 4, write 4 [mmio:4], tasklet queued? no (enabled)
<7> [284.754790] hangcheck 		ELSP[0] count=1, ring:{start:00d7f000, hwsp:ffb50a00, seqno:00000089}, rq:  17c:8a*+  prio=5 @ 5089ms: gem_ctx_switch[1178]/1d
<7> [284.754800] hangcheck 		ELSP[1] count=1, ring:{start:00924000, hwsp:ff9ce600, seqno:00003994}, rq:  137:3996  prio=4 @ 5114ms: gem_ctx_switch[1178]/1
<7> [284.754805] hangcheck 		HW active? 0x5
<7> [284.754814] hangcheck 		E  17c:8a*+  prio=5 @ 5089ms: gem_ctx_switch[1178]/1d
<7> [284.754821] hangcheck 		E  137:3996  prio=4 @ 5114ms: gem_ctx_switch[1178]/1
<7> [284.754825] hangcheck 		Queue priority hint: 4
<7> [284.754832] hangcheck 		Q  139:2760  prio=4 @ 5113ms: gem_ctx_switch[1178]/2
<7> [284.754839] hangcheck 		Q  13b:1e84  prio=4 @ 5113ms: gem_ctx_switch[1178]/3
<7> [284.754846] hangcheck 		Q  17f:84  prio=4 @ 5108ms: gem_ctx_switch[1178]/1e
<7> [284.754853] hangcheck 		Q  183:84  prio=4 @ 5108ms: gem_ctx_switch[1178]/1f
<7> [284.754859] hangcheck 		Q  137:3998  prio=4 @ 5108ms: gem_ctx_switch[1178]/1
<7> [284.754866] hangcheck 		Q  139:2762  prio=4 @ 5107ms: gem_ctx_switch[1178]/2
<7> [284.754872] hangcheck 		Q  13b:1e86  prio=4 @ 5107ms: gem_ctx_switch[1178]/3
<7> [284.754879] hangcheck 		...skipping 14 queued requests...
<7> [284.754885] hangcheck 		Q  13b:1e8c  prio=4 @ 5088ms: gem_ctx_switch[1178]/3
<7> [284.754890] hangcheck HWSP:
<7> [284.754897] hangcheck [0000] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<7> [284.754901] hangcheck *
<7> [284.754909] hangcheck [0040] 00008002 200003e0 00000014 200003e0 00008002 20000400 00000014 20000400
<7> [284.754916] hangcheck [0060] 00008002 200003c0 00000014 200003a0 00000000 00000000 00000000 00000000
<7> [284.754923] hangcheck [0080] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<7> [284.754930] hangcheck [00a0] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000004
<7> [284.754937] hangcheck [00c0] 00000000 00000000 00000000 00000000 ad6a22ec 00000000 00000000 00000000
<7> [284.754944] hangcheck [00e0] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<7> [284.754948] hangcheck *
<7> [284.754957] hangcheck Idle? no
<7> [284.754961] hangcheck Signals:
<7> [284.754968] hangcheck 	[17c:8a*] @ 5089ms
Comment 4 Chris Wilson 2019-03-20 17:33:42 UTC

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


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.