All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108854] [polaris11] - GPU Hang - ring gfx timeout
Date: Thu, 21 Feb 2019 19:21:57 +0000	[thread overview]
Message-ID: <bug-108854-502-Dqbpk9YkyS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108854-502@http.bugs.freedesktop.org/>


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

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

--- Comment #14 from Tom Seewald <tseewald@gmail.com> ---
(In reply to Tom St Denis from comment #13)
> The wave dump seems to be empty... Is that the complete output?  Was there
> anything printed to stderr (like there are no waves)?

Yes it says "no active waves!" - so it makes sense that is empty.  Is there
something else you'd like me to try? 

Currently I'm running "umr -i 1 -O verbose,halt_waves -wa" immediately after I
see the "ring gfx timeout" in dmesg.  I also just rebuilt UMR so I should be up
to date.

Some potentially good news though, after upgrading from mesa 18.3.1 to 18.3.3,
I have not been able to reproduce the issue. On mesa 18.3.1 and earlier I can
reproduce it in under 20 seconds (I did so today on the latest
amd-staging-drm-next), and I have tested mesa 18.3.3 for about an hour now.

But I believe this is still something to look into as user space should
probably not be able to hang the entire system, even if the user is running an
older version of Mesa.

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

[-- Attachment #1.2: Type: text/html, Size: 2015 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-02-21 19:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-24 20:41 [Bug 108854] [polaris11] - Failed GPU reset after hang bugzilla-daemon
2018-12-01 18:17 ` bugzilla-daemon
2018-12-08 18:20 ` bugzilla-daemon
2018-12-08 18:27 ` bugzilla-daemon
2019-01-14 16:54 ` bugzilla-daemon
2019-01-14 16:55 ` bugzilla-daemon
2019-01-14 16:55 ` bugzilla-daemon
2019-01-14 16:57 ` bugzilla-daemon
2019-01-14 17:05 ` bugzilla-daemon
2019-01-14 17:42 ` bugzilla-daemon
2019-01-14 17:43 ` bugzilla-daemon
2019-01-23  0:20 ` [Bug 108854] [polaris11] - GPU Hang - ring gfx timeout bugzilla-daemon
2019-01-25 17:24 ` bugzilla-daemon
2019-01-25 17:26 ` bugzilla-daemon
2019-02-10  1:01 ` bugzilla-daemon
2019-02-21 17:56 ` bugzilla-daemon
2019-02-21 19:21 ` bugzilla-daemon [this message]
2019-02-22 17:03 ` bugzilla-daemon
2019-02-22 18:15 ` bugzilla-daemon
2019-02-22 18:31 ` bugzilla-daemon
2019-02-22 18:46 ` 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-108854-502-Dqbpk9YkyS@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.