<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - [4.17-rc1] RIP: smu7_populate_single_firmware_entry.isra.6+0x57/0xc0 [amdgpu] RSP: ffffa17901efb930" href="https://bugs.freedesktop.org/show_bug.cgi?id=105760#c64">Comment # 64</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - [4.17-rc1] 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 <a class="email" href="mailto:peter@lekensteyn.nl" title="Peter Wu <peter@lekensteyn.nl>"> Peter Wu</a> <pre>(In reply to Thomas Martitz from <a href="show_bug.cgi?id=105760#c62">comment #62</a>) > To recap, the original bug (panic with that particular backtrace) is also > fixed for me. In that case, it is probably better to open a new bug report (and refer to this bug for context) for other issues. > It may be worth noting that on my system the eGPU seems to be behind the > same PCIe bridge as the TB3 port. I think I need at least to disable runtime > pm for that bridge but that alone isn't sufficient from my testing. The dGPU and TB devices appear behind different bridges (lspci -tv): -[0000:00]-+-00.0 Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers ... +-1c.0-[01]----00.0 Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 3100] ... +-1c.4-[03-3b]----00.0-[04-3b]--+-00.0-[05]----00.0 Intel Corporation JHL6340 Thunderbolt 3 NHI (C step) [Alpine Ridge 2C 2016] (In reply to Thomas Martitz from <a href="show_bug.cgi?id=105760#c63">comment #63</a>) > Maybe <a href="https://bugzilla.kernel.org/show_bug.cgi?id=156341">https://bugzilla.kernel.org/show_bug.cgi?id=156341</a> is related? I found > a related thread on the nouveau ML ("Rewriting Intel PCI bridge prefetch > base address bits solves nvidia graphics issues") that seems to talk about > similar resume problems. Maybe related (or maybe not), that's why I was asking for some detail (thanks for providing these!). But please do open a new bug since the original issue appears to be solved.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>