<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Horizontal lines in radeon driver on kernel 3.15 and upwards"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87682#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Horizontal lines in radeon driver on kernel 3.15 and upwards"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87682">bug 87682</a>
from <span class="vcard"><a class="email" href="mailto:chris.bainbridge@gmail.com" title="Chris Bainbridge <chris.bainbridge@gmail.com>"> <span class="fn">Chris Bainbridge</span></a>
</span></b>
<pre><span class="quote">> As far as I understand; 3.15.0-rc2-00077-g76e7745 is a later revision (good)
> than 3.15.0-rc2-00069-g1aae31c (bad)</span >
This is not correct. The 77/69 does not imply a linear ordering because of
forks:
$ git merge-base --is-ancestor 3.15.0-rc2-00069-g1aae31c
3.15.0-rc2-00077-g76e7745; echo $?
1
Trust git ;-)
<span class="quote">> c2fb3094669a3205f16a32f4119d0afe40b1a1fd is the first bad commit</span >
Not familiar with this code, but from the patch the PLL values are printed out:
DRM_DEBUG_KMS("%d - %d, pll dividers - fb: %d.%d ref: %d, post %d\n",
freq, *dot_clock_p * 10, *fb_div_p, *frac_fb_div_p,
ref_div, post_div);
So suggest enabling debug log and compare those two lines from a working and
non-working kernel.
It should also be trivial to checkout a recent tag and revert the bad commit
(there is a conflict but just delete the avivo_get_fb_ref_div function to
resolve it).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>