<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 - MinnowBoard MAX DRM hang on linux-next 3.19-rc5 2015-02-26"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88805">88805</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>MinnowBoard MAX DRM hang on linux-next 3.19-rc5 2015-02-26
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg git
</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>normal
</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>dvhart@linux.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=112836" name="attach_112836" title="MinnowBoard MAX linux-next 3.19-rc5 2015-01-26 dmesg drm.debug=0x7">attachment 112836</a> <a href="attachment.cgi?id=112836&action=edit" title="MinnowBoard MAX linux-next 3.19-rc5 2015-01-26 dmesg drm.debug=0x7">[details]</a></span>
MinnowBoard MAX linux-next 3.19-rc5 2015-01-26 dmesg drm.debug=0x7
Olof Johanson originally reported his MinnowBoard MAX hung using linux-next
3.19-rc5+, I reproduced this using linux-next from 2015-01-26. His dmesg is
here:
<a href="http://arm-soc.lixom.net/bootlogs/next/next-20150123/minnowmax-x86-minnowmax_defconfig.html">http://arm-soc.lixom.net/bootlogs/next/next-20150123/minnowmax-x86-minnowmax_defconfig.html</a>
My dmesg is attached, the final drm messages leading to the hang follow:
...
[ 1.673003] [drm] Initialized drm 1.1.0 20060810
[ 1.679809] [drm] Memory usable by graphics device = 2048M
[ 1.685985] [drm] Replacing VGA console driver
[ 1.693153] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 1.700581] [drm] Driver supports precise vblank timestamp query.
[ 1.736168] vgaarb: device changed decodes:
PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 1.988096] [drm] failed to retrieve link info, disabling eDP
This was bisected to:
commit fc72355f5c04c40f2916a07e9f8d4b357e2e0a93
Author: Mika Kuoppala <<a href="mailto:mika.kuoppala@linux.intel.com">mika.kuoppala@linux.intel.com</a>>
AuthorDate: Mon Jan 19 16:20:43 2015 +0200
Commit: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
CommitDate: Tue Jan 20 12:36:57 2015 +0100
drm/i915: Consolidate forcewake code
Which appears to be related to the patch Jani V created to resolve a similar
issue for this board:
commit 05adaf1f101f25f40f12c29403e6488f0e45f6b6
Author: Jani Nikula <<a href="mailto:jani.nikula@intel.com">jani.nikula@intel.com</a>>
Date: Fri May 9 14:52:34 2014 +0300
drm/i915/vlv: reset VLV media force wake request register
Jani confirms:
"""
That's the fix all right.
However there's
[ 2.032075] [drm] failed to retrieve link info, disabling eDP
in the logs suggesting the minnowmax tries to initialize eDP which it
doesn't have. That's a VBT problem in itself, but since
commit d2182a660808d9053a605e3ebc8c46a323ec6e5d
Author: Ville Syrjälä <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>>
Date: Fri Jan 9 14:21:14 2015 +0200
drm/i915: Don't register HDMI connectors for eDP ports on VLV/CHV
we don't register HDMI if there's an eDP in the same port...
Potentially two problems I think.
"""</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>