Mailinglist Archive: opensuse-bugs (4790 mails)

< Previous Next >
[Bug 1046962] radeonsi: 3D engines causing frequent GPU lockups
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 27 Jul 2017 09:26:43 +0000
  • Message-id: <bug-1046962-21960-a769wCoVRm@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1046962
http://bugzilla.opensuse.org/show_bug.cgi?id=1046962#c28

--- Comment #28 from Max Staudt <mstaudt@xxxxxxxx> ---
This... is weird. So if I understand correctly, you've been running 3D
applications, yet the only client shown in "clients" is X? Okay, that file
isn't being helpful...

So it seems that the most interesting are radeon_gtt_mm, radeon_vram_mm, and
ttm_dma_page_pool. I'm not sure what the last one says, but the former two
should, together, list all allocations. Unfortunately we can only see the first
few lines of each now, since watch cuts off the output where it overruns the
screen.

So...

while true ; do clear ; echo $(( $(cat /sys/kernel/debug/dri/0/radeon_vram_mm
| tail -n +3 | cut -d : -f 2 | sed "s/$/ + /") 0 )) ; sleep 1 ; done

and

while true ; do clear ; echo $(( $(cat /sys/kernel/debug/dri/0/radeon_gtt_mm
| tail -n +3 | cut -d : -f 2 | sed "s/$/ + /") 0 )) ; sleep 1 ; done

should sum them up. This way, you can watch whether some operation reserves
more VRAM without freeing it.

Silly me forgot to also ask for

dmesg -w

which is dmesg in 'watch' mode. Your kernel will probably start screaming once
the problems appear.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References