From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88978] [bisected] [SI Scheduler] Graphical corruption in Dota 2
Date: Mon, 09 Feb 2015 03:39:33 +0000 [thread overview]
Message-ID: <bug-88978-502-cUA8onrjpJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-88978-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1134 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=88978
--- Comment #6 from Tom Stellard <tstellar@gmail.com> ---
(In reply to sarnex from comment #5)
> (In reply to Tom Stellard from comment #4)
> > (In reply to sarnex from comment #0)
> > > Hi guys. If I use LLVM git, I get these graphical glitches in Dota 2 native.
> > >
> > > https://i.imgur.com/I4vyWFt.jpg
> > >
> > > The bug has been bisected to LLVM: 51a3c27d6e0c66cc8d2d1da8e9205fec7b74ca5c
> > > R600/SI: Define a schedule model and enable the generic machine scheduler
> > >
> > >
> > > I'm using Mesa git, Kernel 3.18.5 and Linux Mint.
> > >
> > > Thanks alot,
> > >
> > > sarnex
> >
> > Can you run the game with the environment variable:
> > R600_DEBUG=ps,vs,gs and post the output.
>
> Hi Tom, thanks for replying.
>
> The log is here, since it's too big to be an attachment. Skip to near the
> end to see the in-game bugged time, the beginning is mostly the menu.
>
> Log: http://paste.ubuntu.com/10075950/
Thanks, would you also be able to get a dump using the last good commit.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2316 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-02-09 3:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 3:34 [Bug 88978] [bisected] [SI Scheduler] Graphical corruption in Dota 2 bugzilla-daemon
2015-02-05 4:39 ` bugzilla-daemon
2015-02-05 5:17 ` bugzilla-daemon
2015-02-05 5:30 ` bugzilla-daemon
2015-02-05 14:35 ` bugzilla-daemon
2015-02-05 16:54 ` bugzilla-daemon
2015-02-09 3:39 ` bugzilla-daemon [this message]
2015-02-09 15:24 ` bugzilla-daemon
2015-02-19 19:27 ` bugzilla-daemon
2015-02-20 1:52 ` bugzilla-daemon
2015-02-20 3:26 ` bugzilla-daemon
2015-04-12 15:08 ` bugzilla-daemon
2015-05-23 20:43 ` bugzilla-daemon
2015-05-23 20:45 ` bugzilla-daemon
2015-05-23 20:45 ` bugzilla-daemon
2015-05-30 1:05 ` bugzilla-daemon
2015-05-30 14:08 ` bugzilla-daemon
2015-06-01 15:00 ` bugzilla-daemon
2015-06-01 15:08 ` bugzilla-daemon
2015-06-02 3:55 ` bugzilla-daemon
2015-07-31 17:55 ` bugzilla-daemon
2015-08-01 7:02 ` 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-88978-502-cUA8onrjpJ@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