From: Przemek Socha <soprwa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Koenig,
Christian" <Christian.Koenig-5C7GfCeVMHo@public.gmane.org>,
Tom St Denis <tom.stdenis-5C7GfCeVMHo@public.gmane.org>
Cc: "Zhou,
David(ChunMing)" <David1.Zhou-5C7GfCeVMHo@public.gmane.org>,
"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: amd-staging-drm-next: Oops - BUG: unable to handle kernel NULL pointer dereference, bisected.
Date: Thu, 31 Jan 2019 10:23:49 +0100 [thread overview]
Message-ID: <3492051.hfQoeLTAnN@eclipse> (raw)
In-Reply-To: <7a65412b-1b41-9e5b-f700-0a944a33cf49-5C7GfCeVMHo@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1463 bytes --]
Dnia środa, 30 stycznia 2019 13:42:33 CET piszesz:
> Does the attached patch fix the issue?
>
> Christian.
I have tested this one also - "drm/amdgpu: partial revert cleanup setting
bulk_movable v2"
>We still need to set bulk_movable to false when new BOs are added or removed.
>
>v2: also set it to false on removal
>
>Signed-off-by: Christian König <christian.koenig-5C7GfCeVMHo@public.gmane.org>
>---
> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
>diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/
>amdgpu/amdgpu_vm.c
>index 79f9dde70bc0..822546a149fa 100644
>--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
>+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
>@@ -332,6 +332,7 @@ static void amdgpu_vm_bo_base_init(struct
>amdgpu_vm_bo_base *base,
> if (bo->tbo.resv != vm->root.base.bo->tbo.resv)
> return;
>
>+ vm->bulk_moveable = false;
> if (bo->tbo.type == ttm_bo_type_kernel)
> amdgpu_vm_bo_relocated(base);
> else
>@@ -2772,6 +2773,9 @@ void amdgpu_vm_bo_rmv(struct amdgpu_device *adev,
> struct amdgpu_vm_bo_base **base;
>
> if (bo) {
>+ if (bo->tbo.resv == vm->root.base.bo->tbo.resv)
>+ vm->bulk_moveable = false;
>+
> for (base = &bo_va->base.bo->vm_bo; *base;
> base = &(*base)->next) {
> if (*base != &bo_va->base)
and so far I have no lockup and Oops, so I think this one is ok.
Thank you very much,
Przemek.
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2019-01-31 9:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 11:07 amd-staging-drm-next: Oops - BUG: unable to handle kernel NULL pointer dereference, bisected Przemek Socha
2019-01-30 12:02 ` Christian König
[not found] ` <2c13e24c-6d53-a7f5-55ed-d44d7c58f655-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-01-30 12:06 ` Koenig, Christian
[not found] ` <34e7e9b9-8d16-1055-cd08-68eac497743e-5C7GfCeVMHo@public.gmane.org>
2019-01-30 12:42 ` Koenig, Christian
[not found] ` <7a65412b-1b41-9e5b-f700-0a944a33cf49-5C7GfCeVMHo@public.gmane.org>
2019-01-30 14:17 ` Przemek Socha
2019-01-30 14:37 ` StDenis, Tom
2019-01-31 9:23 ` Przemek Socha [this message]
2019-01-31 16:56 ` StDenis, Tom
[not found] ` <676b4805-fc73-245f-abd2-38e014248b61-5C7GfCeVMHo@public.gmane.org>
2019-01-31 17:31 ` Przemek Socha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3492051.hfQoeLTAnN@eclipse \
--to=soprwa-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=Christian.Koenig-5C7GfCeVMHo@public.gmane.org \
--cc=David1.Zhou-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=tom.stdenis-5C7GfCeVMHo@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox