<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <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#c14">Comment # 14</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 <a class="email" href="mailto:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> Alex Deucher</a> <pre>Created <a href="attachment.cgi?id=142303" name="attach_142303" title="possible fix">attachment 142303</a> <a href="attachment.cgi?id=142303&action=edit" title="possible fix">[details]</a> <a href='page.cgi?id=splinter.html&bug=108585&attachment=142303'>[review]</a> possible fix (In reply to Benjamin Herrenschmidt from <a href="show_bug.cgi?id=108585#c12">comment #12</a>) > We have no control on what firmware is loaded by the target distro so the > right thing is going to reset the adapter. > > We'll probably need to add something to the amdgpu shutdown() path to force > an adapter reset. Does the attached patch help? I'd been hesitant to add reset to the shutdown path because it adds latency to the regular shutdown path and users complain when that slows down. > > Do you have details of what specific PCIe config space write you use ? FLR ? The reset sequence is asic specific. older parts just happened to use PCI config space to trigger a GPU reset via an AMD specific sequence. Newer GPUs reset via the PSP. FLR is only available on SR-IOV capable skus so it's not a general solution.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>