<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI] igt@gem_exec_* - fail - Failed assertion: !"GPU hung""
href="https://bugs.freedesktop.org/show_bug.cgi?id=105900#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI] igt@gem_exec_* - fail - Failed assertion: !"GPU hung""
href="https://bugs.freedesktop.org/show_bug.cgi?id=105900">bug 105900</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=105900#c5">comment #5</a>)
<span class="quote">> (In reply to Martin Peres from <a href="show_bug.cgi?id=105900#c4">comment #4</a>)
> > <a href="https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_29/fi-cnl-y3/">https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_29/fi-cnl-y3/</a>
> > igt@<a href="mailto:gem_exec_await@wide-contexts.html">gem_exec_await@wide-contexts.html</a>
> >
> > (gem_exec_await:2291) igt_aux-CRITICAL: Test assertion failure function
> > sig_abort, file ../lib/igt_aux.c:481:
> > (gem_exec_await:2291) igt_aux-CRITICAL: Failed assertion: !"GPU hung"
> > Subtest wide-contexts failed.
>
> This is a different issue. The GPU hang here is a result of hitting a
> blocking ioctl in the test.</span >
Using Execlists submission
Ring size: 143 batches
If we can only fit 143 batches in a ring, why did we submit 144?...
<7>[ 134.752155] hangcheck bcs0
<7>[ 134.752174] hangcheck current seqno c707, last c797, hangcheck c707
[4031 ms]
<7>[ 134.752178] hangcheck Reset count: 0 (global 0)
<7>[ 134.752181] hangcheck Requests:
<7>[ 134.752192] hangcheck first c708 [4e0a:1] prio=0 @ 4047ms:
gem_exec_await[2291]/3
<7>[ 134.752196] hangcheck last c797 [4e0a:90] prio=0 @ 4037ms:
gem_exec_await[2291]/3
<7>[ 134.752207] hangcheck active c708 [4e0a:1] prio=0 @ 4047ms:
gem_exec_await[2291]/3
<7>[ 134.752212] hangcheck [head 0000, postfix 0030, tail 0050,
batch 0x00000000_00040000]
<7>[ 134.752215] hangcheck ring->start: 0x035a8000
<7>[ 134.752218] hangcheck ring->head: 0x00000000
<7>[ 134.752221] hangcheck ring->tail: 0x00002cf8
<7>[ 134.752224] hangcheck ring->emit: 0x00002d00
<7>[ 134.752227] hangcheck ring->space: 0x000012c0
<7>[ 134.752232] hangcheck RING_START: 0x035a8000
<7>[ 134.752237] hangcheck RING_HEAD: 0x00000020
<7>[ 134.752241] hangcheck RING_TAIL: 0x00002cf8
<7>[ 134.752246] hangcheck RING_CTL: 0x00003001
<7>[ 134.752252] hangcheck RING_MODE: 0x00000000
<7>[ 134.752256] hangcheck RING_IMR: feffffff
<7>[ 134.752263] hangcheck ACTHD: 0x00000000_00040000
<7>[ 134.752271] hangcheck BBADDR: 0x00000000_00040001
<7>[ 134.752277] hangcheck DMA_FADDR: 0x00000000_00040200
<7>[ 134.752282] hangcheck IPEIR: 0x00000000
<7>[ 134.752286] hangcheck IPEHR: 0x18800101
<7>[ 134.752292] hangcheck Execlist status: 0x00024049 0000057e
<7>[ 134.752297] hangcheck Execlist CSB read 1 [1 cached], write 1 [1 from
hws], interrupt posted? no, tasklet queued? no (enabled)
<7>[ 134.752302] hangcheck ELSP[0] count=1, rq: c797 [4e0a:90]
prio=0 @ 4037ms: gem_exec_await[2291]/3
<7>[ 134.752305] hangcheck ELSP[1] idle
<7>[ 134.752308] hangcheck HW active? 0x5
<7>[ 134.752355] hangcheck E c708 [4e0a:1] prio=0 @ 4047ms:
gem_exec_await[2291]/3
<7>[ 134.752392] hangcheck E c709 [4e0a:2] prio=0 @ 4047ms:
gem_exec_await[2291]/3
<7>[ 134.752396] hangcheck E c70a [4e0a:3] prio=0 @ 4047ms:
gem_exec_await[2291]/3
<7>[ 134.752399] hangcheck E c70b [4e0a:4] prio=0 @ 4047ms:
gem_exec_await[2291]/3
<7>[ 134.752403] hangcheck E c70c [4e0a:5] prio=0 @ 4047ms:
gem_exec_await[2291]/3
<7>[ 134.752407] hangcheck E c70d [4e0a:6] prio=0 @ 4047ms:
gem_exec_await[2291]/3
<7>[ 134.752411] hangcheck E c70e [4e0a:7] prio=0 @ 4047ms:
gem_exec_await[2291]/3
<7>[ 134.752427] hangcheck ...skipping 136 executing requests...
<7>[ 134.752431] hangcheck E c797 [4e0a:90] prio=0 @ 4037ms:
gem_exec_await[2291]/3
<7>[ 134.752434] hangcheck Queue priority: -2147483648</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>