[Bug 103479] [CI] igt@[gem_flink_basic at bad-open | igt at drv_module_reload@basic-reload] *ERROR* Timeout waiting for engines to idle

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Nov 3 14:11:50 UTC 2017


https://bugs.freedesktop.org/show_bug.cgi?id=103479

--- Comment #6 from Chris Wilson <chris at chris-wilson.co.uk> ---
Still!!!

<3>[  100.640238] [drm:intel_engines_park [i915]] *ERROR* vecs0 is not idle
before parking
<7>[  100.640569] intel_engines_park vecs0
<7>[  100.640586] intel_engines_park    current seqno 19a, last 19a, hangcheck
14a [5856 ms], inflight 0
<7>[  100.640598] intel_engines_park    Reset count: 0
<7>[  100.640662] intel_engines_park    Requests:
<7>[  100.640895] intel_engines_park    RING_START: 0x00000000 [0x00000000]
<7>[  100.640913] intel_engines_park    RING_HEAD:  0x00000000 [0x00000000]
<7>[  100.640931] intel_engines_park    RING_TAIL:  0x00000000 [0x00000000]
<7>[  100.640952] intel_engines_park    RING_CTL:   0x00000000
<7>[  100.640974] intel_engines_park    RING_MODE:  0x00000200 [idle]
<7>[  100.641000] intel_engines_park    ACTHD:  0x00000000_00000000
<7>[  100.641025] intel_engines_park    BBADDR: 0x00000000_00000000
<7>[  100.641046] intel_engines_park    Execlist status: 0x00000301 00000000
<7>[  100.641064] intel_engines_park    Execlist CSB read 3 [3 cached], write 3
[3 from hws], interrupt posted? no
<7>[  100.641079] intel_engines_park            ELSP[0] idle
<7>[  100.641092] intel_engines_park            ELSP[1] idle
<7>[  100.641105] intel_engines_park            HW active? 0x0
<7>[  100.641294] intel_engines_park 

Afaict, that should pose no problems in being recognised as idle; so is it
still idling between the check and the print? Possibly.

-- 
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/20171103/c4c926f6/attachment-0001.html>


More information about the intel-gfx-bugs mailing list