WARNING at amdgpu_vm_sdma.c:85

[Christian König]

Mhm, that is actually harmless. We somehow end up trying to submit a 
zero sized IB.

Going to double check tomorrow how this can happen.

Is the anything bad happening when you just remove the warning?

Christian.

Am 26.03.19 um 18:30 schrieb Michel Dänzer:
> On 2019-03-26 4:21 p.m., Michel Dänzer wrote:
>> I'm hitting some badness with piglit today, see the attached dmesg
>> excerpt. I was away for a couple of days, but looks like it might be
>> related to the VM changes? I'll try bisecting.
> Bisected to:
>
> 602b5050d839c40572bbb19e9b17a37a150c1e3c is the first bad commit
> commit 602b5050d839c40572bbb19e9b17a37a150c1e3c
> Author: Christian König <christian.koenig at amd.com>
> Date:   Mon Mar 18 14:26:24 2019 +0100
>
>      drm/amdgpu: use the new VM backend for PDEs
>
>      And remove the existing code when it is unused.
>
>      Signed-off-by: Christian König <christian.koenig at amd.com>
>      Reviewed-by: Chunming Zhou <david1.zhou at amd.com>
>      Reviewed-by: Felix Kuehling <Felix.Kuehling at amd.com>
>
>
> The problem doesn't happen with this commit and the corresponding PTE
> one reverted on current amd-staging-drm-next.
>
>