From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109808] ROCm OpenCL segfaults on drm-next-5.1-wip
Date: Fri, 01 Mar 2019 21:19:15 +0000 [thread overview]
Message-ID: <bug-109808-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1020 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109808
Bug ID: 109808
Summary: ROCm OpenCL segfaults on drm-next-5.1-wip
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: bmilreu@gmail.com
rocm clinfo segfaults with this on dmesg:
mar 01 15:27:36 mjb kernel: kfd2kgd: init_user_pages: Failed to register MMU
notifier: -19
Reverting:
drm/amdgpu: use HMM callback to replace mmu notifier
drm/amdgpu: replace get_user_pages with HMM mirror helpers
drm/amdkfd: avoid HMM change cause circular lock
drm/amdgpu: use HMM callback to replace mmu notifier
makes it work again, something might be wrong with those related commits.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2309 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-03-01 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 21:19 bugzilla-daemon [this message]
2019-03-03 18:39 ` [Bug 109808] ROCm OpenCL segfaults on drm-next-5.1-wip bugzilla-daemon
2019-03-03 20:36 ` bugzilla-daemon
2019-03-04 9:00 ` Mihai
2019-03-04 9:01 ` bugzilla-daemon
2019-03-04 15:30 ` 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-109808-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.