<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:ckoenig.leichtzumerken@gmail.com" title="Christian König <ckoenig.leichtzumerken@gmail.com>"> <span class="fn">Christian König</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - *ERROR* hw_init of IP block <gfx_v8_0> failed -22"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108585">bug 108585</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>NOTABUG
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - *ERROR* hw_init of IP block <gfx_v8_0> failed -22"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108585#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - *ERROR* hw_init of IP block <gfx_v8_0> failed -22"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108585">bug 108585</a>
from <span class="vcard"><a class="email" href="mailto:ckoenig.leichtzumerken@gmail.com" title="Christian König <ckoenig.leichtzumerken@gmail.com>"> <span class="fn">Christian König</span></a>
</span></b>
<pre>(In reply to Benjamin Herrenschmidt from <a href="show_bug.cgi?id=108585#c6">comment #6</a>)
<span class="quote">> They may or may not be related ... Alex, kexec is how we boot these
> machines, there's a Linux kernel in flash that runs a Linux based bootloader.</span >
Yeah, you guys should have noted that because that combination is known to not
work correctly.
The problem is that some parts of the hardware are explicitly designed in a way
which only allows loading one firmware after an ASIC reset. So as long as kexec
doesn't makes a full PCIe level ASIC reset the second driver load is intended
to fail.
We have the same problem with virtualization and used to have a workaround in
KVM which triggers the ASIC reset with a PCIe config space write. Alex should
know the details.
Only solution I can see is to either use the same workaround as the KVM guys or
use the same firmware for both the loader and the final kernel.</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>