<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> <span class="fn">Daniel Vetter</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - Warnings after resume in i915"
href="https://bugs.freedesktop.org/show_bug.cgi?id=65497">bug 65497</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>NEEDINFO
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - Warnings after resume in i915"
href="https://bugs.freedesktop.org/show_bug.cgi?id=65497#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - Warnings after resume in i915"
href="https://bugs.freedesktop.org/show_bug.cgi?id=65497">bug 65497</a>
from <span class="vcard"><a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> <span class="fn">Daniel Vetter</span></a>
</span></b>
<pre>For the time out warning, can you please check whether it goes away if you
increase the timeout:
diff --git a/drivers/gpu/drm/i915/intel_lvds.c
b/drivers/gpu/drm/i915/intel_lvds.c
index 10c3d56..7e0ee01 100644
--- a/drivers/gpu/drm/i915/intel_lvds.c
+++ b/drivers/gpu/drm/i915/intel_lvds.c
@@ -200,7 +200,7 @@ static void intel_enable_lvds(struct intel_encoder
*encoder)
I915_WRITE(ctl_reg, I915_READ(ctl_reg) | POWER_TARGET_ON);
POSTING_READ(lvds_encoder->reg);
- if (wait_for((I915_READ(stat_reg) & PP_ON) != 0, 1000))
+ if (wait_for((I915_READ(stat_reg) & PP_ON) != 0, 2000))
DRM_ERROR("timed out waiting for panel to power on\n");
intel_panel_enable_backlight(dev, intel_crtc->pipe);
If that works then most likely the firmware on your board sets up a
ridiculously high panel power on delay.
For the WARNs we need dmesg with drm.debug=0xe added to your kernel
commandline. They are self-checks of our modeset code to make sure the hw state
agrees with our sw tracking. Usually they do indicate real issues, but
sometimes there's also a tiny bug in the checker itself.</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 the assignee for the bug.</li>
</ul>
</body>
</html>