<html><head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body> I retested hot plug tests at the commit I mentioned bellow - looks ok, my ASIC is Navi 10, I also tested using Vega 10 and older Polaris ASICs (whatever i had at home at the time). It's possible there are extra issues in ASICs like ur which I didn't cover during tests. andrey@andrey-test:~/drm$ sudo ./build/tests/amdgpu/amdgpu_test -s 13 /usr/local/share/libdrm/amdgpu.ids: No such file or directory /usr/local/share/libdrm/amdgpu.ids: No such file or directory /usr/local/share/libdrm/amdgpu.ids: No such file or directory The ASIC NOT support UVD, suite disabled /usr/local/share/libdrm/amdgpu.ids: No such file or directory The ASIC NOT support VCE, suite disabled /usr/local/share/libdrm/amdgpu.ids: No such file or directory /usr/local/share/libdrm/amdgpu.ids: No such file or directory /usr/local/share/libdrm/amdgpu.ids: No such file or directory The ASIC NOT support UVD ENC, suite disabled. /usr/local/share/libdrm/amdgpu.ids: No such file or directory /usr/local/share/libdrm/amdgpu.ids: No such file or directory /usr/local/share/libdrm/amdgpu.ids: No such file or directory /usr/local/share/libdrm/amdgpu.ids: No such file or directory Don't support TMZ (trust memory zone), security suite disabled /usr/local/share/libdrm/amdgpu.ids: No such file or directory /usr/local/share/libdrm/amdgpu.ids: No such file or directory Peer device is not opened or has ASIC not supported by the suite, skip all Peer to Peer tests. CUnit - A unit testing framework for C - Version 2.1-3 <a class="moz-txt-link-freetext" href="http://cunit.sourceforge.net/">http://cunit.sourceforge.net/</a> Suite: Hotunplug Tests Test: Unplug card and rescan the bus to plug it back .../usr/local/share/libdrm/amdgpu.ids: No such file or directory passed Test: Same as first test but with command submission .../usr/local/share/libdrm/amdgpu.ids: No such file or directory passed Test: Unplug with exported bo .../usr/local/share/libdrm/amdgpu.ids: No such file or directory passed Run Summary: Type Total Ran Passed Failed Inactive suites 14 1 n/a 0 0 tests 71 3 3 0 1 asserts 21 21 21 0 n/a Elapsed time = 9.195 seconds Andrey <div class="moz-cite-prefix">On 2022-04-20 11:44, Andrey Grodzovsky wrote: </div> <blockquote type="cite" cite="mid:34789d77-b8ee-1e4f-c5c2-f32f42f923dc@amd.com"> The only one in Radeon 7 I see is the same sysfs crash we already fixed so you can use the same fix. The MI 200 issue i haven't seen yet but I also haven't tested MI200 so never saw it before. Need to test when i get the time. So try that fix with Radeon 7 again to see if you pass the tests (the warnings should all be minor issues). Andrey <div class="moz-cite-prefix">On 2022-04-20 05:24, Shuotao Xu wrote: </div> <blockquote type="cite" cite="mid:549246A3-B326-47CC-92FD-608708E1876B@microsoft.com"> <div> <blockquote type="cite" class=""> <div class=""> <div class=""> That a problem, latest working baseline I tested and confirmed passing hotplug tests is this branch and commit <a class="moz-txt-link-freetext" href="https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fagd5f%2Flinux%2F-%2Fcommit%2F86e12a53b73135806e101142e72f3f1c0e6fa8e6&data=05%7C01%7Candrey.grodzovsky%40amd.com%7C39356160279b44accbe208da22af9c6d%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637860435039102940%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Lz7qOj8b%2BQ%2BI8XmC016E7M%2B7c7v6WHlRsMaynDUAL0o%3D&reserved=0" originalsrc="https://gitlab.freedesktop.org/agd5f/linux/-/commit/86e12a53b73135806e101142e72f3f1c0e6fa8e6" shash="aQsDnBBx+4wVN7dIUr4Ib91c16nNH4kHfx1IPv2d+8MyW5GFeo2j0+YcklqfAtyO82rJfGn0Sz11kc4IrTFF7Kb8E+okwybryejcAdvHmEzKeIspr9c5HDusNm/aejWGuhgbkBJD1eJrwEdZewgbPcvOh9jw4UV5jNl9d+7uNj8=" moz-do-not-send="true"> https://gitlab.freedesktop.org/agd5f/linux/-/commit/86e12a53b73135806e101142e72f3f1c0e6fa8e6</a> which is amd-staging-drm-next. 5.14 was the branch we ups-reamed the hotplug code but it had a lot of regressions over time due to new changes (that why I added the hotplug test to try and catch them early). It would be best to run this branch on mi-100 so we have a clean baseline and only after confirming this particular branch from this commits passes libdrm tests only then start adding the KFD specific addons. Another option if you can't work with MI-100 and this branch is to try a different ASIC that does work with this branch (if possible). Andrey </div> </div> </blockquote> OK I tried both this commit and the HEAD of and-staging-drm-next on two GPUs( MI100 and Radeon VII) both did not pass hotplugout libdrm test. I might be able to gain access to MI200, but I suspect it would work. </div> <div> </div> <div>I copied the complete dmesgs as follows. I highlighted the OOPSES for you.</div> <div> </div> <div>Radeon VII:</div> </blockquote> </blockquote> </body> </html>