<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [HSW] Probabilistic resume from s4 causes call trace and system hang, with warm boot"
href="https://bugs.freedesktop.org/show_bug.cgi?id=65496">65496</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>[HSW] Probabilistic resume from s4 causes call trace and system hang, with warm boot
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>yangweix.shui@intel.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=80458" name="attach_80458" title="picture: probabilistic S4 call trace and hang">attachment 80458</a> <a href="attachment.cgi?id=80458&action=edit" title="picture: probabilistic S4 call trace and hang">[details]</a></span>
picture: probabilistic S4 call trace and hang
Environment:
-------------------
Kernel: (drm-intel-next-queued)d41ca032afdb4e12a9782df523c8798cd42aaaa3
Some additional commit info:
Author: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
Date: Thu Apr 11 19:49:07 2013 +0200
drm/i915: move debug output back to the right place
Description:
--------------------
This bug is used to separate from <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [HSW ULT desktop mobile bisected] Resume from s4 causes call trace and system hang, with cool boot"
href="show_bug.cgi?id=63586">bug #63586</a>, run S4 test in a loop, when
execute 95 times, system resume with call trace and hang. This issue is
probabilistic, perhaps it will come up to your eyes for just a while S4 test or
more. I append the picture of the call trace in attachment.
Reproduce step:
----------------------
1.boot up machine with command "reboot"(warm boot)
2.echo 0 > /sys/class/rtc/rtc0/wakealarm ;
echo +10 > /sys/class/rtc/rtc0/wakealarm;
3.echo disk > /sys/power/state
4.loop running step 2 and 3</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 the assignee for the bug.</li>
</ul>
</body>
</html>