[Bug 90868] New: [BYT/BSW Bisected] Suspend Resume time increase to 6000+ ms
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Jun 5 01:51:19 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=90868
Bug ID: 90868
Summary: [BYT/BSW Bisected] Suspend Resume time increase to
6000+ ms
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: critical
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: wendy.wang at intel.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 116315
--> https://bugs.freedesktop.org/attachment.cgi?id=116315&action=edit
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 <maarten.lankhorst at linux.intel.com>
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 <maarten.lankhorst at linux.intel.com>
Reviewed-by: Matt Roper <matthew.d.roper at intel.com>
Signed-off-by: Jani Nikula <jani.nikula at intel.com>
: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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150605/f3172042/attachment.html>
More information about the intel-gfx-bugs
mailing list