[Bug 101522] [bsw] lite-restore failed on vcs

[bugzilla-daemon at freedesktop.org]

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

--- Comment #17 from Elizabeth <elizabethx.de.la.torre.mena at intel.com> ---
>From error state:

bsd command stream:

  HEAD:  0x52e01df0 [0x00001df0]
    head = 0x00001df0, wraps = 663
  ACTHD: 0x00000000 52e01df0
    at ring: 0x00000000
  ...
  IPEHR: 0x00000000
  ...
  seqno: 0x0090ea64
  last_seqno: 0x0090ea66
  waiting: yes
  ring->head: 0x00001dd0
  ring->tail: 0x00001f30
  hangcheck stall: yes
  hangcheck action: dead
  hangcheck action timestamp: 4314722752, 10059896 ms ago
  ELSP[0]:  pid 1307, ban score 0, seqno        5:0090ea65, emitted 10061652ms
ago, head 00001df0, tail 00001e40
  ELSP[1]:  pid 1682, ban score 0, seqno        6:0090ea66, emitted 10061640ms
ago, head 000015d0, tail 00001618
  Active context: ffmpeg[1307] user_handle 0 hw_id 5, ban score 0 guilty 0
active 0

batch (vcs (submitted by ffmpeg [1307], ctx 0 [5], score 0)) at
0x00000000_ff354000
0xff354000:      0x13000082: MI_FLUSH_DW post_sync_op='no write'  invalidate
video state (BCS-only),
0xff354004:      0x00000000:    address
0xff354008:      0x00000000:    dword
0xff35400c:      0x00000000:    upper dword
0xff354010:      0x70000003: 3D UNKNOWN: 3d_965 opcode = 0x7000
0xff354014:      0x00020202: MI_NOOP
0xff354018:      0x00000000: MI_NOOP
0xff35401c:      0x00000000: MI_NOOP
0xff354020:      0x00000000: MI_NOOP
0xff354024:      0x70010004: 3D UNKNOWN: 3d_965 opcode = 0x7001
0xff354028:      0x00000000: MI_NOOP
Bad length (114) in MI_SEMAPHORE_MBOX, [3, 3]
0xff35402c:      0x0b3c4ff0: MI_SEMAPHORE_MBOX update semaphore, compare
semaphore, use compare reg 0
0xff354030:      0x480027fb:    value
0xff354034:      0x000002e0:    address

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