From: Shaoyun Liu <[email protected]>

job could be NULL when amdgpu_device_gpu_recover is called

Signed-off-by: Shaoyun Liu <[email protected]>
Reviewed-by: Andrey Grodzovsky <[email protected]>
Signed-off-by: Felix Kuehling <[email protected]>
---
 drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c 
b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
index 470cc25..e463f36 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
@@ -3215,7 +3215,7 @@ int amdgpu_device_gpu_recover(struct amdgpu_device *adev,
                if (job && job->ring->idx != i)
                        continue;
 
-               drm_sched_hw_job_reset(&ring->sched, &job->base);
+               drm_sched_hw_job_reset(&ring->sched, job ? &job->base : NULL);
 
                /* after all hw jobs are reset, hw fence is meaningless, so 
force_completion */
                amdgpu_fence_driver_force_completion(ring);
-- 
2.7.4

_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

Reply via email to