From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 102666] amdgpu_vm_bo_invalidate NULL reference in amd-staging-drm-next Date: Mon, 11 Sep 2017 22:22:57 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0059551864==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 2D6616E542 for ; Mon, 11 Sep 2017 22:22:57 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0059551864== Content-Type: multipart/alternative; boundary="15051685770.6daBE.30374"; charset="UTF-8" --15051685770.6daBE.30374 Date: Mon, 11 Sep 2017 22:22:57 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D102666 Bug ID: 102666 Summary: amdgpu_vm_bo_invalidate NULL reference in amd-staging-drm-next Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: bas@basnieuwenhuizen.nl Created attachment 134171 --> https://bugs.freedesktop.org/attachment.cgi?id=3D134171&action=3Dedit dmesg I'm getting a=20 [ 404.518419] BUG: unable to handle kernel NULL pointer dereference at 0000000000000220 [ 404.518445] IP: amdgpu_vm_bo_invalidate+0x71/0x150 [amdgpu] when running vulkan cts with 32 processes (with tests that cause OOM remove= d). Current linux tip: commit 2dd9dc59c1419c090b084461165bd8b0adf1fecb (HEAD -> amd-staging-drm-ne= xt, origin/amd-staging-drm-next) Author: Harry Wentland Date: Thu Aug 31 21:17:05 2017 -0400 drm/amdgpu: Remove unused flip_flags from amdgpu_crtc It doesn't seem like there is a correlating hang: the card is clocked down = and /sys/kernel/debug/dri/0/amdgpu_fence_info shows no pending fences. However, eventually some of the CTS processes get stuck, and I can't kill them gdb i= nto them etc. Probably a pagefault that gets stuck, since fence waiting doesn't seem to get stuck easily? Either way, not sure if that is related yet. AFAICT the issue is that vm->root.base.bo is NULL in if (evicted && bo->tbo.resv =3D=3D vm->root.base.bo->tbo.resv) { --=20 You are receiving this mail because: You are the assignee for the bug.= --15051685770.6daBE.30374 Date: Mon, 11 Sep 2017 22:22:57 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
Bug ID 102666
Summary amdgpu_vm_bo_invalidate NULL reference in amd-staging-drm-next
Product DRI
Version DRI git
Hardware Other
OS All
Status NEW
Severity normal
Priority medium
Component DRM/AMDgpu
Assignee dri-devel@lists.freedesktop.org
Reporter bas@basnieuwenhuizen.nl 

Created attachment 134171 [details]<=
/span>
dmesg

I'm getting a=20

[  404.518419] BUG: unable to handle kernel NULL pointer dereference at
0000000000000220
[  404.518445] IP: amdgpu_vm_bo_invalidate+0x71/0x150 [amdgpu]


when running vulkan cts with 32 processes (with tests that cause OOM remove=
d).

Current linux tip:

commit 2dd9dc59c1419c090b084461165bd8b0adf1fecb (HEAD -> amd-staging-drm=
-next,
origin/amd-staging-drm-next)
Author: Harry Wentland <ha=
rry.wentland@amd.com>
Date:   Thu Aug 31 21:17:05 2017 -0400

    drm/amdgpu: Remove unused flip_flags from amdgpu_crtc


It doesn't seem like there is a correlating hang: the card is clocked down =
and
/sys/kernel/debug/dri/0/amdgpu_fence_info shows no pending fences. However,
eventually some of the CTS processes get stuck, and I can't kill them gdb i=
nto
them etc. Probably a pagefault that gets stuck, since fence waiting doesn't
seem to get stuck easily? Either way, not sure if that is related yet.

AFAICT the issue is that vm->root.base.bo is NULL in

if (evicted && bo->tbo.resv =3D=3D vm->root.base.bo->tbo.r=
esv) {

You are receiving this mail because:
  • You are the assignee for the bug.
= --15051685770.6daBE.30374-- --===============0059551864== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0059551864==--