From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 91880] Radeonsi on Grenada cards (r9 390) exceptionally unstable and poorly performing Date: Fri, 15 Jan 2016 01:47:07 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1361353031==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 692F16EAC9 for ; Thu, 14 Jan 2016 17:47:07 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1361353031== Content-Type: multipart/alternative; boundary="1452822427.f7334.31610"; charset="UTF-8" --1452822427.f7334.31610 Date: Fri, 15 Jan 2016 01:47:07 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=91880 --- Comment #55 from Thomas DEBESSE --- 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: https://github.com/illwieckz/dpm-query/ 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. -- You are receiving this mail because: You are the assignee for the bug. --1452822427.f7334.31610 Date: Fri, 15 Jan 2016 01:47:07 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 55 on bug 91880 from 
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:
https://github.com/illwieckz/dpm-query/

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.

You are receiving this mail because:
  • You are the assignee for the bug.
--1452822427.f7334.31610-- --===============1361353031== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1361353031==--