From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107545] radeon - ring 0 stalled - GPU lockup - SI
Date: Fri, 24 Aug 2018 23:34:53 +0000 [thread overview]
Message-ID: <bug-107545-502-PRrXxrA6SL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107545-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1026 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107545
--- Comment #11 from Julien Isorce <julien.isorce@gmail.com> ---
I found time to go a bit further. Now I understand this radeon_cs_parser_init
function a bit more
If I comment the AGP condition here
https://cgit.freedesktop.org/~agd5f/linux/tree/drivers/gpu/drm/radeon/radeon_cs.c?h=amd-staging-drm-next#n340
so that kdata is used then I can verify that the kdata contains the same data
as user space.
But when writing to parser->ib.ptr here
https://cgit.freedesktop.org/~agd5f/linux/tree/drivers/gpu/drm/radeon/radeon_cs.c?h=amd-staging-drm-next#n648
then comparing parser->ib.ptr's data and kdata shows the same difference as
pointed in comment #5.
Could it be an issue with pcie (though is works with admgpu, well in fact it
uses kdata on amdgpu) ? Is there anyway I can force a commit/flush just after
it writes to parser->ib.ptr as a test even if it is slower ? thx!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2096 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:[~2018-08-24 23:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 22:59 [Bug 107545] radeon - ring 0 stalled - GPU lockup - SI bugzilla-daemon
2018-08-14 16:52 ` bugzilla-daemon
2018-08-20 17:24 ` bugzilla-daemon
2018-08-20 17:26 ` bugzilla-daemon
2018-08-20 17:27 ` bugzilla-daemon
2018-08-20 17:42 ` bugzilla-daemon
2018-08-23 23:03 ` bugzilla-daemon
2018-08-23 23:04 ` bugzilla-daemon
2018-08-23 23:06 ` bugzilla-daemon
2018-08-24 7:30 ` bugzilla-daemon
2018-08-24 9:06 ` bugzilla-daemon
2018-08-24 23:34 ` bugzilla-daemon [this message]
2018-08-27 10:38 ` bugzilla-daemon
2018-11-14 9:57 ` bugzilla-daemon
2018-11-14 9:59 ` bugzilla-daemon
2018-11-14 10:02 ` bugzilla-daemon
2018-11-14 10:07 ` bugzilla-daemon
2018-11-14 10:07 ` bugzilla-daemon
2018-11-14 10:09 ` bugzilla-daemon
2018-11-15 22:24 ` bugzilla-daemon
2019-11-19 9:34 ` 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-107545-502-PRrXxrA6SL@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;
as well as URLs for NNTP newsgroup(s).