<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 - [BYT/BSW Bisected] Suspend Resume time increase to 6000+ ms"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90868">90868</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[BYT/BSW Bisected] Suspend Resume time increase to 6000+ ms
</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=116315" name="attach_116315" title="suspend resume time failure dmesg">attachment 116315</a> <a href="attachment.cgi?id=116315&action=edit" title="suspend resume time failure dmesg">[details]</a></span>
suspend resume time failure dmesg
==System Environment==
-----------------------------------------------------
Kernel Regression: Yes
Non-working platforms: BYT/HSW
Bisect result show :
490f400db5d886fc28566af69b02f6497f31be4b is the first bad commit
commit 490f400db5d886fc28566af69b02f6497f31be4b
Author: Maarten Lankhorst <<a href="mailto:maarten.lankhorst@linux.intel.com">maarten.lankhorst@linux.intel.com</a>>
Date: Mon Jun 1 12:50:05 2015 +0200
drm/i915: Make intel_display_suspend atomic, v2.
Calculate all state using a normal transition, but afterwards fudge
crtc->state->active back to its old value. This should still allow
state restore in setup_hw_state to work properly.
Calling intel_set_mode will cause intel_display_set_init_power to be
called, make sure init_power gets set again afterwards.
Changes since v1:
- Fix to compile with v2 of the patch that adds intel_display_suspend.
- Add intel_display_set_init_power.
- Set return value to int to allow error checking.
Signed-off-by: Maarten Lankhorst <<a href="mailto:maarten.lankhorst@linux.intel.com">maarten.lankhorst@linux.intel.com</a>>
Reviewed-by: Matt Roper <<a href="mailto:matthew.d.roper@intel.com">matthew.d.roper@intel.com</a>>
Signed-off-by: Jani Nikula <<a href="mailto:jani.nikula@intel.com">jani.nikula@intel.com</a>>
:040000 040000 b53b1c05451c72787a26e1efc85c0e544ae1ec94
1e8df3b7f16307d9e637276c10c54e
3b94850486 M
drivers
==Bug detailed description==
Suspend resume time is too large: 6000+ ms
==Reproduce steps==
----------------------------
1. Boot up system with initcall_debug drm.debug=0xe kernel parameter
2. echo 0 > /sys/class/rtc/rtc0/wakealarm
echo +20 > /sys/class/rtc/rtc0/wakealarm
echo mem > /sys/power/state
3. run attached script.</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>