diff options
| author | Rob Clark <robdclark@chromium.org> | 2021-03-17 09:40:38 -0700 |
|---|---|---|
| committer | Rob Clark <robdclark@chromium.org> | 2021-03-17 14:19:19 -0700 |
| commit | 7ad48d27a2846bfda29214fb454d001c3e02b9e7 (patch) | |
| tree | 1c2864321a579c2c0c97018d68d133db8a781fd0 | |
| parent | 4a9d36b0610aa7034340e976652e5b43320dd7c5 (diff) | |
| download | linux-7ad48d27a2846bfda29214fb454d001c3e02b9e7.tar.bz2 | |
drm/msm: Ratelimit invalid-fence message
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>
| -rw-r--r-- | drivers/gpu/drm/msm/msm_fence.c | 2 |
1 files changed, 1 insertions, 1 deletions
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; } |