<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [SNB] Glxgears frozen under gnome-session in stress test with Q4 release"
href="https://bugs.freedesktop.org/show_bug.cgi?id=72508#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [SNB] Glxgears frozen under gnome-session in stress test with Q4 release"
href="https://bugs.freedesktop.org/show_bug.cgi?id=72508">bug 72508</a>
from <span class="vcard"><a class="email" href="mailto:jianx.zhou@intel.com" title="zhoujian <jianx.zhou@intel.com>"> <span class="fn">zhoujian</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=72508#c9">comment #9</a>)
<span class="quote">> Bisect fail, you fell down the rabbit hole of chasing a different bug. To
> confirm yet again,you do not see the bug with the current ddx?</span >
In this stress test,glxgears loop running 100 times as a round.
On 2013Q4,the frame of a glxgears would frozed when running to 30~50 time(only
one round),but after a few seconds, then glxgears would work well again.
Eerros in demsg:"[65598.315187] [drm:i915_set_reset_status] *ERROR* render
ring hung inside bo(0x55e6000 ctx 1) at 0x55e6220"
On 2013Q2,it's OK (I have tried 4 rounds,all passed).
I'm sorry,the problem doesn't seem caused by xf86.
I find that the probability of reproduing the bug is quit lower with old
driver.
It's difficult to find out which commpent.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>