<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [SNB]System fails to suspend from second time in "drm_suspend_s3" test"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90252">90252</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[SNB]System fails to suspend from second time in "drm_suspend_s3" test
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>haox.chen@intel.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=115469" name="attach_115469" title="dmesg">attachment 115469</a> <a href="attachment.cgi?id=115469&action=edit" title="dmesg">[details]</a></span>
dmesg
System Environment==
--------------------------
Regression: Yes.Good commit:d600654ab94b325f253e267422dcf60302120ea0
==Bug detailed description==
-----------------------------
1.echo mem > /sys/power/state
2.resume the machine
3.repeat above steps for 5 times
>From the second time,the machine can't suspend.
dmesg shows:
[ 44.768274] [drm] stuck on render ring
[ 44.768658] [drm] GPU HANG: ecode 6:0:0x00d3ffe0, reason: Ring hung, action:
reset
[ 44.768659] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 44.768659] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 44.768660] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 44.768660] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 44.768661] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 44.768675] [drm:i915_reset_and_wakeup] resetting chip
[ 44.768697] i915 0000:00:02.0: GEM idle failed, resume might fail
[ 44.768712] pci_pm_suspend(): i915_pm_suspend+0x0/0x3f [i915] returns -11
[ 44.768715] dpm_run_callback(): pci_pm_suspend+0x0/0xf6 returns -11
[ 44.768718] PM: Device 0000:00:02.0 failed to suspend async: error -11
[ 44.768753] PM: Some devices failed to suspend, or early wake event detected
[ 44.768952] rtc_cmos 00:02: System wakeup disabled by ACPI
[ 44.769550] serial 00:04: activated
[ 44.769995] drm/i915: Resetting chip after gpu hang
[ 44.790393] sd 0:0:0:0: [sda] Starting disk
[ 44.793317] tpm_tis 00:05: TPM is disabled/deactivated (0x7)
[ 44.929257] PM: resume of devices complete after 160.318 msecs
[ 44.942465] PM: Finishing wakeup.
[ 44.942466] Restarting tasks ... done.
==Reproduce steps==
----------------------------
1.echo mem > /sys/power/state
2.resume the machine
3.repeat above steps for 5 times
>From the second time,the machine can't suspend.</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>