Difference between revisions of "Development:Debugging Adreno Crash"
Jump to navigation
Jump to search
(Created page with "== Information from upstream == This is Adreno's documentation [https://docs.mesa3d.org/drivers/freedreno.html#gpu-devcoredump here] == Timeout related == The default hangch...") |
|||
| Line 1: | Line 1: | ||
== Information from upstream == | == Information from upstream == | ||
| − | This is Adreno's documentation [https://docs.mesa3d.org/drivers/freedreno.html#gpu-devcoredump here] | + | This is Adreno's documentation [https://docs.mesa3d.org/drivers/freedreno.html#gpu-devcoredump here]. Has some good information about storing devcoredumps for GPU backtraces. |
== Timeout related == | == Timeout related == | ||
Revision as of 02:01, 27 February 2023
Information from upstream
This is Adreno's documentation here. Has some good information about storing devcoredumps for GPU backtraces.
The default hangcheck timeout is only 250ms, this can be increased for testing purposes if suspected that for some reason it's just a long compute job.
echo "20000" | sudo tee /sys/kernel/debug/dri/0/hangcheck_period_ms
Sometimes the issue might be related to performance. You can set the GPU clocks to the maximum for testing
cat /sys/devices/platform/soc@0/3d00000.gpu/devfreq/3d00000.gpu/max_freq | sudo tee /sys/devices/platform/soc@0/3d00000.gpu/devfreq/3d00000.gpu/min_freq
Probably some easier way to reach that node.
Seeing GPU load
If you want to know how loaded the GPU is.
sudo cat /sys/kernel/debug/dri/0/perf