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, 2 Jan 2013 18:59:23 -0500
From:	Alex Deucher <alexdeucher@...il.com>
To:	Shuah Khan <shuahkhan@...il.com>
Cc:	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	Jerome Glisse <j.glisse@...il.com>,
	Antti Palosaari <crope@....fi>, Borislav Petkov <bp@...en8.de>,
	Andy Furniss <andyqos@...sn.org>,
	Alex Deucher <alexander.deucher@....com>,
	dri-devel@...ts.freedesktop.org,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec

On Wed, Jan 2, 2013 at 6:58 PM, Shuah Khan <shuahkhan@...il.com> wrote:
> On Wed, Jan 2, 2013 at 4:37 PM, Alex Deucher <alexdeucher@...il.com> wrote:
>> On Wed, Jan 2, 2013 at 5:38 PM, Markus Trippelsdorf
>> <markus@...ppelsdorf.de> wrote:
>>> On 2013.01.02 at 17:31 -0500, Jerome Glisse wrote:
>>>> Please affected people can you test if patch :
>>>> http://people.freedesktop.org/~glisse/0003-drm-radeon-fix-dma-copy-on-r6xx-r7xx-evergen-ni-si-g.patch
>>>>
>>>> Fix the issue, you need to make sure you don't have the patch that
>>>> disable dma on r6xx ie that line 977-978 & 1061-1062  in radeon_asic.c
>>>> is :
>>>>  .copy = &r600_copy_dma,
>>>>  .copy_ring_index = R600_RING_TYPE_DMA_INDEX,
>>>
>>> It fixes the issue for me. Thanks.
>>
>> The count is actually the count, not count - 1.  The real fix seems to
>> be that r6xx requires 2 dw aligned transfers.  The attached patch
>> fixes the issue for me.
>>
>
> Catching up with this thread. I reverted the
>
> drm/radeon: use async dma for ttm buffer moves on 6xx-SI
> commit id: 2d6cc7296d4ee128ab0fa3b715f0afde511f49c2
>
> Do I need to apply this patch without reverting
> 2d6cc7296d4ee128ab0fa3b715f0afde511f49c2?

Correct.  Don't revert anything.  Just apply this patch.

Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ