<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 - [drm:ironlake_crtc_compute_clock [i915]] *ERROR* Couldn't find PLL settings for mode!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97363">97363</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[drm:ironlake_crtc_compute_clock [i915]] *ERROR* Couldn't find PLL settings for mode!
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</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>a-kobel@a-kobel.de
</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=125813" name="attach_125813" title="Xorg.log">attachment 125813</a> <a href="attachment.cgi?id=125813&action=edit" title="Xorg.log">[details]</a></span>
Xorg.log
This is a followup on <a href="https://bugzilla.kernel.org/show_bug.cgi?id=153181">https://bugzilla.kernel.org/show_bug.cgi?id=153181</a>, where
we were redirected to here.
Robin reports:
After upgrading to linux-4.7 I get the following error during boot time and
while starting Wayland or xserver (ends in a black screen):
[drm:ironlake_crtc_compute_clock [i915]] *ERROR* Couldn't find PLL settings for
mode!
I'm not sure if this is the cause for the error but I had a look to the changes
of the intel_driver.c between 4.6 and 4.7 and noticed the following:
With linux-4.6 the method ironlake_crtc_compute_clock used
ironlake_compute_clocks for retrieving the PLL settings. Which then used on of
the following methods depending on the given device:
- g4x_find_best_dpll
- chv_find_best_dpll
- vlv_find_best_dpll
- pnv_find_best_dpll
- i9xx_find_best_dpll
In linux-4.7 the method ironlake_crtc_compute_clock uses only this one
g4x_find_best_dpll.
I confirm on a Samsung NP900X4C laptop (Intel HD graphics 4000) on Arch Linux.
Worked fine in 4.6.5. Booting to the console already prints the message a
number of times. When trying to start X as root, the system freezes entirely
(only Magic SysRq to the rescue); as user, X fails to start, but the system
stays responsive. The error message from the title also appears whenever I
switch virtual terminals.
A discussion with some (unsuccessful) hints is here:
<a href="https://bbs.archlinux.org/viewtopic.php?id=215847">https://bbs.archlinux.org/viewtopic.php?id=215847</a>
Things that didn't work:
- uninstall xf86-video-intel and use the native modesetting
- add iomem=relaxed as a kernel parameter
I attach the dmesg output as well as an Xorg.log. The btrfs complaints are
unrelated and due to the fact that I had to shut down the system hard.</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>