From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206895] [amdgpu] crash while using opencl from amdgpu-pro on kernel 5.5.10
Date: Mon, 23 Mar 2020 00:38:58 +0000 [thread overview]
Message-ID: <bug-206895-2300-hxOZ2BnDyb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206895-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206895
--- Comment #8 from bigbeeshane@gmail.com ---
After some further validation
5.6-rc6 also has this bug
Reverting be62dbf554c5b50718a54a359372c148cd9975c7 fixes the issue but overall
it seems that amdgpu is not using the new implementation of dma_map_sg
correctly.
Looking at the documentation (here :
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/Documentation/DMA-API.txt?h=v5.5.11#n354)
it seems like return value of dma_map_sg and the supplied value for nents can
differ in length.
Currently the amdgpu driver code validates that the return value of dma_map_sg
and nents are equal, otherwise bailing out of amdgpu_ttm_tt_pin_userptr see
line :
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c?h=v5.5.11#n976
This would explain the "*ERROR* failed to pin userptr" message followed by the
trace.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-03-23 0:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 19:55 [Bug 206895] New: [amdgpu] crash while using opencl from amdgpu-pro on kernel 5.5.10 bugzilla-daemon
2020-03-20 20:32 ` [Bug 206895] " bugzilla-daemon
2020-03-20 20:41 ` bugzilla-daemon
2020-03-21 14:52 ` bugzilla-daemon
2020-03-21 23:09 ` bugzilla-daemon
2020-03-22 10:35 ` bugzilla-daemon
2020-03-22 23:45 ` bugzilla-daemon
2020-03-22 23:47 ` bugzilla-daemon
2020-03-23 0:38 ` bugzilla-daemon [this message]
2020-03-23 12:44 ` bugzilla-daemon
2020-03-23 12:46 ` [Bug 206895] [amdgpu] crash while using opencl from amdgpu-pro on kernel 5.5.10 & 5.6.0-rc6 bugzilla-daemon
2020-03-23 13:57 ` bugzilla-daemon
2020-03-23 15:59 ` bugzilla-daemon
2020-03-23 16:01 ` bugzilla-daemon
2020-03-23 16:11 ` bugzilla-daemon
2020-03-23 16:16 ` bugzilla-daemon
2020-03-23 16:18 ` bugzilla-daemon
2020-03-23 17:01 ` 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-206895-2300-hxOZ2BnDyb@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.