[Bug 106947] [CI] igt at drv_selftest@live_hangcheck - dmesg-fail - Failed to switch back to kernel context; declaring wedged
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Jun 18 07:34:22 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=106947
--- Comment #1 from Chris Wilson <chris at chris-wilson.co.uk> ---
Hmm, this is a different symptom than bug 106560. Instead of the RING_MODE
being disabled (with RING_STOP), here it looks like we missed kicking the
tasklet:
<7>[ 374.261828] i915_gem_set_wedged vcs0
<7>[ 374.261831] i915_gem_set_wedged current seqno 13814, last 13814,
hangcheck 0 [5263 ms]
<7>[ 374.261834] i915_gem_set_wedged Reset count: 5598 (global 1)
<7>[ 374.261838] i915_gem_set_wedged Requests:
<7>[ 374.261869] i915_gem_set_wedged RING_START: 0x00109000
<7>[ 374.261873] i915_gem_set_wedged RING_HEAD: 0x00001cf8
<7>[ 374.261877] i915_gem_set_wedged RING_TAIL: 0x00001cf8
<7>[ 374.261883] i915_gem_set_wedged RING_CTL: 0x00003000
<7>[ 374.261889] i915_gem_set_wedged RING_MODE: 0x00000200 [idle]
<7>[ 374.261893] i915_gem_set_wedged RING_IMR: fffffeff
<7>[ 374.261901] i915_gem_set_wedged ACTHD: 0x00000000_00201cf8
<7>[ 374.261908] i915_gem_set_wedged BBADDR: 0x00000000_00000000
<7>[ 374.261916] i915_gem_set_wedged DMA_FADDR: 0x00000000_00000000
<7>[ 374.261920] i915_gem_set_wedged IPEIR: 0x00000000
<7>[ 374.261924] i915_gem_set_wedged IPEHR: 0x00000000
<7>[ 374.261930] i915_gem_set_wedged Execlist status: 0x00000301 00000000
<7>[ 374.261936] i915_gem_set_wedged Execlist CSB read 2 [2 cached], write 5
[5 from hws], interrupt posted? yes, tasklet queued? no (enabled)
<7>[ 374.261942] i915_gem_set_wedged Execlist CSB[3]: 0x00000001 [0x00000001
in hwsp], context: 0 [0 in hwsp]
<7>[ 374.261949] i915_gem_set_wedged Execlist CSB[4]: 0x00000014 [0x00000014
in hwsp], context: 81 [81 in hwsp]
<7>[ 374.261956] i915_gem_set_wedged Execlist CSB[5]: 0x00000018 [0x00000018
in hwsp], context: 84 [84 in hwsp]
<7>[ 374.261962] i915_gem_set_wedged ELSP[0] count=1,
ring->start=000d8000, rq: 13813! [aef:175] prio=395 @ 5261ms: signaled
<7>[ 374.261967] i915_gem_set_wedged ELSP[1] count=1,
ring->start=00109000, rq: 13814! [af2:174] prio=292 @ 5261ms: signaled
<7>[ 374.261988] i915_gem_set_wedged HW active? 0x1
<7>[ 374.261991] i915_gem_set_wedged Queue priority: 292
<7>[ 374.261996] i915_gem_set_wedged Q 0 [af0:174] prio=248 @
5265ms: igt/vcs0[5775]/5
<7>[ 374.262000] i915_gem_set_wedged Q 0 [af0:175] prio=236 @
5261ms: igt/vcs0[5775]/5
<7>[ 374.262004] i915_gem_set_wedged Q 0 [aed:175] prio=195 @
5262ms: igt/vcs0[5775]/2
<7>[ 374.262009] i915_gem_set_wedged Q 0 [af3:174] prio=136 @
5262ms: igt/vcs0[5775]/8
<7>[ 374.262014] i915_gem_set_wedged Q 0 [aec:175] prio=134 @
5262ms: igt/vcs0[5775]/1
<7>[ 374.262019] i915_gem_set_wedged Q 0 [aee:175] prio=13 @ 5262ms:
igt/vcs0[5775]/3
<7>[ 374.262022] i915_gem_set_wedged IRQ? 0x3 (breadcrumbs? yes) (execlists?
yes)
<7>[ 374.262024] i915_gem_set_wedged HWSP:
<7>[ 374.262029] i915_gem_set_wedged [0000] 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000
<7>[ 374.262031] i915_gem_set_wedged *
<7>[ 374.262037] i915_gem_set_wedged [0040] 00000001 00000000 00000014
00000003 00000018 00000053 00000001 00000000
<7>[ 374.262041] i915_gem_set_wedged [0060] 00000014 00000051 00000018
00000054 00000000 00000000 00000000 00000005
<7>[ 374.262044] i915_gem_set_wedged [0080] 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000
<7>[ 374.262047] i915_gem_set_wedged *
<7>[ 374.262051] i915_gem_set_wedged [00c0] 00013814 00000000 00000000
00000000 00000000 00000000 00000000 00000000
<7>[ 374.262055] i915_gem_set_wedged [00e0] 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000
<7>[ 374.262057] i915_gem_set_wedged *
<7>[ 374.262103] i915_gem_set_wedged Idle? no
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180618/60a92502/attachment.html>
More information about the intel-gfx-bugs
mailing list