OK, just apply the following to your amdgpu_dm_do_flip function and see if GPU reset does proceed after you experience the hang. diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c index d59bafc..586301f 100644 --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c @@ -4809,7 +4809,7 @@ static void amdgpu_dm_do_flip(struct drm_atomic_state *state, /* Wait for all fences on this FB */ WARN_ON(reservation_object_wait_timeout_rcu(abo->tbo.resv, true, false, - MAX_SCHEDULE_TIMEOUT) < 0); + msecs_to_jiffies(5000)) < 0); amdgpu_bo_get_tiling_flags(abo, &tiling_flags); Andrey On 2/13/19 8:59 AM, Mikhail Gavrilov wrote: > On Wed, 13 Feb 2019 at 00:44, Grodzovsky, Andrey > <Andrey.Grodzovsky@xxxxxxx> wrote: >> Sorry, for your kernel this particular set of prints should go in amdgpu_dm_do_flip >> > > Kernel logs became very weird after yesterday patch. > Too many messages even without reproducing the issue which cause > "ring gfx timeout". > > -- > Best Regards, > Mike Gavrilov. _______________________________________________ amd-gfx mailing list amd-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/amd-gfx
