<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Hang regression with R7 M370, identified possible culprit commit"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100222#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Hang regression with R7 M370, identified possible culprit commit"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100222">bug 100222</a>
from <span class="vcard"><a class="email" href="mailto:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> <span class="fn">Alex Deucher</span></a>
</span></b>
<pre>(In reply to Mauro Santos from <a href="show_bug.cgi?id=100222#c3">comment #3</a>)
<span class="quote">> 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?</span >
The patch modifies si_apply_state_adjust_rules, I guess it's not applying
cleanly to your kernel.
<span class="quote">>
> 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.</span >
There is still some bug in the driver that prevents the higher clocks for
working stable on your card. We fixed some issues and the driver was working
on the hardware samples we had in house (which is why I removed the
workaround), but apparently there are still some variants that are not working
correctly.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>