On Mon, Oct 24, 2016 at 6:35 AM, Qu, Jim wrote:
> I did observed the issue when replace kernel module use DKMS, and it maybe
> get error at reboot, got calltrace:
>
> [ 3529.525360]
> =
> [ 3529.525361] BUG amd_sched_fen
On Sun, Oct 23, 2016 at 2:31 PM, Grazvydas Ignotas wrote:
> To free fences, call_rcu() is used, which calls amdgpu_fence_free()
> after a grace period. During teardown, there is no guarantee all
> callbacks have finished, so amdgpu_fence_slab may be destroyed before
> all fences have been freed. I
Interesting catch, patch is Reviewed-by: Christian König
.
Am 24.10.2016 um 04:34 schrieb zhoucm1:
> Acked-by: Chunming Zhou
>
> On 2016å¹´10æ24æ¥ 02:31, Grazvydas Ignotas wrote:
>> To free fences, call_rcu() is used, which calls amdgpu_fence_free()
>> after a grace period. During teardown,
Acked-by: Chunming Zhou
On 2016å¹´10æ24æ¥ 02:31, Grazvydas Ignotas wrote:
> To free fences, call_rcu() is used, which calls amdgpu_fence_free()
> after a grace period. During teardown, there is no guarantee all
> callbacks have finished, so amdgpu_fence_slab may be destroyed before
> all fence
å件人: amd-gfx 代表 zhoucm1
åéæ¶é´: 2016å¹´10æ24æ¥ 10:34
æ¶ä»¶äºº: Grazvydas Ignotas; dri-devel at lists.freedesktop.org; amd-gfx at
lists.freedesktop.org
主é¢: Re: [PATCH] drm/amdgpu: fix fence slab teardown
Acked-by: Chunming Zhou
On 2016å¹´10æ
To free fences, call_rcu() is used, which calls amdgpu_fence_free()
after a grace period. During teardown, there is no guarantee all
callbacks have finished, so amdgpu_fence_slab may be destroyed before
all fences have been freed. If we are lucky, this results in some slab
warnings, if not, we get
