drm/i915: Include a little more information about why ring init fails

If we include the expected values for the failing ring register checks,
it makes it marginally easier to see which is the culprit.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Oscar Mateo <oscar.mateo@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>

1 files changed, 5 insertions, 6 deletions

diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
index 7d99e84f76a3..8a2bd5a7ea9f 100644
--- a/drivers/gpu/drm/i915/intel_ringbuffer.c
+++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
@@ -523,12 +523,11 @@ static int init_ring_common(struct intel_ring_buffer *ring)
                      I915_READ_START(ring) == i915_gem_obj_ggtt_offset(obj) &&
                      (I915_READ_HEAD(ring) & HEAD_ADDR) == 0, 50)) {
                 DRM_ERROR("%s initialization failed "
-                                "ctl %08x head %08x tail %08x start %08x\n",
-                                ring->name,
-                                I915_READ_CTL(ring),
-                                I915_READ_HEAD(ring),
-                                I915_READ_TAIL(ring),
-                                I915_READ_START(ring));
+                          "ctl %08x (valid? %d) head %08x tail %08x start %08x [expected %08lx]\n",
+                          ring->name,
+                          I915_READ_CTL(ring), I915_READ_CTL(ring) & RING_VALID,
+                          I915_READ_HEAD(ring), I915_READ_TAIL(ring),
+                          I915_READ_START(ring), (unsigned long)i915_gem_obj_ggtt_offset(obj));
                 ret = -EIO;
                 goto out;
         }