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: Sat, 09 Sep 2017 11:29:04 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1825813352==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 43F8B6E2A3 for ; Sat, 9 Sep 2017 11:29:05 +0000 (UTC) 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 --===============1825813352== Content-Type: multipart/alternative; boundary="15049565453.667B30a.21634"; charset="UTF-8" --15049565453.667B30a.21634 Date: Sat, 9 Sep 2017 11:29:05 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D91880 --- Comment #159 from Jon Doane --- Is there going to be any work on this? I've literally been doing: "echo high > /sys/class/device/drm/card0/power_dpm_force_performance_level" every day to boot my machine for over a year hoping that this might get fix= ed but, I've seen practically no progress made on this bug. After attempting to use kernel 4.13, it becomes unstable and crashes faster than I can duck out into a TTY so, it's almost like the problem is getting worse as time goes o= n. This is literally a crippling bug and I find it astonishing that something, like locking VRAM clocks and making 500Mhz the minimum core clock for all 3= 90s hasn't been implemented as a stopgap measure to at least get the thing stab= le. For crying out loud, this bug has been open for 2 years now and has been reproduced by several different people, or do we have to wait another 2 yea= rs before we're told that it won't be fixed? --=20 You are receiving this mail because: You are the assignee for the bug.= --15049565453.667B30a.21634 Date: Sat, 9 Sep 2017 11:29:05 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 159 on bug 91880<= /a> from <= span class=3D"fn">Jon Doane 
Is there going to be any work on this? I've literally been doi=
ng:
"echo  high > /sys/class/device/drm/card0/power_dpm_force_performan=
ce_level"
every day to boot my machine for over a year hoping that this might get fix=
ed
but, I've seen practically no progress made on this bug. After attempting to
use kernel 4.13, it becomes unstable and crashes faster than I can duck out
into a TTY so, it's almost like the problem is getting worse as time goes o=
n.
This is literally a crippling bug and I find it astonishing that something,
like locking VRAM clocks and making 500Mhz the minimum core clock for all 3=
90s
hasn't been implemented as a stopgap measure to at least get the thing stab=
le.
For crying out loud, this bug has been open for 2 years now and has been
reproduced by several different people, or do we have to wait another 2 yea=
rs
before we're told that it won't be fixed?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15049565453.667B30a.21634-- --===============1825813352== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1825813352==--