lkml.org 
[lkml]   [2021]   [Apr]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 5.11 16/45] drm/msm: Ratelimit invalid-fence message
    Date
    From: Rob Clark <robdclark@chromium.org>

    [ Upstream commit 7ad48d27a2846bfda29214fb454d001c3e02b9e7 ]

    We have seen a couple cases where low memory situations cause something
    bad to happen, followed by a flood of these messages obscuring the root
    cause. Lets ratelimit the dmesg spam so that next time it happens we
    don't lose the kernel traces leading up to this.

    Signed-off-by: Rob Clark <robdclark@chromium.org>
    Reviewed-by: Douglas Anderson <dianders@chromium.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>
    ---
    drivers/gpu/drm/msm/msm_fence.c | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    diff --git a/drivers/gpu/drm/msm/msm_fence.c b/drivers/gpu/drm/msm/msm_fence.c
    index ad2703698b05..cd59a5918038 100644
    --- a/drivers/gpu/drm/msm/msm_fence.c
    +++ b/drivers/gpu/drm/msm/msm_fence.c
    @@ -45,7 +45,7 @@ int msm_wait_fence(struct msm_fence_context *fctx, uint32_t fence,
    int ret;

    if (fence > fctx->last_fence) {
    - DRM_ERROR("%s: waiting on invalid fence: %u (of %u)\n",
    + DRM_ERROR_RATELIMITED("%s: waiting on invalid fence: %u (of %u)\n",
    fctx->name, fence, fctx->last_fence);
    return -EINVAL;
    }
    --
    2.30.2


    \
     
     \ /
      Last update: 2021-04-09 12:40    [W:2.627 / U:0.016 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site