From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100712] ring 0 stalled after bytes_moved_threshold reached - Cap Verde - HD 7770
Date: Wed, 19 Apr 2017 03:48:45 +0000 [thread overview]
Message-ID: <bug-100712-502-lkSBSBBUFH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100712-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1736 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100712
--- Comment #4 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Julien Isorce from comment #0)
> In kernel radeon_object.c::radeon_bo_list_validate, once "bytes_moved >
> bytes_moved_threshold" is reached (this is the case for 850 bo in the same
> list_for_each_entry loop), I can see that radeon_ib_schedule emits a fence
> that it takes more than the radeon.lockup_timeout to be signaled.
radeon_ib_schedule is called for submitting the command stream from userspace,
not for any BO moves directly, right?
How did you determine that this hang is directly related to bytes_moved /
bytes_moved_threshold? Maybe it's only indirectly related, e.g. due to the
threshold preventing a BO from being moved to VRAM despite userspace's
preference.
> Also it seems the fence is signaled by swapper after more than 10 seconds
> but it is too late. I requires to reduce the "15" param above to 4 to see
> that.
How does "swapper" (what is that exactly?) signal the fence?
> Is it normal that radeon_bo_list_validate still tries to move the bo if
> bytes_moved_threshold is reached ?
There are circumstances where a BO has to be moved even though the threshold is
reached.
> Indeed ttm_bo_validate is always called
ttm_bo_validate must be called for every BO referenced by the command stream
from userspace for correct lifetime management of its memory.
> (it blits from vram to vram).
It might be worth looking into why this happens, though. If domain ==
current_domain == RADEON_GEM_DOMAIN_VRAM, I wouldn't expect ttm_bo_validate to
trigger a blit.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2812 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-19 3:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 15:14 [Bug 100712] ring 0 stalled after bytes_moved_threshold reached - Cap Verde - HD 7770 bugzilla-daemon
2017-04-18 15:15 ` bugzilla-daemon
2017-04-18 15:15 ` bugzilla-daemon
2017-04-18 15:16 ` bugzilla-daemon
2017-04-19 3:48 ` bugzilla-daemon [this message]
2017-04-19 12:03 ` bugzilla-daemon
2017-04-20 15:15 ` bugzilla-daemon
2017-04-20 15:15 ` [Bug 100712] ring 0 stalled after bytes_moved_threshold reached - CAPVERDE/HD7770 - TAHITI/W9000 bugzilla-daemon
2017-04-20 15:23 ` bugzilla-daemon
2017-04-24 11:02 ` bugzilla-daemon
2019-11-19 9:28 ` 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-100712-502-lkSBSBBUFH@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox