<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Crashes / Resets From AMDGPU / Radeon VII" href="https://bugs.freedesktop.org/show_bug.cgi?id=110674#c129">Comment # 129</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Crashes / Resets From AMDGPU / Radeon VII" href="https://bugs.freedesktop.org/show_bug.cgi?id=110674">bug 110674</a> from <a class="email" href="mailto:tom@r.je" title="Tom B <tom@r.je>"> Tom B</a> <pre>Thank you Alex! That has fixed it! The card is now correctly setting its voltages and clocks. I applied the patch to 5.3.1 However, I've noticed a few very minor problems that are probably worth reporting. 1. I still get this in dmesg: [ 6.307005] amdgpu: [powerplay] Failed to send message 0x28, response 0x0 [ 6.307006] amdgpu: [powerplay] [SetHardMinFreq] Set hard min uclk failed! [ 9.225192] amdgpu 0000:44:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on sdma0 (-110). [ 10.238621] amdgpu 0000:44:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on page0 (-110). [ 10.532004] amdgpu: [powerplay] Failed to send message 0x26, response 0x0 [ 10.532005] amdgpu: [powerplay] Failed to set soft min gfxclk ! [ 10.532006] amdgpu: [powerplay] Failed to upload DPM Bootup Levels! Though this doesn't really matter, we were focussing our issue there earlier in the thread as it looked like `Set hard min uclk failed!` was the cause of the problem, obviously it isn't. 2. This repeats indefinitely in dmesg: [ 332.575747] [drm] schedsdma0 is not ready, skipping [ 332.582657] [drm] schedsdma0 is not ready, skipping [ 332.582864] [drm] schedsdma0 is not ready, skipping [ 332.708848] [drm] schedsdma0 is not ready, skipping [ 332.715975] [drm] schedsdma0 is not ready, skipping [ 332.716229] [drm] schedsdma0 is not ready, skipping [ 332.756987] [drm] schedsdma0 is not ready, skipping [ 332.763970] [drm] schedsdma0 is not ready, skipping [ 332.764169] [drm] schedsdma0 is not ready, skipping As you can see several dozens of times second this gets written to dmesg. This might be because the patches are intended to be used on 5.4? 3. The lowest wattage now seems to be 33w rather than 23w which means increased idle power usage and temps. This isn't really a problem but I thought it was worth mentioning and is a fair tradeoff for stability.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>