From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89685] Cripling Dota 2 freeze with Morphling at hero selection or loadout
Date: Sat, 04 Apr 2015 22:30:00 +0000 [thread overview]
Message-ID: <bug-89685-502-p7IAOOrW9X@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89685-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 679 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=89685
--- Comment #11 from Kevin <wittyman37@yahoo.com> ---
(In reply to Kevin from comment #9)
> (In reply to Tom Stellard from comment #3)
> > Can you run the game with R600_DEBUG=ps,vs,gs and post the output?
>
> OK, sorry, I just saw this. So I know some of what I'm doing by not a lot. I
> do `export R600_DEBUG=ps,vs,gs` and then run the game? Where and how do I
> get output? dmesg? jounralctl? Something else?
I'm not sure if this is what you are looking for, but I am attaching new
journalctl and dmesg outputs after enabling R600_DEBUG=ps,vs,gs
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1600 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
next prev parent reply other threads:[~2015-04-04 22:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 23:21 [Bug 89685] Cripling Dota 2 freeze with Morphling at hero selection or loadout bugzilla-daemon
2015-03-25 21:08 ` bugzilla-daemon
2015-03-25 21:08 ` bugzilla-daemon
2015-03-25 21:10 ` bugzilla-daemon
2015-04-04 1:14 ` bugzilla-daemon
2015-04-04 1:16 ` bugzilla-daemon
2015-04-04 1:17 ` bugzilla-daemon
2015-04-04 1:18 ` bugzilla-daemon
2015-04-04 1:30 ` bugzilla-daemon
2015-04-04 3:54 ` bugzilla-daemon
2015-04-04 22:01 ` bugzilla-daemon
2015-04-04 22:28 ` bugzilla-daemon
2015-04-04 22:30 ` bugzilla-daemon [this message]
2015-04-04 22:31 ` bugzilla-daemon
2015-04-04 22:31 ` bugzilla-daemon
2015-04-16 7:48 ` bugzilla-daemon
2015-04-29 0:15 ` bugzilla-daemon
2015-04-29 0:31 ` bugzilla-daemon
2015-04-29 1:53 ` bugzilla-daemon
2015-04-30 0:02 ` bugzilla-daemon
2015-04-30 0:24 ` bugzilla-daemon
2015-04-30 0:54 ` bugzilla-daemon
2015-04-30 3:22 ` bugzilla-daemon
2015-05-02 19:24 ` bugzilla-daemon
2015-05-03 20:21 ` bugzilla-daemon
2015-05-13 2:00 ` bugzilla-daemon
2018-04-03 3:43 ` bugzilla-daemon
2018-04-03 3:45 ` bugzilla-daemon
2018-04-03 6:27 ` 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-89685-502-p7IAOOrW9X@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