On 17.12.2012 17:04, j.glisse at gmail.com wrote:
> From: Jerome Glisse
>
> radeon_fence_wait_empty_locked should not trigger GPU reset as no
> place where it's call from would benefit from such thing and it
> actually lead to a kernel deadlock in case the reset is triggered
> from pm codepath. In
Added to fixes and stable. Thanks!
On Mon, Dec 17, 2012 at 11:41 AM, Christian K?nig
wrote:
> On 17.12.2012 17:04, j.glisse at gmail.com wrote:
>>
>> From: Jerome Glisse
>>
>> radeon_fence_wait_empty_locked should not trigger GPU reset as no
>> place where it's call from would benefit from such
Added to fixes and stable. Thanks!
On Mon, Dec 17, 2012 at 11:41 AM, Christian König
wrote:
> On 17.12.2012 17:04, j.gli...@gmail.com wrote:
>>
>> From: Jerome Glisse
>>
>> radeon_fence_wait_empty_locked should not trigger GPU reset as no
>> place where it's call from would benefit from such th
From: Jerome Glisse
radeon_fence_wait_empty_locked should not trigger GPU reset as no
place where it's call from would benefit from such thing and it
actually lead to a kernel deadlock in case the reset is triggered
from pm codepath. Instead force ring completion in place where it
makes sense or
On 17.12.2012 17:04, j.gli...@gmail.com wrote:
From: Jerome Glisse
radeon_fence_wait_empty_locked should not trigger GPU reset as no
place where it's call from would benefit from such thing and it
actually lead to a kernel deadlock in case the reset is triggered
from pm codepath. Instead force
From: Jerome Glisse
radeon_fence_wait_empty_locked should not trigger GPU reset as no
place where it's call from would benefit from such thing and it
actually lead to a kernel deadlock in case the reset is triggered
from pm codepath. Instead force ring completion in place where it
makes sense or