5 Following a GPU hang the MSM driver outputs debugging information via
6 /sys/kernel/dri/X/show or via devcoredump (/sys/class/devcoredump/dcdX/data).
7 This document describes how the output is formatted.
9 Each entry is in the form key: value. Sections headers will not have a value
10 and all the contents of a section will be indented two spaces from the header.
11 Each section might have multiple array entries the start of which is designated
18 The kernel version that generated the dump (UTS_RELEASE).
21 The module that generated the crashdump.
24 The kernel time at crash formated as seconds.microseconds.
27 Comm string for the binary that generated the fault.
30 Command line for the binary that generated the fault.
33 ID of the GPU that generated the crash formatted as
34 core.major.minor.patchlevel separated by dots.
37 The current value of RBBM_STATUS which shows what top level GPU
38 components are in use at the time of crash.
41 Section containing the contents of each ringbuffer. Each ringbuffer is
42 identified with an id number.
45 Ringbuffer ID (0 based index). Each ringbuffer in the section
46 will have its own unique id.
48 GPU address of the ringbuffer.
51 The last fence that was issued on the ringbuffer
54 The last fence retired on the ringbuffer.
57 The current read pointer (rptr) for the ringbuffer.
60 The current write pointer (wptr) for the ringbuffer.
63 Set of registers values. Each entry is on its own line enclosed
67 Byte offset of the register from the start of the
71 Hexadecimal value of the register.