<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Black screen on KMS with 4.18.0-rc1 with Kaveri+Topaz, amdgpu, dc=1"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106940#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Black screen on KMS with 4.18.0-rc1 with Kaveri+Topaz, amdgpu, dc=1"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106940">bug 106940</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>(In reply to SET from <a href="show_bug.cgi?id=106940#c15">comment #15</a>)
<span class="quote">> After narrowing good and bad commits between june 4th and 6th, it started to
> test commits in april, then december.</span >
That's normal, due to the non-linear Git history of the Linux kernel.
<span class="quote">> Some commits don't compile and must be skipped. This is going endless, can't
> continue.</span >
It will finish eventually.
Can you attach the current output of
git bisect log
and tell us the commit it wants to test next?</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>