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: Tue, 19 Jul 2016 21:39:53 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0487388538=="
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 4476E6E079
for ; Tue, 19 Jul 2016 21:39:53 +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
--===============0487388538==
Content-Type: multipart/alternative; boundary="14689643932.1ddEFf0.19363";
charset="UTF-8"
--14689643932.1ddEFf0.19363
Date: Tue, 19 Jul 2016 21:39:53 +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 #110 from Chris Waters ---
(In reply to John Bridgman from comment #108)
> Chris, are you using the -k firmware files and associated kernel patches,
> updated initrd if needed, etc... ?
I have not for two reasons.
1. As Christoffer mentions, the _k firmware only seems good for the 390X
2. I'm unfamiliar with the process of doing such and the steps for doing it=
are
spread across 100+ comments with no real sign of what steps are the right o=
nes.
> My impression is that a few different issues are being discussed in this =
one
> ticket, and that is hampering progress. Not quite sure what the right spl=
it
> would be (if we were to close this and replace with N more focused ticket=
s)
> but probably one of them should be for stability problems when running the
> -k firmware and checking whether locking dpm level to performance makes a
> difference.
Still, these issues make using an 390 or 390X on Linux a nightmare. This is=
sue
isn't "minor" and its importance rating should reflect that. This is a major
(or even critical) bug report, IMO.
One that has been open for 10 months, I might add.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--14689643932.1ddEFf0.19363
Date: Tue, 19 Jul 2016 21:39:53 +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 # 110
on bug 91880<=
/a>
from Chris Waters
(In reply to John Bridgman from comment #108)
> Chris, are you using the -k firmware files and a=
ssociated kernel patches,
> updated initrd if needed, etc... ?
I have not for two reasons.
1. As Christoffer mentions, the _k firmware only seems good for the 390X
2. I'm unfamiliar with the process of doing such and the steps for doing it=
are
spread across 100+ comments with no real sign of what steps are the right o=
nes.
> My impression is that a few different issues are=
being discussed in this one
> ticket, and that is hampering progress. Not quite sure what the right =
split
> would be (if we were to close this and replace with N more focused tic=
kets)
> but probably one of them should be for stability problems when running=
the
> -k firmware and checking whether locking dpm level to performance make=
s a
> difference.
Still, these issues make using an 390 or 390X on Linux a nightmare. This is=
sue
isn't "minor" and its importance rating should reflect that. This=
is a major
(or even critical) bug report, IMO.
One that has been open for 10 months, I might add.
You are receiving this mail because:
- You are the assignee for the bug.
=
--14689643932.1ddEFf0.19363--
--===============0487388538==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============0487388538==--