mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ilkka Prusi <ilkka.prusi@pp.inet.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: WARNING: AMDGPU DRM warning in 5.11.9
Date: Thu, 25 Mar 2021 07:57:33 +0200	[thread overview]
Message-ID: <a38a3c04-4ac8-01a6-da69-a2bdaa54f61d@pp.inet.fi> (raw)
In-Reply-To: <CAK2bqVJ+=nHTK-hnUC=qL1mcOvHWTCwDMYPBKJp77QCbBvBGGw@mail.gmail.com>

On 24.3.2021 16.16, Chris Rankin wrote:
> Hi,
> 
> Theee warnings ares not present in my dmesg log from 5.11.8:
> 
> [   43.390159] ------------[ cut here ]------------
> [   43.393574] WARNING: CPU: 2 PID: 1268 at
> drivers/gpu/drm/ttm/ttm_bo.c:517 ttm_bo_release+0x172/0x282 [ttm]
> [   43.401940] Modules linked in: nf_nat_ftp nf_conntrack_ftp cfg80211

Changing WARN_ON to WARN_ON_ONCE in drivers/gpu/drm/ttm/ttm_bo.c 
ttm_bo_release() reduces the flood of messages into single splat.

This warning appears to come from 57fcd550eb15bce ("drm/ttm: Warn on 
pinning without holding a reference)" and reverting it might be one choice.


> 
> There are others, but I am assuming there is a common cause here.
> 
> Cheers,
> Chris
> 

diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
index a76eb2c14e8c..50b53355b265 100644
--- a/drivers/gpu/drm/ttm/ttm_bo.c
+++ b/drivers/gpu/drm/ttm/ttm_bo.c
@@ -514,7 +514,7 @@ static void ttm_bo_release(struct kref *kref)
                  * shrinkers, now that they are queued for
                  * destruction.
                  */
-               if (WARN_ON(bo->pin_count)) {
+               if (WARN_ON_ONCE(bo->pin_count)) {
                         bo->pin_count = 0;
                         ttm_bo_del_from_lru(bo);
                         ttm_bo_add_mem_to_lru(bo, &bo->mem);



--
  - Ilkka


  reply	other threads:[~2021-03-25  6:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24 14:16 Chris Rankin
2021-03-25  5:57 ` Ilkka Prusi [this message]
2021-03-25  8:17   ` Oleksandr Natalenko
2021-03-25  8:29     ` Christian König

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a38a3c04-4ac8-01a6-da69-a2bdaa54f61d@pp.inet.fi \
    --to=ilkka.prusi@pp.inet.fi \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®