search for: gf100_gr_trap_mp

Displaying 2 results from an estimated 2 matches for "gf100_gr_trap_mp".

2015 May 18
2
Tessellation shaders get MEM_OUT_OF_BOUNDS errors / missing triangles
...-- 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 this: TRAP ch 5 [0x003facf000 shader_runner[19044]] I would imagine that's some floating point number ending up in the register instead of an address, but the fp32 value of it (1.351...
2015 May 26
2
Tessellation shaders get MEM_OUT_OF_BOUNDS errors / missing triangles
...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 this: TRAP ch 5 [0x003facf000 shader_runner[19044]] >> >> I would imagine that's some floating point number ending up in the >> register in...