[Bug 100222] Hang regression with R7 M370, identified possible culprit commit

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=100222

--- Comment #3 from Mauro Santos <registo.mailling at gmail.com> ---
Build fails after applying patch 1 followed by patch 2 with:


drivers/gpu/drm/radeon/si_dpm.c: In function ‘si_get_vce_clock_voltage’:
drivers/gpu/drm/radeon/si_dpm.c:2977:4: error: ‘else’ without a previous ‘if’
  } else if (rdev->family == CHIP_OLAND) {
    ^~~~
drivers/gpu/drm/radeon/si_dpm.c:2985:4: error: ‘max_sclk’ undeclared (first use
in this function)
    max_sclk = 75000;
    ^~~~~~~~
drivers/gpu/drm/radeon/si_dpm.c:2985:4: note: each undeclared identifier is
reported only once for each function it appears in


The patch changes things inside the si_get_vce_clock_voltage function but I
suppose the changes should be made a few lines bellow that to the
si_apply_state_adjust_rules function after the quirks for pitcairn and hainan
right?

Another thing that I'm curious about, any guesses as to why the card needs the
maximum core clock limited to 750MHz on linux but seems to work fine on windows
10 at 875MHz? I've tried it on Windows 10 (all drivers downloaded via windows
update) with unigine heaven + cpu-z to monitor the frequencies and it seems to
go along happily with 875MHz core and 900MHz memory clocks.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170316/b2832c56/attachment.html>