<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [Regression HSW ULT] Calltrace when system resume from S4: WARNING: CPU: 0 PID: 6 at drivers/gpu/drm/i915/intel_display.c:10299 intel_get_pipe_from_connector+0x26/0x3c [i915]()"
href="https://bugs.freedesktop.org/show_bug.cgi?id=73688">73688</a>
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Assignee</th>
<td>jbarnes@virtuousgeek.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>[Regression HSW ULT] Calltrace when system resume from S4: WARNING: CPU: 0 PID: 6 at drivers/gpu/drm/i915/intel_display.c:10299 intel_get_pipe_from_connector+0x26/0x3c [i915]()
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>qingshuai.tian@intel.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=92209" name="attach_92209" title="dmesg after system resume from s4">attachment 92209</a> <a href="attachment.cgi?id=92209&action=edit" title="dmesg after system resume from s4">[details]</a></span>
dmesg after system resume from s4
Environment:
-------------------
Kernel: (drm-intel-next-queued) f1fcde49872f390a4060fa9ee8b02d3f2a8508b7
Machin Info: Lenovo idealpad u330p
Description:
--------------------
When testing s4 on a HSW ULT, there is Call trace information in dmesg after
the machine resume. You can check the dmesg in the attachment.
The Call trace will disappear when test with parameter "i915.modeset=0".
It's a regression, and I biscted it.
Bisect shows:
--------------------
752aa88a1e784c22d514db3b440e49427b58259e is the first bad commit
commit 752aa88a1e784c22d514db3b440e49427b58259e
Author: Jesse Barnes <<a href="mailto:jbarnes@virtuousgeek.org">jbarnes@virtuousgeek.org</a>>
Date: Thu Oct 31 18:55:49 2013 +0200
drm/i915: make backlight functions take a connector
On VLV/BYT, backlight controls a per-pipe, so when adjusting the
backlight we need to pass the correct info. So make the externally
visible backlight functions take a connector argument, which can be used
internally to figure out the pipe backlight to adjust.
v2: make connector pipe lookup check for NULL crtc (Jani)
fixup connector check in ASLE code (Jani)
v3: make sure we take the mode config lock around lookups (Daniel)
v4: fix double unlock in panel_get_brightness (Daniel)
v5: push ASLE work into a work queue (Daniel)
v6: separate ASLE work to a prep patch, rebase (Jani)
Signed-off-by: Jesse Barnes <<a href="mailto:jbarnes@virtuousgeek.org">jbarnes@virtuousgeek.org</a>>
Signed-off-by: Jani Nikula <<a href="mailto:jani.nikula@intel.com">jani.nikula@intel.com</a>>
Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
:040000 040000 8c3767165764c6e36b90d9e62b1e23940071d909
2d0aa55819f045debb6e14208bc30e6de516255f M drivers
Test Step:
--------------------
1.boot up machine
2.echo disk > /sys/power/state</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>
</ul>
</body>
</html>