From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108854] [polaris11] - Failed GPU reset after hang
Date: Mon, 14 Jan 2019 17:05:14 +0000 [thread overview]
Message-ID: <bug-108854-502-9gGGPefpm9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108854-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1177 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108854
--- Comment #8 from Tom Seewald <tseewald@gmail.com> ---
I've reproduced this issue on amd-staging-drm-next and have attached a UMR wave
and gfx ring dump, along with a new dmesg. To clarify, this issue also
prevents me from rebooting/shutting down my computer, and I am forced to hold
the power button.
Here are the version strings of the relevant software I'm running:
Kernel: amd-staging-drm-next (commit: d2d07f246b126b23d02af0603b83866a3c3e2483)
Mesa: 18.3.1
Xorg: 1.19.6
UMR: 016bc2e93af2cac7a9bd790f7fcacb1ffdadc819
This is my first attempt at using UMR to get information about this system
hang. I'm essentially just copying what Andrey Grodzovsky suggested in a
previous thread[0].
Here are the umr commands used to gather the information:
Waves dump: umr -i 1 -O verbose,halt_waves -wa
GFX ring dump: umr -i 1 -O verbose,follow -R gfx[.]
GFX info: umr -i 1 -e
I've attached the output of these to the bugzilla report.
[0] https://lists.freedesktop.org/archives/amd-gfx/2018-December/029790.html
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2029 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:[~2019-01-14 17:05 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 [this message]
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
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-9gGGPefpm9@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).