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: Thu, 22 Nov 2018 04:44:54 +0000	[thread overview]
Message-ID: <bug-105113-502-bMwXLeosqS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105113-502@http.bugs.freedesktop.org/>


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

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

--- Comment #9 from Jan Vesely <jan.vesely@rutgers.edu> ---
(In reply to Maciej S. Szmigiero from comment #8)
> Aren't program@execute@calls-struct and program@execute@tail-calls tests
> from comment 4 examples of this behavior?
> These seem to run but return wrong results, or am I not parsing the piglit
> test results correctly?

This is more of a piglit problem. piglit uses a combination of enqueue and
clFinish. However, the error happens on kernel launch. thus;
1.) clEnqueueNDRangeKernel -- success
2.) The driver tries to launch the kernel and fails on relocations
3.) application(piglit) calls clFinish

depending on the order of 2. and 3. clFinish can either see an empty queue and
succeed or try to wait for kernel execution and fail.

The following series should address that:
https://patchwork.freedesktop.org/series/52857/

> This would explain why "amdgpu" seemed to not even attempt to reset the GPU
> after a crash.
> 
> However, I think I've got at least one lockup when testing this issue half a
> year ago on "radeon" driver ("amdgpu" is still marked as experimental for SI
> parts).
> If I am able to reproduce it in the future I will report it then.

comment #1 shows an example of a successful restart using radeon.ko, so I guess
it worked for at least some ASICs. at any rate, restarting GPU is a separate,
kernel, problem.
Feel free to remove the relocation guard if you want to investigate GPU reset.

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

[-- Attachment #1.2: Type: text/html, Size: 2889 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-22  4:44 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
2018-11-19 14:03 ` bugzilla-daemon
2018-11-22  4:44 ` bugzilla-daemon [this message]
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-bMwXLeosqS@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).