<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [4.17-drm-wip] RIP: smu7_populate_single_firmware_entry.isra.6+0x57/0xc0 [amdgpu] RSP: ffffa17901efb930"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105760#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [4.17-drm-wip] RIP: smu7_populate_single_firmware_entry.isra.6+0x57/0xc0 [amdgpu] RSP: ffffa17901efb930"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105760">bug 105760</a>
from <span class="vcard"><a class="email" href="mailto:taijian@posteo.de" title="taijian@posteo.de">taijian@posteo.de</a>
</span></b>
<pre>OK, I think I've managed to narrow this one down a bit.
If I build the kernel from commit 09695ad78f1f5f315c7e9c5090f0c7b846a43690,
which is also tagged as 'drm-next-4.17', then everything is shiny. However, if
I go one step beyond that, which is commit
33d009cd889490838c5db9b9339856c9e3d3facc - being the rebasing of
drm-next-4.17-wip onto David Airlie's drm-next branch after he merged AMD's
drm-next-4.17 into his branch, then things to belly up and the kernel does not
boot anymore.
Now, what I do not get is how the rebase to a tree that includes stuff that is
not amdgpu would bork up the ability of amdgpu to load it's firmware?</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>