From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 213983] WARNING: CPU: 3 PID: 520 at drivers/gpu/drm/ttm/ttm_bo.c:409 ttm_bo_release+0x7a/0x803 [ttm]
Date: Wed, 27 Oct 2021 07:49:09 +0000 [thread overview]
Message-ID: <bug-213983-2300-XzZgxn4AfA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213983-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213983
Christian König (christian.koenig@amd.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |christian.koenig@amd.com
--- Comment #3 from Christian König (christian.koenig@amd.com) ---
Well what happens here is that a buffer object is released while it is pinned
and TTM now warns about doing stuff like that.
The key point is we need to figure out why the buffer is pinned in the first
place.
One possibility is that it is used for scanout and containing the displayed
picture, but from the backtrace my guess is that the buffer is shared with a
different device and pinned because of that.
Can we get an lspci output for the system?
Thanks in advance,
Christian.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-10-27 7:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 9:27 [Bug 213983] New: WARNING: CPU: 3 PID: 520 at drivers/gpu/drm/ttm/ttm_bo.c:409 ttm_bo_release+0x7a/0x803 [ttm] bugzilla-daemon
2021-08-06 9:28 ` [Bug 213983] " bugzilla-daemon
2021-10-20 15:15 ` bugzilla-daemon
2021-10-27 7:49 ` bugzilla-daemon [this message]
2021-10-27 13:43 ` bugzilla-daemon
2022-03-29 21:03 ` bugzilla-daemon
2022-03-29 21:15 ` bugzilla-daemon
2023-08-05 21:33 ` bugzilla-daemon
2023-09-13 12:58 ` bugzilla-daemon
2023-12-23 20:17 ` bugzilla-daemon
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=bug-213983-2300-XzZgxn4AfA@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.