dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94900] HD6950 GPU lockup loop with various steam games (octodad, saints row 4, grid autosport)
Date: Sat, 16 Jul 2016 10:51:13 +0000	[thread overview]
Message-ID: <bug-94900-502-1SDOPeAI5Y@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94900-502@http.bugs.freedesktop.org/>


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

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

--- Comment #14 from iive@yahoo.com ---
@Daniel T.
FYI 12.1 would be the next release. The first bugfix release 12.0.1 is already
out (fixes compilation with debugging).
The shader backend is very specific to r600 cards and very few people even
touch it. So there is no way this bugs gets fixed by accident.

@eydee,
Are you using environment variables for the override in drirc file?
`
export MESA_GL_VERSION_OVERRIDE=4.1
export MESA_GLSL_VERSION_OVERRIDE=410
`
should set override for any programs started from this bash session onward.

If you prefer drirc override, then have in mind that `glretrace` is the program
that does the actual playback/replay.

If you upload a trace I could try to narrow it down, but my card also needs the
override.

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

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

  parent reply	other threads:[~2016-07-16 10:51 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 21:41 [Bug 94900] Regression: HD6950 GPU lockup with octodad: dadliest catch bugzilla-daemon
2016-04-11 22:52 ` [Bug 94900] " bugzilla-daemon
2016-04-11 22:53 ` bugzilla-daemon
2016-04-15  3:49 ` bugzilla-daemon
2016-05-03 11:05 ` [Bug 94900] HD6950 GPU lockup with various steam games (octodad, saints row 4) bugzilla-daemon
2016-05-03 11:06 ` bugzilla-daemon
2016-05-04 21:23 ` bugzilla-daemon
2016-05-06 11:37 ` bugzilla-daemon
2016-05-06 11:38 ` bugzilla-daemon
2016-05-06 19:30 ` bugzilla-daemon
2016-05-06 20:32 ` bugzilla-daemon
2016-05-16  9:05 ` bugzilla-daemon
2016-05-16  9:05 ` [Bug 94900] HD6950 GPU lockup loop with various steam games (octodad, saints row 4, grid autosport) bugzilla-daemon
2016-05-16 10:00 ` bugzilla-daemon
2016-06-06 11:57 ` bugzilla-daemon
2016-06-06 11:58 ` bugzilla-daemon
2016-07-12 22:21 ` bugzilla-daemon
2016-07-13 12:06 ` bugzilla-daemon
2016-07-16  1:50 ` bugzilla-daemon
2016-07-16 10:51 ` bugzilla-daemon [this message]
2016-07-16 13:53 ` bugzilla-daemon
2016-07-16 14:18 ` [Bug 94900] HD6950 GPU lockup loop with various steam games (octodad, saints row 4, dead island, " bugzilla-daemon
2016-07-16 16:20 ` bugzilla-daemon
2016-07-16 16:20 ` bugzilla-daemon
2016-07-16 16:26 ` [Bug 94900] HD6950 GPU lockup loop with various steam games (octodad[always], saints row 4[always], dead island[always], grid autosport[sometimes]) bugzilla-daemon
2016-07-17 21:36 ` bugzilla-daemon
2016-07-18  9:04 ` bugzilla-daemon
2016-07-18 10:26 ` bugzilla-daemon
2016-07-23  8:43 ` bugzilla-daemon
2016-09-02  8:11 ` bugzilla-daemon
2016-09-09  4:52 ` bugzilla-daemon
2016-09-17 20:23 ` bugzilla-daemon
2016-09-18 15:37 ` bugzilla-daemon
2016-09-22 14:59 ` bugzilla-daemon
2016-09-23  7:35 ` bugzilla-daemon
2016-09-28 17:26 ` bugzilla-daemon
2016-09-28 17:40 ` bugzilla-daemon
2016-10-02 10:07 ` bugzilla-daemon
2016-10-02 10:13 ` bugzilla-daemon
2016-10-02 10:29 ` bugzilla-daemon
2016-10-04 15:47 ` bugzilla-daemon
2016-10-30  9:11 ` bugzilla-daemon
2016-12-16 13:32 ` bugzilla-daemon
2016-12-22  8:37 ` bugzilla-daemon
2017-01-12 10:53 ` 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-94900-502-1SDOPeAI5Y@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).