Comment 36 for bug 1314787

I see where you are coming from, but no, I do not think it is a
regression because a) it existed with the prior AMD driver set, and b)
it goes away with the 3.14.x kernel & Trusty shipped with the 3.13.x
branch. Technically, I guess it could be some sort of regression though
because it comes back with later kernel branches.

What I think is that AMD sucks at Linux driver sets :) I.e., still
using Loki; still using 32bit libraries etc. etc.. The reason I believe
it is kernel related is to not blame Linux, but AMD's long history of
poor kernel integration. Do a google of that and you will see what I
mean.

As it stands, the latest driver only supports versions of the 3.16.x
Kernel branch. When it was released I believe the 3.18.x branch was
well established... Maybe 3.19.

I know that as a Linux user who will never go back to Windows, that I
will also never buy another AMD GPU ... at least while they continue
with their half-hearted driver development for Linux.

Gordon VS
<email address hidden>

On 15-04-23 01:03 AM, Mediaklan wrote:
> Well, I'm willing to try because I spoke too soon : leak is back for me
> after a few days if i let 1 or 2 programs running. It's still slower
> than before to fill my ram, but still here.
>
>> 2) Installing kernels from the 3.13 or 3.16 (I have not bothered with
>> 3.15 branches) branches result in the issue instantly back.
>
> So you think it's a regression ? Didn't expect that.
>