dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104932] Hang when running X11/Wayland on GFX8/Polaris10/Ellesmere/Rx-480-8GiB (agd5f a5592a6df4f45a018b48f252ad1c498e683e9b9d, hwentland's DC-Patches-Jan-31-2018.mbox applied)
Date: Sat, 03 Feb 2018 20:25:19 +0000	[thread overview]
Message-ID: <bug-104932-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 104932
           Summary: Hang when running X11/Wayland on
                    GFX8/Polaris10/Ellesmere/Rx-480-8GiB (agd5f
                    a5592a6df4f45a018b48f252ad1c498e683e9b9d, hwentland's
                    DC-Patches-Jan-31-2018.mbox applied)
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: robink@creosotehill.org

Created attachment 137158
  --> https://bugs.freedesktop.org/attachment.cgi?id=137158&action=edit
Kernel serial log while firing up the Awesome WM

Hello-
    I've been having (for a while now, and going back a bit in terms of AMDGPU
tree commit history) an issue whereby the framebuffer & graphics stack
(*usually* not the kernel writ large) will hang upon firing up XOrg's XServer
or a Wayland compositor (in my case, GNOME-Shell).
    What compounded my frustration was that I'd rarely (if ever) see any output
from the Xorg server, the Wayland compositor, or the kernel indicating there
was any sort of problem, save for a trapped SIGQUIT (trap3) hitting
gnome-shell.
    Finally, in firing up X11 directly w/ Awesome as the WM I obtained some
kernel output which will hopefully prove useful in diagnosing this issue.  It's
below (and attached):
amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00500002
amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A088002
amdgpu 0000:01:00.0: VM fault (0x02, vmid 5, pasid 32768) at page 5242882, read
from 'TC6' (0x54433600) (136)
[drm:amdgpu_job_timedout] *ERROR* ring gfx timeout, last signaled seq=45, last
emitted seq=48
[drm] IP block:gfx_v8_0 is hung!
[drm] GPU recovery disabled.

Doubt it's tremendously useful, but kernel output with gnome-shell (in this
case acting as a Wayland compositor) is below and attached as well:
traps: gnome-shell[1260] trap int3 ip:7f6e4b956e01 sp:7ffe72a8aa50 error:0 in
libglib-2.0.so.0.5200.3[7f6e4b908000+10f000]
traps: gnome-shell[1336] trap int3 ip:7f0f89b3ee01 sp:7ffefd8d3df0 error:0 in
libglib-2.0.so.0.5200.3[7f0f89af0000+10f000]
traps: gnome-shell[1351] trap int3 ip:7f0984cb6e01 sp:7ffd3caa7650 error:0 in
libglib-2.0.so.0.5200.3[7f0984c68000+10f000]

Lastly, my Xorg.0.log is attached, but you'll find it's quite boring (no
complaints, which is good, but seemingly no useful debugging information,
either).

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

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

             reply	other threads:[~2018-02-03 20:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-03 20:25 bugzilla-daemon [this message]
2018-02-03 20:26 ` [Bug 104932] Hang when running X11/Wayland on GFX8/Polaris10/Ellesmere/Rx-480-8GiB (agd5f a5592a6df4f45a018b48f252ad1c498e683e9b9d, hwentland's DC-Patches-Jan-31-2018.mbox applied) bugzilla-daemon
2018-02-03 20:27 ` bugzilla-daemon
2018-02-03 20:47 ` bugzilla-daemon
2018-02-05  9:06 ` bugzilla-daemon
2018-02-07 17:51 ` bugzilla-daemon
2018-02-10 19:33 ` bugzilla-daemon
2018-02-11 22:54 ` bugzilla-daemon
2018-03-07 17:57 ` 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-104932-502@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