From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73785] [HyperZ] Team Fortress 2 causes random GPU stalls on radeonsi
Date: Mon, 09 May 2016 05:37:17 +0000 [thread overview]
Message-ID: <bug-73785-502-EiEptNe6ab@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73785-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 221 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73785
--- Comment #13 from Matías Locatti <matias.locatti@gmail.com> ---
R600_DEBUG=nohyperz right?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1038 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
next prev parent reply other threads:[~2016-05-09 5:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 5:52 [Bug 73785] New: Team Fortress 2 causes random GPU stalls on radeonsi bugzilla-daemon
2014-01-19 20:13 ` [Bug 73785] " bugzilla-daemon
2014-01-22 14:29 ` bugzilla-daemon
2014-01-22 14:37 ` [Bug 73785] Team Fortress 2 causes random GPU stalls on radeonsi with dpm enabled bugzilla-daemon
2014-01-22 14:38 ` bugzilla-daemon
2014-02-09 14:18 ` bugzilla-daemon
2014-02-10 22:30 ` bugzilla-daemon
2014-02-14 17:20 ` bugzilla-daemon
2014-02-14 20:52 ` [Bug 73785] [HyperZ] Team Fortress 2 causes random GPU stalls on radeonsi bugzilla-daemon
2014-02-17 18:58 ` bugzilla-daemon
2014-09-01 21:26 ` bugzilla-daemon
2014-09-03 10:33 ` bugzilla-daemon
2014-09-13 20:08 ` bugzilla-daemon
2015-02-24 22:51 ` bugzilla-daemon
2016-05-03 3:15 ` bugzilla-daemon
2016-05-05 15:51 ` bugzilla-daemon
2016-05-09 5:37 ` bugzilla-daemon [this message]
2016-05-09 5:48 ` bugzilla-daemon
2016-05-24 13:52 ` 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-73785-502-EiEptNe6ab@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.