<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 - [BSW] System fail to enter hibernation with error message after load i915 driver"
href="https://bugs.freedesktop.org/show_bug.cgi?id=84902">84902</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[BSW] System fail to enter hibernation with error message after load i915 driver
</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>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>critical
</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>wendy.wang@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=107702" name="attach_107702" title="dmesg log file">attachment 107702</a> <a href="attachment.cgi?id=107702&action=edit" title="dmesg log file">[details]</a></span>
dmesg log file
==System Environment==
--------------------------
Regression: No.
It's first run tests on BSW
Non-working platforms: BSW
==kernel==
--------------------------
origin/drm-intel-nightly:
BOOT_IMAGE=kernels//nightly_parents/2014_10_11/drm-intel-nightly/ea4bec8e96ea8b33b49a7892c1c7f20041a56da6/bzImage_x86_64
root=/dev/sda4 drm.debug=0xe
modules_path=kernels//nightly_parents/2014_10_11/drm-intel-nightly/ea4bec8e96ea8b33b49a7892c1c7f20041a56da6/modules_x86_64/lib/modules/3.17.0_drm-intel-nightly_ea4bec_20141011+
acpi_rsdp=0x7b729014 kexec_jump_back_entry=0x5434a8e8
==Bug detailed description==
-----------------------------
With i915 driver loaded the fail symptom as below:
1. 1st cycle to execute "echo disk > /sys/power/state"
2. test machine will enter S4 successfully, then automatically resume back from
S4.
3. Second time to try "echo disk > /sys/power/state", system will fail to enter
into S4 with dmesge error:"
[ 90.753796] [drm] stuck on blitter ring
[ 90.776392] [drm] GPU HANG: ecode 2:0xfffffffe, reason: Ring hung, action:
reset
[ 90.780688] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 90.785052] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 90.789480] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 90.793974] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 90.798527] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 90.803502] i915 0000:00:02.0: GEM idle failed, resume might fail
[ 90.805296] drm/i915: Resetting chip after gpu hang
[ 90.812746] pci_pm_freeze(): i915_pm_freeze+0x0/0x34 [i915] returns -11
[ 90.817418] dpm_run_callback(): pci_pm_freeze+0x0/0xb5 returns -11
[ 90.822089] call 0000:00:02.0+ returned -11 after 5851154 usecs
[ 90.826773] PM: Device 0000:00:02.0 failed to freeze async: error -11
"
4. Disable i915 driver and system can enter S4 successfully both at the 1st or
2nd cycle.</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>