<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Radeonsi on Grenada cards (r9 390) exceptionally unstable and poorly performing" href="https://bugs.freedesktop.org/show_bug.cgi?id=91880#c111">Comment # 111</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - 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:john.bridgman@amd.com" title="John Bridgman <john.bridgman@amd.com>"> John Bridgman</a> <pre>(In reply to Jan Ziak from <a href="show_bug.cgi?id=91880#c109">comment #109</a>) > My question would be: Why isn't the _k patch already in linux-git? > > I tested the patch on my R9 390, so the Hawaii-specific part of the patch > works on at least one machine in the world outside of freedesktop.org. > > Or is there a reason to delay patch submission to linux-git? > > _k firmware files are already available in Gentoo Linux for example. The patch is queued up for 4.8. It's the usual chicken-and-egg problem... if we can't get enough users testing a patch early in a kernel cycle then it ends up having to wait for the next merge window. (In reply to Chris Waters from <a href="show_bug.cgi?id=91880#c110">comment #110</a>) > (In reply to John Bridgman from <a href="show_bug.cgi?id=91880#c108">comment #108</a>) > > 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 I think that is part of the "few different issues" point. The -k microcode may not be the only change required but AFAIK it is one part of the solution. In other words if the patch and new ucode don't fix the problem that's still useful information, and it doesn't mean the new ucode isn't worth running. > > 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 ones. Yep, that's a fair point. I was just trying to make sure we were collecting good data. Thanks.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>