Am 29.05.22 um 01:52 schrieb Mike Lothian:
On Sat, 28 May 2022 at 08:44, Paneer Selvam, Arunpravin
<arunpravin.paneersel...@amd.com> wrote:
[Public]
Hi,
After investigating quite some time on this issue, found freeze problem is not
with the amdgpu part of buddy allocator patch as the patch doesn’t throw any
issues when applied separately on top of the stable base of drm-next. After
digging more into this issue, the below patch seems to be the cause of this
problem,
drm/ttm: rework bulk move handling v5
https://cgit.freedesktop.org/drm/drm/commit/?id=fee2ede155423b0f7a559050a39750b98fe9db69
when this patch applied on top of the stable (working version) of drm-next
without buddy allocator patch, we can see multiple issues listed below, each
thrown randomly at every GravityMark run, 1. general protection fault at
ttm_lru_bulk_move_tail() 2. NULL pointer deference at ttm_lru_bulk_move_tail()
3. NULL pointer deference at ttm_resource_init().
Regards,
Arun.
Thanks for tracking it down, fee2ede155423b0f7a559050a39750b98fe9db69
isn't trivial to revert
Hopefully Christian can figure it out
Arun is unfortunately running into the wrong direction with his testing.
The merge fallout from "drm/ttm: rework bulk move handling v5" is
already fixed by "drm/amdgpu: fix drm-next merge fallout", but your
problem with the buddy allocator is separate to that.
Regards,
Christian.
