search for: invalid_addr_spac

NVIDIA provided the documentation for mp error 0x10, INVALID_ADDR_SPACE, which apparently happens when trying to use an atomic operation on local or shared memory (instead of global memory). Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- drm/nouveau/nvkm/engine/gr/gf100.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drm/nouveau/nvkm/engine/gr/...

Hello, I've recently come across an error reported by the GPU and would like to know what it means and especially what causes it to be triggered. Any information would be very useful: I'm seeing MP warp error 0x10 (appears in MP register 0x48). This is what we currently have in nouveau: <reg32 offset="0x048" name="TRAP_WARP_ERROR"> <!-- ctx-switched -->

...going to leave it for image support and break direct buffer accesses directly into OP_ATOM (and in NVIDIA terminology RED is just ATOM without a destination). Thanks, -ilia On Fri, Oct 2, 2015 at 5:48 PM, Robert Morell <rmorell at nvidia.com> wrote: > Hi Ilia, > > Error 0x10 is INVALID_ADDR_SPACE. It is triggered when an ATOM or RED [1] > instruction accesses local or shared memory. Global memory accesses are the > only allowed accesses for ATOM and RED instructions. > > > Note that SM30 also has this restriction that ATOM and RED should only be used > on global memory, b...

...in > NVIDIA terminology RED is just ATOM without a destination). Neat. I'll take a look at it. Thanks, Robert > Thanks, > > -ilia > > On Fri, Oct 2, 2015 at 5:48 PM, Robert Morell <rmorell at nvidia.com> wrote: > > Hi Ilia, > > > > Error 0x10 is INVALID_ADDR_SPACE. It is triggered when an ATOM or RED [1] > > instruction accesses local or shared memory. Global memory accesses are the > > only allowed accesses for ATOM and RED instructions. > > > > > > Note that SM30 also has this restriction that ATOM and RED should only be used...