All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82186] [r600g] BARTS GPU lockup with minecraft shaders
Date: Wed, 01 Jul 2015 18:36:20 +0000	[thread overview]
Message-ID: <bug-82186-502-Q47ChtSGfx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-82186-502@http.bugs.freedesktop.org/>


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

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

--- Comment #10 from MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com> ---
Alright, I finished testing the 3 problematic games which this bug affected for
me, to see how they behave with R600_DEBUG=notiling enabled. I don't use
shaders for MineCraft so I can't test them specifically, although we're
obviously talking about the same issue so this is still relevant. My results
are:

Second Life: No more GPU freeze when Advanced Lighting is enabled! This was one
of the most immediate triggers for the issue in my case, and in most scenarios
it immediately brought down the X server... now there is not a single hiccup.

Stunt Rally: No more freezes when enabling shaders! In its case however the
problem is more probabilistic, so this isn't 100% guaranteed.

One Late Night: The crash still exists, even with notiling. So there are still
cases where this variable does not solve the problem, although in most engines
it does and I'm happy enough with that for the time being.

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

[-- Attachment #1.2: Type: text/html, Size: 1888 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-07-01 18:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 11:06 [Bug 82186] New: BARTS GPU lockup with minecraft shaders bugzilla-daemon
2014-08-05 11:08 ` [Bug 82186] [r600g] " bugzilla-daemon
2014-08-08 10:03 ` bugzilla-daemon
2014-08-13 10:44 ` bugzilla-daemon
2014-08-13 11:48 ` bugzilla-daemon
2014-08-13 15:35 ` bugzilla-daemon
2014-11-19  2:39 ` bugzilla-daemon
2014-11-19  6:16 ` bugzilla-daemon
2014-11-19 16:01 ` bugzilla-daemon
2014-11-20 20:45 ` bugzilla-daemon
2015-07-01 17:54 ` bugzilla-daemon
2015-07-01 18:36 ` bugzilla-daemon [this message]
2015-07-02 10:36 ` 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-82186-502-Q47ChtSGfx@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.