<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Radeonsi on Grenada cards (r9 390) exceptionally unstable and poorly performing" href="https://bugs.freedesktop.org/show_bug.cgi?id=91880#c55">Comment # 55</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Radeonsi on Grenada cards (r9 390) exceptionally unstable and poorly performing" href="https://bugs.freedesktop.org/show_bug.cgi?id=91880">bug 91880</a> from <a class="email" href="mailto:dev@illwieckz.net" title="Thomas DEBESSE <dev@illwieckz.net>"> Thomas DEBESSE</a> <pre>Hi, I made some tests, I discovered that my R9 390X works very well if I never load the "auto" `power_dpm_force_performance_level` profile, both "low" and "high" works. Also, both `power_dpm_state` "balanced", "battery", "performance" works. So, I wrote a little systemd service that load the "low/battery" profile at startup (just before multi-user.target so it's loaded before the login manager startup. I discovered I can switch `power_dpm_force_performance_level` profile to the value I want and the same for `power_dpm_state` without any crashing, even when an heavy task (like Unigine Valley Benchmark) is running. The fault is on the "auto" `power_dpm_force_performance_level` profile, and only that. All other options work. If you want to workaround the bug, you can use my service: <a href="https://github.com/illwieckz/dpm-query/">https://github.com/illwieckz/dpm-query/</a> Just install the service (it will load "low/battery" DPM profile at startup), then use the `dpm-query` tool to set "high/performance" DPM profile when you need it.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>