[PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling

Alex Deucher alexdeucher at gmail.com
Wed Dec 19 06:47:39 PST 2012


On Wed, Dec 19, 2012 at 9:41 AM, Paul Menzel
<paulepanter at users.sourceforge.net> wrote:
> Am Mittwoch, den 19.12.2012, 15:18 +0100 schrieb Maarten Lankhorst:
>> Fix regression introduced by 85b144f860176
>
> Thanks for the catch and patch.
>
> Also please add the commit summary to make the commit message self
> contained?
>
> The problem description would also be nice.
>
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com>
>> Reported-by: Markus Trippelsdorf <markus at trippelsdorf.de>
> Message-ID: <20121217182752.GA351 at x4>
>
>> ---
>>
>> diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
>> index 0bf66f9..9f85418 100644
>> --- a/drivers/gpu/drm/ttm/ttm_bo.c
>> +++ b/drivers/gpu/drm/ttm/ttm_bo.c
>> @@ -579,7 +579,7 @@ static int ttm_bo_cleanup_refs_and_unlock(struct ttm_buffer_object *bo,
>>                * at this point the buffer should be dead, so
>>                * no new sync objects can be attached.
>>                */
>> -             sync_obj = driver->sync_obj_ref(&bo->sync_obj);
>> +             sync_obj = driver->sync_obj_ref(bo->sync_obj);
>
> Any idea, why this only had an impact for one person so far?

There are several radeon bugs from drm-next 3.8 that may be ultimately
related to this.

Alex


More information about the dri-devel mailing list