Mailinglist Archive: opensuse-bugs (6221 mails)

< Previous Next >
[Bug 1084767] 3D & games produce periodic GPU crashes (Radeon R7 370)
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sun, 01 Apr 2018 23:11:04 +0000
  • Message-id: <bug-1084767-21960-3S0aMSffQu@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1084767
http://bugzilla.opensuse.org/show_bug.cgi?id=1084767#c15

--- Comment #15 from Mircea Kitsune <sonichedgehog_hyperblast00@xxxxxxxxx> ---
Created attachment 765652
--> http://bugzilla.opensuse.org/attachment.cgi?id=765652&action=edit
Output of: watch cat /sys/kernel/debug/dri/0/amdgpu_pm_info

I decided to turn my attention to the last logical thing I can imagine: DPM
(Dynamic Power Management) and the clocks on my video card. The kernel added
support for realtime tuning of the frequencies a while ago, so I was pondering
if the default setup may have led to excess overclocking.

I left a console to watch the file /sys/kernel/debug/dri/0/amdgpu_pm_info which
I understand contains the video card frequencies. The maximum "power level" I
seem to reach is 4, at sclk 101500 and mclk 140000. I'm attaching the peak
output of this file here.

My video card is supposed to run at 1015 MHz (core clock) + 5600 MHz (memory
clock). I don't fully understand how those numbers translate to frequencies,
but from what I heard that represents the MHz * 100. If such is the case, my
GPU clock is just right whereas my VRAM is actually under-clocked to a quarter
of its default frequency! Can anyone confirm this so at least the hypothesis of
bad clocks is out of the way?

I may try testing with the kernel parameters "radeon.dpm=0 amdgpu.dpm=0" later:
I tried doing so briefly but the performance is too horrible to play a game, so
I'll instead leave a bot match running in spectator mode while I'm away.

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