<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [bisected] [SI Scheduler] Graphical corruption in Dota 2"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88978#c17">Comment # 17</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [bisected] [SI Scheduler] Graphical corruption in Dota 2"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88978">bug 88978</a>
from <span class="vcard"><a class="email" href="mailto:tstellar@gmail.com" title="Tom Stellard <tstellar@gmail.com>"> <span class="fn">Tom Stellard</span></a>
</span></b>
<pre>(In reply to Tom Stellard from <a href="show_bug.cgi?id=88978#c16">comment #16</a>)
<span class="quote">> (In reply to Daniel Scharrer from <a href="show_bug.cgi?id=88978#c15">comment #15</a>)
> > Created <span class=""><a href="attachment.cgi?id=116176" name="attach_116176" title="dmesg log">attachment 116176</a> <a href="attachment.cgi?id=116176&action=edit" title="dmesg log">[details]</a></span>
> > dmesg log
> >
> > Here is the dmesg log with Linux 4.0.4-gentoo and LLVM patched to disable
> > the machine scheduler for SI, after replaying both sarnex' and my trace. I
> > don't have an unpatched LLVM build right now, but don't remember the dmesg
> > output being different.
> >
> > The log is compressed because there are lots of GPU faults at the end (bug
> > #87278) which pushed the uncompressed log over the attachment size limit -
> > not sure if you wanted those or just the startup part.
> >
> > <a class="bz_bug_link
bz_status_NEW "
title="NEW - [LLVM][bisected] GPU lockups in Left 4 Dead 2"
href="show_bug.cgi?id=90378">Bug #90378</a> has the dmesg output for L4D2 including GPU lockups with an
> > unpatched (but older revision on) LLVM and 4.0.1-gentoo in <span class=""><a href="attachment.cgi?id=115653" name="attach_115653" title="dmesg output">attachment 115653</a> <a href="attachment.cgi?id=115653&action=edit" title="dmesg output">[details]</a></span>
> > [details].
>
> Would you be able to post an API trace of one of the games that is locking
> up?</span >
Nevermind, I think the one you posted already should be enough.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>