From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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 [thread overview]
Message-ID: <bug-102666-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1745 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102666
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=134171&action=edit
dmesg
I'm getting a
[ 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 removed).
Current linux tip:
commit 2dd9dc59c1419c090b084461165bd8b0adf1fecb (HEAD -> amd-staging-drm-next,
origin/amd-staging-drm-next)
Author: Harry Wentland <harry.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 into
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 == vm->root.base.bo->tbo.resv) {
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3217 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-09-11 22:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 22:22 bugzilla-daemon [this message]
2017-09-11 22:23 ` [Bug 102666] amdgpu_vm_bo_invalidate NULL reference in amd-staging-drm-next bugzilla-daemon
2018-06-20 22:41 ` bugzilla-daemon
2018-06-21 9:24 ` bugzilla-daemon
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=bug-102666-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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