<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - vega56 undervolting/overclocking voltage issues" href="https://bugs.freedesktop.org/show_bug.cgi?id=109887#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - vega56 undervolting/overclocking voltage issues" href="https://bugs.freedesktop.org/show_bug.cgi?id=109887">bug 109887</a> from <a class="email" href="mailto:asheldon55@gmail.com" title="Andrew Sheldon <asheldon55@gmail.com>"> Andrew Sheldon</a> <pre>(In reply to Andrew Sheldon from <a href="show_bug.cgi?id=109887#c9">comment #9</a>) > I will note that you might still see raised voltages if you do a too > aggressive overclock/undervolt with modded PP tables, but it seems to only > overvolt as much as is needed (say 975mv -> 1.05V) if you set a too high > clock, rather than jumping to the maximum possible voltage that you see by > editing pp_od_clk_voltage. Replying to myself here. I've found that the raised voltage occurs when forcing GPU state to "high". If I then re-write the PP table again, it settles on the correct voltage, and successfully switches to "high" after. I'm not sure if this is related to some of the other voltage issues, but there you go. This occurs on both 5.2.3 and 5.3-rc2, for the record. I have to do this every time I force to "high", BTW.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>