<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:an.inbox@free.fr" title="Jerome <an.inbox@free.fr>"> <span class="fn">Jerome</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BDW] System hard lock-up on resume from suspend"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91585">bug 91585</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">i915 platform</td>
<td>
</td>
<td>BDW
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BDW] System hard lock-up on resume from suspend"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91585#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BDW] System hard lock-up on resume from suspend"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91585">bug 91585</a>
from <span class="vcard"><a class="email" href="mailto:an.inbox@free.fr" title="Jerome <an.inbox@free.fr>"> <span class="fn">Jerome</span></a>
</span></b>
<pre>With Intel kernel 4.2.0rc5, with old driver 2.21.15 (so LLVMpipe for 3D): I had
a lock-up at the 3rd resume (long hibernations, > 1h). I then tried quick
suspend/resume cycles and got 2 lock-ups in 6 cycles.
I then update the X Intel driver to 2.99.917 (still with Intel kernel
4.2.0rc5). Because glxgears may be too light to make a difference, I installed
and ran Tux racer. Then did suspend/resume cycles, mostly in short succession
but with some pauses of a few minutes at times: it locked-up at the 22nd resume
only.
So, to resume:
- the issue occurs both with LLVMpipe (X driver 2.21.15) and real hardware
acceleration (X driver 2.99.917). Also both with kernels 4.1.3 (Debian testing)
and Intel 4.2.0rc5, all 4 combinations tested;
- having running 3D clients when suspending does not seem to increase the
likelihood of a lock-up;
- the lock-up seems to happen early, before the mode switch to a graphical
setting (still in console mode when it locks up). By this I mean that anytime I
saw the glitch/flicker that happens when switching to graphical mode, then the
resume went fine (no lock-up);
- the lock-up frequency is highly variable, it's hard to make reliable
conclusion based on it. So ignore my previous comment on getting lock-up after
a long suspend duration, it's likely just chance and not relevant.
Please let me know how how you want to proceed here. Thanks</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>