On Sun, Feb 24, 2013 at 06:10:02PM -0800, Ben Widawsky wrote: > On error, this represents the state of the currently running context at > the time it was loaded. > > Unfortunately, since we're hung and can't switch out the context this > may not tell us too much about the most current state of the context, > but does give clues about what has happened since loading. > > Thanks to recent doc updates, we have a little more confidence regarding > what is actually in this memory, and perhaps it will help us gain more > insight into certain bugs. AFAICT, the most interesting info is in the > first page. To save space, we only capture the first page. In the > future, we might want to dump more. > > Sample of the relevant part of error state: > render ring --- HW Context = 0x01b20000 > [0000] 00000000 1100105f 00002028 ffff0880 > [0010] 0000209c feff4040 000020c0 efdf0080 > [0020] 00002178 00000001 0000217c 00145855 > [0030] 00002310 00000000 00002314 00000000 > > v2: Move error collection to the ring error code > Change format of dump to not confuse intel_error_decode (Chris) > Put the context error object with the others (Chris) > Don't search bound_list instead of active_list (chris) > > References: https://bugs.freedesktop.org/show_bug.cgi?id=55845 > Cc: Chris Wilson <chris at chris-wilson.co.uk> > Signed-off-by: Ben Widawsky <ben at bwidawsk.net> Can't spot anything else to nag about so all 3 are Reviewed-by: Chris Wilson <chris at chris-wilson.co.uk> -Chris -- Chris Wilson, Intel Open Source Technology Centre
