Re: [PATCH] drm/amdgpu: dma_fence finished signaled by unexpected callback

2018-12-27 Thread Grodzovsky, Andrey
, 2018 12:57 AM > To: Lou, Wentao ; amd-gfx@lists.freedesktop.org > Subject: Re: [PATCH] drm/amdgpu: dma_fence finished signaled by unexpected > callback > > I believe this issue would be resolved by my pending  in review patch set, > specifically 'drm/sched: Refactor

RE: [PATCH] drm/amdgpu: dma_fence finished signaled by unexpected callback

2018-12-25 Thread Lou, Wentao
for these patches? Thanks. BR, Wentao -Original Message- From: Grodzovsky, Andrey Sent: Saturday, December 22, 2018 12:57 AM To: Lou, Wentao ; amd-gfx@lists.freedesktop.org Subject: Re: [PATCH] drm/amdgpu: dma_fence finished signaled by unexpected callback I believe this issue would

Re: [PATCH] drm/amdgpu: dma_fence finished signaled by unexpected callback

2018-12-21 Thread Grodzovsky, Andrey
I believe this issue would be resolved by my pending  in review patch set, specifically 'drm/sched: Refactor ring mirror list handling.' since already on the first TO handler it will go over all the rings including the second timed out ring and will remove all call backs including the bad job c

[PATCH] drm/amdgpu: dma_fence finished signaled by unexpected callback

2018-12-21 Thread wentalou
When 2 rings met timeout at same time, triggered job_timedout separately. Each job_timedout called gpu_recover, but one of gpu_recover locked by another's mutex_lock. Bad jod’s callback should be removed by dma_fence_remove_callback but locked inside mutex_lock. So dma_fence_remove_callback could