Displaying 12 results from an estimated 12 matches for "mem_out_of_bounds".
2014 Jul 03
0
[Bug 80865] [NVE7] Hard hang (GPC0/TPC0/MP trap: MULTIPLE_WARP_ERRORS MEM_OUT_OF_BOUNDS)
...t; changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Hard hang (GPC0/TPC0/MP |[NVE7] Hard hang
|trap: MULTIPLE_WARP_ERRORS |(GPC0/TPC0/MP trap:
|MEM_OUT_OF_BOUNDS) |MULTIPLE_WARP_ERRORS
| |MEM_OUT_OF_BOUNDS)
--- Comment #5 from Ilia Mirkin <imirkin at alum.mit.edu> ---
Those errors are most likely to happen when e.g. you're accessing a UBO out of
its bounds. Or if the driver messed up binding...
2019 Dec 04
0
[Bug 80865] [NVE7] Hard hang (GPC0/TPC0/MP trap: MULTIPLE_WARP_ERRORS MEM_OUT_OF_BOUNDS)
https://bugs.freedesktop.org/show_bug.cgi?id=80865
Martin Peres <martin.peres at free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |MOVED
--- Comment #8 from Martin Peres
2014 Jul 03
0
[Bug 80865] Hard hang (GPC0/TPC0/MP trap: MULTIPLE_WARP_ERRORS MEM_OUT_OF_BOUNDS)
https://bugs.freedesktop.org/show_bug.cgi?id=80865
Aaron Plattner <aplattner at nvidia.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|aplattner at nvidia.com |nouveau at lists.freedesktop.o
| |rg
2014 Jul 07
0
[Bug 80865] [NVE7] Hard hang (GPC0/TPC0/MP trap: MULTIPLE_WARP_ERRORS MEM_OUT_OF_BOUNDS)
https://bugs.freedesktop.org/show_bug.cgi?id=80865
--- Comment #6 from tethys at gmail.com ---
localhost:~# rpm -qa | fgrep mesa
mesa-libGL-10.1.5-1.20140607.fc20.i686
mesa-libglapi-10.1.5-1.20140607.fc20.x86_64
mesa-filesystem-10.1.5-1.20140607.fc20.x86_64
mesa-libglapi-10.1.5-1.20140607.fc20.i686
mesa-libGLU-9.0.0-5.fc20.x86_64
mesa-libgbm-10.1.5-1.20140607.fc20.x86_64
2015 May 18
2
Tessellation shaders get MEM_OUT_OF_BOUNDS errors / missing triangles
...n my GF108, but
it's exceedingly rare, if it does happen. I don't have a GK10x to test
on, unfortunately, but I assume it'll have the same issue as the
GK208.
The issue is this -- a bunch of triangles that should come out of the
tessellator end up black. I also see a GPC0/TPC1/MP trap:
MEM_OUT_OF_BOUNDS error produced by nouveau -- this is output in
response to a interrupt and MP trap generated by the hardware, read
out with nv_rd32(priv, TPC_UNIT(gpc, tpc, 0x648)); (see
gf100_gr_trap_mp). I assume some of the tessellation evaluation
invocations get killed, but I have no proof of this.
I also see...
2015 May 26
2
Tessellation shaders get MEM_OUT_OF_BOUNDS errors / missing triangles
...happen. I don't have a GK10x to test
>> on, unfortunately, but I assume it'll have the same issue as the
>> GK208.
>>
>> The issue is this -- a bunch of triangles that should come out of the
>> tessellator end up black. I also see a GPC0/TPC1/MP trap:
>> MEM_OUT_OF_BOUNDS error produced by nouveau -- this is output in
>> response to a interrupt and MP trap generated by the hardware, read
>> out with nv_rd32(priv, TPC_UNIT(gpc, tpc, 0x648)); (see
>> gf100_gr_trap_mp). I assume some of the tessellation evaluation
>> invocations get killed, but...
2015 Sep 30
2
Documentation request for MP warp error 0x10
...ue="5" name="MISALIGNED_PC"/>
<value value="8" name="MISALIGNED_GPR"/>
<value value="9" name="INVALID_OPCODE"/>
<value value="13" name="GPR_OUT_OF_BOUNDS"/>
<value value="14" name="MEM_OUT_OF_BOUNDS"/>
<value value="17" name="INVALID_PARAM"/>
</bitfield>
</reg32>
[Additionally it seems like 15 = UNALIGNED_MEM_ACCESS]
It seems to happen whenever I try to access global memory on kepler
(potentially only atomics, not sure at this point). Knowing pre...
2015 Oct 02
2
Documentation request for MP warp error 0x10
...ED_PC"/>
>> <value value="8" name="MISALIGNED_GPR"/>
>> <value value="9" name="INVALID_OPCODE"/>
>> <value value="13" name="GPR_OUT_OF_BOUNDS"/>
>> <value value="14" name="MEM_OUT_OF_BOUNDS"/>
>> <value value="17" name="INVALID_PARAM"/>
>> </bitfield>
>> </reg32>
>>
>> [Additionally it seems like 15 = UNALIGNED_MEM_ACCESS]
>>
>> It seems to happen whenever I try to access global memory on kepler
&g...
2015 Dec 04
1
NV50 compute support questions
...nouveaufb frame buffer device
[ 4.141094] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
<snip>
[ 1713.421460] nouveau 0000:01:00.0: gr: TRAP ch 6 [003fa32000 compute[21117]]
[ 1713.421471] nouveau 0000:01:00.0: gr: GPC0/TPC1/MP trap: global 00000000 [] warp 3000e [MEM_OUT_OF_BOUNDS]
[ 1713.441248] nouveau 0000:01:00.0: gr: TRAP ch 6 [003fa32000 compute[21117]]
[ 1713.441260] nouveau 0000:01:00.0: gr: GPC0/TPC0/MP trap: global 00000004 [MULTIPLE_WARP_ERRORS] warp 20005 [MISALIGNED_PC]
[ 1713.441265] nouveau 0000:01:00.0: gr: GPC0/TPC1/MP trap: global 00000004 [MULTIPLE_WARP_ER...
2015 Oct 07
1
[PATCH 1/2] gr: document mp error 0x10
...gine/gr/gf100.c b/drm/nouveau/nvkm/engine/gr/gf100.c
index f1358a5..dda7a7d 100644
--- a/drm/nouveau/nvkm/engine/gr/gf100.c
+++ b/drm/nouveau/nvkm/engine/gr/gf100.c
@@ -882,6 +882,7 @@ static const struct nvkm_enum gf100_mp_warp_error[] = {
{ 0x0d, "GPR_OUT_OF_BOUNDS" },
{ 0x0e, "MEM_OUT_OF_BOUNDS" },
{ 0x0f, "UNALIGNED_MEM_ACCESS" },
+ { 0x10, "INVALID_ADDR_SPACE" },
{ 0x11, "INVALID_PARAM" },
{}
};
--
2.4.9
2015 Oct 02
0
Documentation request for MP warp error 0x10
...; >> <value value="8" name="MISALIGNED_GPR"/>
> >> <value value="9" name="INVALID_OPCODE"/>
> >> <value value="13" name="GPR_OUT_OF_BOUNDS"/>
> >> <value value="14" name="MEM_OUT_OF_BOUNDS"/>
> >> <value value="17" name="INVALID_PARAM"/>
> >> </bitfield>
> >> </reg32>
> >>
> >> [Additionally it seems like 15 = UNALIGNED_MEM_ACCESS]
> >>
> >> It seems to happen whenever I try t...
2015 Dec 04
4
NV50 compute support questions
Hi,
On 02-12-15 19:33, Samuel Pitoiset wrote:
>
>
> On 12/02/2015 04:34 PM, Hans de Goede wrote:
>> On 01-12-15, Samuel Pitoiset wrote:
>>
>> >>> Ok, here is a MMT trace of vectorAdd:
>> >>>
>> >>> https://fedorapeople.org/~jwrdegoede/vectorAdd.log.gz
>> >>
>> >> Hi Hans,
>> >>
>>