[Bug 88411] [HSW] stuck on render ring (screen is repeatedly freezing)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Aug 18 15:14:58 UTC 2017


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

--- Comment #25 from Elizabeth <elizabethx.de.la.torre.mena at intel.com> ---
>From error state with 4.12.3:
HEAD and ACTHD are the different, so execution was inside the batch.
head = 0x00017e30, wraps = 3
ACTHD: 0x00000000 00617e30
    at ring: 0x00000000
FAULT_REG: 0x000000c7
    Valid
    Invalid and Unloaded PD Fault (PPGTT)
    Address 0x00000000
    Source ID 24
hangcheck action: dead

Last command executed IPEHR: 0x7a000002
ring (rcs) at 0x00000000_00002000; HEAD points to: 0x00000000_00019e30
0x00002000:      0x7a000002: PIPE_CONTROL
0x00002004:      0x00100002:    no write, cs stall, stall at scoreboard, 
0x00002008:      0x00000000:    
0x0000200c:      0x00000000:    
0x00002010:      0x7a000002: PIPE_CONTROL
0x00002014:      0x01154c1e:    qword write, cs stall, tlb invalidate,
instruction cache invalidate, texture cache invalidate, vf fetch invalidate,
constant cache invalidate, state cache invalidate, stall at scoreboard, 
0x00002018:      0x7fdee080:    
0x0000201c:      0x00000000:    
0x00002020:      0x18802100: MI_BATCH_BUFFER_START
0x00002024:      0x7fde1000:    dword 1
0x00002028:      0x7a000002: PIPE_CONTROL
0x0000202c:      0x001010a1:    no write, cs stall, render target cache flush,
PIPE_CONTROL flush, DC flush, depth cache flush, 
0x00002030:      0x7fdee080:    
0x00002034:      0x00000000:    
0x00002038:      0x11000001: MI_LOAD_REGISTER_IMM
0x0000203c:      0x00022040:    dword 1
0x00002040:      0x00000db4:    dword 2
0x00002044:      0x11000001: MI_LOAD_REGISTER_IMM
0x00002048:      0x00012044:    dword 1
0x0000204c:      0x00000db4:    dword 2
0x00002050:      0x11000001: MI_LOAD_REGISTER_IMM
0x00002054:      0x0001a044:    dword 1
0x00002058:      0x00000db4:    dword 2
0x0000205c:      0x00000000: MI_NOOP
0x00002060:      0x10800001: MI_STORE_DATA_INDEX
0x00002064:      0x000000c0:    index
0x00002068:      0x00000db4:    dword
0x0000206c:      0x01000000: MI_USER_INTERRUPT
0x00002070:      0x7a000002: PIPE_CONTROL
0x00002074:      0x00100002:    no write, cs stall, stall at scoreboard, 
0x00002078:      0x00000000:    
0x0000207c:      0x00000000:    
0x00002080:      0x7a000002: PIPE_CONTROL
0x00002084:      0x01154c1e:    qword write, cs stall, tlb invalidate,
instruction cache invalidate, texture cache invalidate, vf fetch invalidate,
constant cache invalidate, state cache invalidate, stall at scoreboard, 
0x00002088:      0x7fdee080:    
0x0000208c:      0x00000000: 

This sequence repeats through all the log.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170818/9f27bad5/attachment.html>


More information about the intel-gfx-bugs mailing list