<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - AMD Radeon GPU Acceleration Disabled Under Kernels 4.2.x and later versions"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92858#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - AMD Radeon GPU Acceleration Disabled Under Kernels 4.2.x and later versions"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92858">bug 92858</a>
from <span class="vcard"><a class="email" href="mailto:ysxikrhn@vomoto.com" title="Darren D. <ysxikrhn@vomoto.com>"> <span class="fn">Darren D.</span></a>
</span></b>
<pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=92858#c15">comment #15</a>)
<span class="quote">> (In reply to Michel Dänzer from <a href="show_bug.cgi?id=92858#c14">comment #14</a>)
> > ... I think you'll need to restart the bisection process with
> > 744b058827b3db9a4f6027522dd9c73a208c2d31 as the initial good commit [...]
>
> Actually, you can start with 91d9f9856f91c82ac6289a0fff65dd12cfa07e34 as the
> initial good commit.</span >
I can restart it yet again, and at least this time it'll be a narrower range of
commits.
And this is the sequence of commands I should use to do that, correct?
git bisect start
git bisect good 91d9f9856f91c82ac6289a0fff65dd12cfa07e34
git bisect bad 692a59e696afe1a4e777d0e4359325336ab0ad89
And if I start running into unbootable kernels again, I should start a new
bisect with a different copy of the source tree and identify at which commit
the compiled kernel started failing to boot, shouldn't I?</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>