https://bugs.freedesktop.org/show_bug.cgi?id=102500
--- Comment #17 from Dieter Nützel Dieter@nuetzel-hh.de --- (In reply to Christian König from comment #15)
Created attachment 134082 [details] [review] Possible fix
Please try the attached kernel patch.
Hello Christian,
you've made your 'homework'...;-)
To repeat my question: Does patch "drm/amdgpu: fix moved list handling in the VM" fix the issue?
Do you guys have this in your kernel branch yet? If not that lockup is expected.
No, I haven't. It was fallen into the cranks of the repeated DC rebase of Alex's 'amd-staging-drm-next' tree (didn't noticed it for the last 7 days, Alex vacation). I'll make it short. NO that didn't solve it for me, too.
But _this_ patch is GOLD: drm-amdgpu-fix-VM-sync-with-always-valid-BOs.mbox
Tested-by: Dieter Nützel Dieter@nuetzel-hh.de
Best 'glmark2' Score I've ever seen. RX580, 8 GB Xeon X3470, 4/8, 3 GHz 24 GB
glmark2 Score: 6428
with additional load on the gfx cores through parallel running 'opencl-example/run_tests.sh' I got
glmark2 Score: 7574
Good job!