[Bug 72211] New: [HSW]S3 response time larger than expected
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun Dec 1 19:11:28 PST 2013
https://bugs.freedesktop.org/show_bug.cgi?id=72211
Priority: medium
Bug ID: 72211
CC: intel-gfx-bugs at lists.freedesktop.org
Assignee: intel-gfx-bugs at lists.freedesktop.org
Summary: [HSW]S3 response time larger than expected
QA Contact: intel-gfx-bugs at lists.freedesktop.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: qingshuai.tian at intel.com
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Intel
Product: DRI
Created attachment 90071
--> https://bugs.freedesktop.org/attachment.cgi?id=90071&action=edit
dmseg after a round of s3
Environment:
--------------------
Kernel: (drm-intel-nightly)be46ffd48ba34189336c6fe420ff3370dcd36c60
Some additional commit info:
Author: Ville Syrjälä <ville.syrjala at linux.intel.com>
Date: Fri Nov 29 13:21:49 2013 +0200
drm/i915: Fix port name in vlv_wait_port_ready() timeout warning
Bug detailed description:
-----------------------------
When I test on a HSW ULT machine with a eDP monitor , 3 response time of i915
init,suspend and resume are quite larger than expected.
I list the result below:
Acquire initcall time: 1672.811 msecs
Acquire suspend time: 1093.865 msecs
Acquire resume time: 625.535 msecs
Machin Info: Lenovo idealpad u330p
BIOS Version: 7CCN15WW
CPU: Intel(R) Core(TM) i3-4010U CPU @1.70GHZ
Reproduce Steps:
--------------------
1. Rebuild kernel with option CONFIG_PM_TRACE.
2. Boot system with kernel command: initcall_debug drm.debug=0xe
3. perform a suspend-resume cycle by executing 'echo mem > /sys/power/state'
4. The dump the dmesg with the following command:
dmesg | grep -i -e "i915_init\|PM:.*complete\|00:02.0+"
--
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/20131202/36e98cdd/attachment.html>
More information about the intel-gfx-bugs
mailing list