[Bug 99001] [HSW] GPU HANG: ecode 7:0:0x85dffffc, in glxspheres64 [4492], reason: Hang on render ring, action: reset

[bugzilla-daemon at freedesktop.org]

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

yann <yann.argotti at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|yann.argotti at intel.com      |chris at chris-wilson.co.uk

--- Comment #15 from yann <yann.argotti at intel.com> ---
(In reply to Jari Tahvanainen from comment #14)
> Yann, use five minutes and check out if new crash log give any new
> indication about the reason for hang.
> I also removed bisected keyword since assumable that is not the case.

According to mesa engineers, mesa only emits 3DSTATE_VERTEX_ELEMENTS on-demand
right before 3DPRIMITIVE.

Chris has changed SNA to emit a dummy primitive between VertexElements in 
4acd4a7d3d2f41227022fa7581cfb85a0b124eae in xf86-video-intel (thanks to
https://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=4acd4a7d3d2f41227022fa7581cfb85a0b124eae)
but this is for gen9. Here we are dealing with gen7, do we need such mechanism
as well in gen7_emit_vertex_elements?

An alternate solution is to use Glamor/modesetting.

*Details:
- Kernel: 4.9.0-rc8inteldri+
- Platform: Haswell (PCI ID: 0x0416, PCI Revision: 0x06, PCI Subsystem:
1462:10e0)
- Mesa: 13.0.2-2
- xf86-video-intel: 2.99.917.740.g9ac7a33-1



0x008a0540:      0x78090001: 3DSTATE_VERTEX_ELEMENTS
0x008a0544:      0x02850000:    buffer 0: valid, type 0x0085, src offset 0x0000
bytes
0x008a0548:      0x11230000:    (X, Y, 0.0, 1.0), dst offset 0x00 bytes
0x008a054c:      0x7b000005: 3DPRIMITIVE:
0x008a0550:      0x00000006:    tri fan sequential
0x008a0554:      0x00000004:    vertex count
0x008a0558:      0x00000000:    start vertex
0x008a055c:      0x00000001:    instance count
0x008a0560:      0x00000000:    start instance
0x008a0564:      0x00000000:    index bias
0x008a0568:      0x7a000003: PIPE_CONTROL
0x008a056c:      0x00101001:    no write, cs stall, render target cache flush,
depth cache flush,
0x008a0570:      0x00000000:    destination address
0x008a0574:      0x00000000:    immediate dword low
0x008a0578:      0x00000000:    immediate dword high
0x008a057c:      0x7a000003: PIPE_CONTROL
0x008a0580:      0x00000c10:    no write, instruction cache invalidate, texture
cache invalidate, vf fetch invalidate,
0x008a0584:      0x00000000:    destination address
0x008a0588:      0x00000000:    immediate dword low
0x008a058c:      0x00000000:    immediate dword high

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20170130/4a972a26/attachment.html>