<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [ilk] Batch buffer corruption"
href="https://bugs.freedesktop.org/show_bug.cgi?id=83564#c14">Comment # 14</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [ilk] Batch buffer corruption"
href="https://bugs.freedesktop.org/show_bug.cgi?id=83564">bug 83564</a>
from <span class="vcard"><a class="email" href="mailto:eebfrasn-bugreply@usa.net" title="eebfrasn-bugreply@usa.net">eebfrasn-bugreply@usa.net</a>
</span></b>
<pre>Just came up with a new experiment (how did I not think of it earlier??): check
if it is related to resolution or to the fact that I use DisplayPort:
test1: reduce the resolution to full HD (1920x1080 instead of 2560x1440), try
both with DP and HDMI cable. Result: rock-solid, no failures, no freezes.
test2: test with HDMI cable, resolution set to 1920x1080 and to 2560x1440 (the
latter with 30Hz refresh, because the Intel chip cannot clock this resolution
at 60Hz on HDMI). Result: on HD it works fine, on the high res it freezes just
as with DP.
Conclusion: this is clearly related to the larger display area - could be
integer overflow of some kind, which just does not happen on the regular HD
resolution.
No asserts were observed on GDB (I have recent sources compiled with these
config options: '--enable-xvmc' '--enable-debug' '--prefix=/usr').</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>