From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105113] [hawaii, radeonsi, clover] Running Piglit cl/program/execute/{, tail-}calls{, -struct, -workitem-id}.cl cause GPU VM error and ring stalled GPU lockup
Date: Thu, 15 Nov 2018 22:24:07 +0000 [thread overview]
Message-ID: <bug-105113-502-jHgVMecCvg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105113-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1036 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105113
Jan Vesely <jan.vesely@rutgers.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also|https://bugs.freedesktop.or |
|g/show_bug.cgi?id=102909, |
|https://bugs.freedesktop.or |
|g/show_bug.cgi?id=104307, |
|https://bugs.freedesktop.or |
|g/show_bug.cgi?id=101712, |
|https://bugs.freedesktop.or |
|g/show_bug.cgi?id=107545 |
--- Comment #5 from Jan Vesely <jan.vesely@rutgers.edu> ---
This behaviour is expected.
until mesa properly supports code relocations (or llvm stops using relocations
for internal symbols) it will refuse to run kernels that need relocating.
Jumping to invalid address causes both pagefault and a gpu hang.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2516 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-11-15 22:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 14:58 [Bug 105113] [hawaii] Running Piglit cl/program/execute/calls-struct.cl causes GPU VM error and ring stalled GPU lockup bugzilla-daemon
2018-02-15 15:58 ` bugzilla-daemon
2018-02-15 16:09 ` [Bug 105113] [hawaii, radeonsi, clover] Running Piglit cl/program/execute/{, tail-}calls{, -struct, -workitem-id}.cl cause " bugzilla-daemon
2018-04-29 22:23 ` bugzilla-daemon
2018-06-30 13:06 ` bugzilla-daemon
2018-10-27 17:42 ` bugzilla-daemon
2018-10-27 19:02 ` bugzilla-daemon
2018-11-14 9:58 ` bugzilla-daemon
2018-11-14 10:00 ` bugzilla-daemon
2018-11-14 10:08 ` bugzilla-daemon
2018-11-14 10:08 ` bugzilla-daemon
2018-11-14 10:09 ` bugzilla-daemon
2018-11-15 22:24 ` bugzilla-daemon [this message]
2018-11-16 16:13 ` bugzilla-daemon
2018-11-18 19:24 ` bugzilla-daemon
2018-11-19 14:03 ` bugzilla-daemon
2018-11-22 4:44 ` bugzilla-daemon
2018-11-23 13:43 ` bugzilla-daemon
2018-12-04 17:40 ` bugzilla-daemon
2019-01-15 9:23 ` bugzilla-daemon
2019-06-13 18:45 ` 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-105113-502-jHgVMecCvg@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).