On 2019-03-12 3:26 p.m., Koenig, Christian wrote: > Am 12.03.19 um 14:47 schrieb Michel Dänzer: >> On 2019-02-05 6:40 p.m., Michel Dänzer wrote: >>> FWIW, I've hit this twice now today, whereas I don't remember ever >>> hitting it before (not 100% sure though). >>> >>> I reverted the remaining hunk of the "cleanup setting bulk_movable" >>> change, and it survived a piglit run. Could just be luck, though... >> I'd been running with that revert for the last month without hitting the >> problem. Today I tried without the revert, and promptly hit it again. >> Seems more than just luck. > > Mhm, and the only thing you reverted was the "cleanup setting > bulkmovable" change? Yes, specifically, the only hunk of that which hasn't been reverted yet: diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c index a45ca5d2cfe9..c25b06121e8e 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c @@ -693,6 +693,8 @@ int amdgpu_vm_validate_pt_bos(struct amdgpu_device *adev, struct amdgpu_vm *vm, struct amdgpu_vm_bo_base *bo_base, *tmp; int r = 0; + vm->bulk_moveable &= list_empty(&vm->evicted); + list_for_each_entry_safe(bo_base, tmp, &vm->evicted, vm_status) { struct amdgpu_bo *bo = bo_base->bo; -- Earthling Michel Dänzer | https://www.amd.com Libre software enthusiast | Mesa and X developer _______________________________________________ amd-gfx mailing list amd-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/amd-gfx