dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
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: Sun, 18 Nov 2018 19:24:54 +0000	[thread overview]
Message-ID: <bug-105113-502-h4RipjsiK3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105113-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1598 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=105113

--- Comment #7 from Jan Vesely <jan.vesely@rutgers.edu> ---
(In reply to Maciej S. Szmigiero from comment #6)
> There are really two issues at play here:
> 1) If the LLVM-generated code cannot be run properly then it should be simply
> rejected by whatever is actually in charge of submitting it to the GPU (I
> guess
> this would be Mesa?).
> This way an application will know it cannot use OpenCL for computation, at
> least
> not with this compute kernel.
> 
> Instead, it currently looks like many of these test run but give incorrect
> results, which is obviously rather bad.

Do you have an example of this? clover should return OUT_OF_RESOURCES error
when the compute state creation fails (like in the presence of code
relocations).
It does not change the content of the buffer, so it will return whatever was
stored in the buffer on creation.

> 2) Some (previous) Mesa + LLVM versions generate a command stream that
> crashes the GPU and, as far as I can remember, sometimes even lockup the
> whole machine.
> 
> It should not be possible to crash the GPU, regardless how incorrect a
> command stream that userspace sends to it is - because otherwise it is
> possible for
> an unprivileged user with GPU access to DoS the machine.

This is a separate issue. GPU hangs are generally addressed via gpu reset which
should be enabled for gfx8/9 GPUs in recent amdgpu.ko [0]

[0] https://patchwork.freedesktop.org/patch/257994/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2793 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

  parent reply	other threads:[~2018-11-18 19: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
2018-11-16 16:13 ` bugzilla-daemon
2018-11-18 19:24 ` bugzilla-daemon [this message]
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-h4RipjsiK3@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).