path: root/drivers/gpu/drm/i915/i915_gpu_error.c
diff options
authorBen Widawsky <benjamin.widawsky@intel.com>2013-08-12 16:53:03 -0700
committerDaniel Vetter <daniel.vetter@ffwll.ch>2013-08-22 13:31:42 +0200
commit5020150b3b8d2912466e28572f25b3cc56722aec (patch)
tree998683ba8392670c7b3cd9878ba3c13c26c69d12 /drivers/gpu/drm/i915/i915_gpu_error.c
parent351aa5666d02062b52329bcfe4bcf9d1f882fba9 (diff)
drm/i915: Initialize seqno for VECS too
We require n-1 mailboxes for proper semaphore synchronization. All semaphore synchronization code relies on proper values in these mailboxes. The fact that we failed to touch the vebox ring by itself was unlikely to be an issue since the HW should be initializing the values to 0. However the error framework for testing seqno wrap introduced by Mika, in addition to the hangcheck via seqno, and i915_error_first_batchbuffer() combined caused a nice explosion. The problem is caused by seqno wrap because the wrap condition is not properly setup. The wrap code attempts to set the sync mailboxes all to 0, and then set the current seqno to one less than 0. In all cases, the vebox mailbox wasn't properly being initialized. This caused a wrap to not occur. When hangcheck kicks in with the bogus seqno values, the rest just doesn't work. It makes me wonder if we shouldn't consider a dumber version of hangcheck... How we messed this up: VECS support was written before the aforementioned other features. Upon VECS being rebased, these facts were missed. Cc: Mika Kuoppala <mika.kuoppala@intel.com> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=65387 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=67198 Signed-off-by: Ben Widawsky <ben@bwidawsk.net> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/gpu/drm/i915/i915_gpu_error.c')
0 files changed, 0 insertions, 0 deletions