Documentation/gpu: How to collect DTN log
Introduce how to collect DTN log from debugfs. Reviewed-by: Yann Dirson <ydirson@free.fr> Reviewed-by: Harry Wentland <harry.wentland@amd.com> Signed-off-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
This commit is contained in:
committed by
Alex Deucher
parent
b2568d6834
commit
76659755b4
@@ -58,3 +58,20 @@ In this case, if you have a pipe split, you will see one small red bar at the
|
|||||||
bottom of the display covering the entire display width and another bar
|
bottom of the display covering the entire display width and another bar
|
||||||
covering the second pipe. In other words, you will see a bit high bar in the
|
covering the second pipe. In other words, you will see a bit high bar in the
|
||||||
second pipe.
|
second pipe.
|
||||||
|
|
||||||
|
DTN Debug
|
||||||
|
=========
|
||||||
|
|
||||||
|
DC (DCN) provides an extensive log that dumps multiple details from our
|
||||||
|
hardware configuration. Via debugfs, you can capture those status values by
|
||||||
|
using Display Test Next (DTN) log, which can be captured via debugfs by using::
|
||||||
|
|
||||||
|
cat /sys/kernel/debug/dri/0/amdgpu_dm_dtn_log
|
||||||
|
|
||||||
|
Since this log is updated accordingly with DCN status, you can also follow the
|
||||||
|
change in real-time by using something like::
|
||||||
|
|
||||||
|
sudo watch -d cat /sys/kernel/debug/dri/0/amdgpu_dm_dtn_log
|
||||||
|
|
||||||
|
When reporting a bug related to DC, consider attaching this log before and
|
||||||
|
after you reproduce the bug.
|
||||||
|
|||||||
Reference in New Issue
Block a user