From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73852] Dota 2: texture corruption (r600 on HD 6550M)
Date: Sat, 08 Feb 2014 03:39:44 +0000 [thread overview]
Message-ID: <bug-73852-502-ieKLWoEUps@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73852-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 807 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73852
--- Comment #5 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
(In reply to comment #3)
> I tried running Dota2 with
> R600_DEBUG=noinvalrange %command% -console
> R600_DEBUG=noinvalrange,nodma,nocpdma %command% -console
> R600_DEBUG=nodma,nocpdma %command% -console
>
> ...neither helps. I don't understand why 68451 has been marked as fixed
> though. I'll retry this weekend with 3.14rc2, unless someone advises on what
> next to try out.
See comment 48 in bug 68451 for an explanation about why it was marked as
fixed. In short, the original bug (identified problematic commit on given
hardware) has been fixed. The other reports must be treated as different bugs.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1937 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
prev parent reply other threads:[~2014-02-08 3:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 22:33 [Bug 73852] New: Dota 2: texture corruption (r600 on HD 6550M) bugzilla-daemon
2014-01-23 11:54 ` [Bug 73852] " bugzilla-daemon
2014-01-30 11:15 ` bugzilla-daemon
2014-02-07 19:48 ` bugzilla-daemon
2014-02-07 20:39 ` bugzilla-daemon
2014-02-08 0:17 ` bugzilla-daemon
2014-02-08 3:39 ` bugzilla-daemon [this message]
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-73852-502-ieKLWoEUps@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