<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#c6">Comment # 6</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:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>(In reply to Darren from <a href="show_bug.cgi?id=92858#c5">comment #5</a>)
<span class="quote">> Sadly, as of thus far, every kernel I've compiled panics at bootup, with a
> message like this, or similar: "kernel panic. vfs unable to mount root on
> unknown block (0,0)".</span >
Sounds like there's a problem with the .config or maybe the root=[...]
parameter on the kernel command line. For .config, I'd recommend starting with
the original .config from 4.3-rc7 and then just running "make oldconfig".
<span class="quote">> After I get the kernel to compile and boot, do I need to run "make clean" in
> the source tree directory after "git bisect good," or is that going to strip
> away files that git bisect needs in order to keep a record of good and bad
> commits?</span >
make clean is neither necessary nor does it hurt (other than potentially
increasing the build time of the next kernel to test).</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>