All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 178281] wine-staging apps freezes the machine with RX460
Date: Fri, 28 Oct 2016 04:41:44 +0000	[thread overview]
Message-ID: <bug-178281-2300-81nYqH8izw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-178281-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=178281

--- Comment #12 from fin4478@hotmail.com ---
With Tomb Raider Legend the game hangs Xserver in one minute when playing at
fullhd.Dropping resolution to 720p allows to play stable. drm-next-4.10-wip and
Oipaf ppa mesa from yesterday used. There is no matter if csmt in wine-staging
is enabled or not.

OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD POLARIS11 (DRM 3.9.0 / 4.9.0-rc2+,
LLVM 3.9.0)
OpenGL core profile version string: 4.3 (Core Profile) Mesa 13.1.0-devel
OpenGL core profile shading language version string: 4.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 13.1.0-devel
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 13.1.0-devel
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10

I needed to configure 4.9 kernel like a stock laptop kernel to make it more
stable when gaming.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-10-28  4:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18 11:17 [Bug 178281] New: wine-staging apps freezes the machine with RX460 bugzilla-daemon
2016-10-18 14:16 ` [Bug 178281] " bugzilla-daemon
2016-10-18 16:42 ` bugzilla-daemon
2016-10-18 17:12 ` bugzilla-daemon
2016-10-18 18:35 ` bugzilla-daemon
2016-10-19  7:12 ` bugzilla-daemon
2016-10-19 11:24 ` bugzilla-daemon
2016-10-19 12:56 ` bugzilla-daemon
2016-10-19 14:19 ` bugzilla-daemon
2016-10-21 15:40 ` bugzilla-daemon
2016-10-22 10:05 ` bugzilla-daemon
2016-10-26  0:22 ` bugzilla-daemon
2016-10-28  4:41 ` bugzilla-daemon [this message]
2016-10-28  6:22 ` bugzilla-daemon
2016-10-28  6:58 ` bugzilla-daemon
2016-10-28 11:10 ` bugzilla-daemon
2016-11-02  9:10 ` bugzilla-daemon
2018-12-05  2:31 ` 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-178281-2300-81nYqH8izw@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.