lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 6 Jun 2018 13:33:52 +0200
From:   Christian König <christian.koenig@....com>
To:     Gabriel C <nix.or.die@...il.com>
Cc:     Jean-Marc Valin <jmvalin@...illa.com>,
        Dave Airlie <airlied@...ux.ie>, alexander.deucher@....com,
        Felix Kuehling <Felix.Kuehling@....com>,
        Laura Abbott <labbott@...hat.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        michel.daenzer@....com, dri-devel@...ts.freedesktop.org,
        LKML <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: AMD graphics performance regression in 4.15 and later

Am 06.06.2018 um 13:28 schrieb Gabriel C:
> 2018-04-11 7:02 GMT+02:00 Gabriel C <nix.or.die@...il.com>:
>>> 2018-04-11 6:00 GMT+02:00 Gabriel C <nix.or.die@...il.com>:
>>> 2018-04-09 11:42 GMT+02:00 Christian König <ckoenig.leichtzumerken@...il.com>:
>>>> Am 07.04.2018 um 00:00 schrieb Jean-Marc Valin:
>> ...
>>> I can help testing code for 4.17/++ if you wish but that is *different* storry.
>>>
>> Quick tested an 4.16.0-11490-gb284d4d5a678 , amdgpu and radeon driver
>> are broken now in this one.
>>
>> radeon tells:
>>
>> ...
>>
>> [    6.337838] [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
>> [    6.338210] radeon 0000:21:00.0: (-12) create WB bo failed
>> [    6.338214] radeon 0000:21:00.0: disabling GPU acceleration
>>
>> ...
>>
> I have the same Issue now on final 4.17.

Actually Michel came up with a fix for the performance regression which 
is now backported to older kernels as well.

So the original issue of this mail thread should be fixed by now.

> Also I played with BIOS options also which does not fix anything but
> changes the error message.
>
> IOMMU && SR-IOV disabled the error changes to this :
>
> [    7.092044] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0
> test failed (scratch(0x850C)=0xCAFEDEAD)
> [    7.092059] radeon 0000:21:00.0: disabling GPU acceleration
>
>
> While I could workaround SWIOTLB bugs in 4.15 and 4.16 , 4.17 seems to
> kill the GPU with no way
> for me to make it work ( at least I could not find any workaround by now )

That actually sounds like something completely different. Can you 
provide a full dmesg of radeon and/or amdgpu?

Thanks,
Christian.

>
> BR

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ