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 89785] GPU Fault 147 and Ring Stalls and Tests Fail in Pillars of Eternity
Date: Fri, 27 Mar 2015 18:55:01 +0000	[thread overview]
Message-ID: <bug-89785-502-bjvtgooeeB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89785-502@http.bugs.freedesktop.org/>


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

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

--- Comment #2 from Matthew Scheirer <matt.scheirer@gmail.com> ---
The game is capturing stderr and won't give me any shader output, the syntax I
was using was R600_DEBUG=vs,gs,ps ./PillarsOfEternity 2> ~/poe-crash-log.txt,
also tried &> log and only got its Unity output. Other Gallium tunables like
gallium_hud work, so it seems just to be internal stderr capture in Mono or
Unity. Not well versed in either enough to know if there is a way to circumvent
them, though, and Google isn't helping.

Any other options? It seems really bizarre that this game works on Intel,
Nvidia (blob), and OSX drivers if it has broken GLSL shaders.

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

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

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

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

  parent reply	other threads:[~2015-03-27 18:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27  0:46 [Bug 89785] GPU Fault 147 and Ring Stalls and Tests Fail in Pillars of Eternity bugzilla-daemon
2015-03-27  1:14 ` bugzilla-daemon
2015-03-27 18:55 ` bugzilla-daemon [this message]
2015-03-28  0:21 ` bugzilla-daemon
2015-03-28  0:57 ` bugzilla-daemon
2015-03-28 17:55 ` bugzilla-daemon
2015-03-28 21:00 ` bugzilla-daemon
2015-03-29  9:48 ` bugzilla-daemon
2015-03-29 20:24 ` bugzilla-daemon
2015-03-30 18:28 ` bugzilla-daemon
2015-03-31 19:04 ` bugzilla-daemon
2015-04-01 19:58 ` bugzilla-daemon
2015-04-02  1:43 ` bugzilla-daemon
2015-04-03 11:58 ` bugzilla-daemon
2015-04-05 21:09 ` bugzilla-daemon
2017-02-15 21:37 ` 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-89785-502-bjvtgooeeB@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