All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97428] Specific OpenGL applications deadlock on AMD GPU drivers
Date: Sun, 21 Aug 2016 08:33:47 +0000	[thread overview]
Message-ID: <bug-97428-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 97428
           Summary: Specific OpenGL applications deadlock on AMD GPU
                    drivers
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: tmp6154@yandex.ru

I've been experiencing problems with open-source AMD GPU driver and specific
OpenGL applications. Particularly, Tabletop Simulator and Left 4 Dead 2 exhibit
this behavior. After a few minutes since game launches, it (apparently
randomly) deadlocks, screen stops to refresh. If game is minimized and
maximized again, it will show black screen. From this state, it could only be
closed with SIGINT in terminal or SIGKILL. Left 4 Dead 2 has similar issue, but
unlike Tabletop Simulator, it doesn't seem to deadlock in main menu.

My configuration:

Gentoo Linux
Dual AMD Radeon RX 480 (Polaris 10).
4.7.0 kernel with AMD GPU built as module (PowerPlay component enabled).
mesa git (9999).
xf86-video-amdgpu git (9999).
XOrg 1.17.4

Direct Rendering works, GPU is detected according to glxinfo:

direct rendering: Yes

OpenGL renderer string: Gallium 0.4 on AMD POLARIS10 (DRM 3.2.0 / 4.7.1-gentoo,
LLVM 3.7.1)

XOrg log shows GPUs are initialized:

[    30.903] (II) AMDGPU(G0): [DRI2] Setup complete 
[    30.903] (II) AMDGPU(G0): [DRI2]   DRI driver: radeonsi 
[    30.903] (II) AMDGPU(G0): [DRI2]   VDPAU driver: radeonsi 
[    30.905] (**) AMDGPU(G0): DRI3 enabled 
[    30.963] (II) AMDGPU(0): [DRI2] Setup complete 
[    30.963] (II) AMDGPU(0): [DRI2]   DRI driver: radeonsi 
[    30.963] (II) AMDGPU(0): [DRI2]   VDPAU driver: radeonsi 
[    30.964] (**) AMDGPU(0): DRI3 enabled 
[    31.036] (II) GLX: Initialized DRI2 GL provider for screen 0

DRI3 is enabled (though GLX uses DRI2 for some reason).

Here's my device configuration:

Section "Device" 
    Identifier  "AMD Radeon RX 480 (POLARIS10)" 
    Driver      "amdgpu" 
    BusID       "PCI:1:0:0" 
    Option      "DRI"         "3" 
    Option      "AccelMethod" "glamor" 
EndSection

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

[-- Attachment #1.2: Type: text/html, Size: 3749 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:[~2016-08-21  8:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-21  8:33 bugzilla-daemon [this message]
2016-08-21  8:50 ` [Bug 97428] Specific OpenGL applications deadlock on AMD GPU drivers bugzilla-daemon
2016-08-22  2:21 ` bugzilla-daemon
2016-08-23  7:23 ` 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-97428-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 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.