search for: shader_runn

Hi Christoph, bin/shader_runner tests/spec/glsl-1.40/uniform_buffer/fs-struct-copy-complicated.shader_test -auto bin/shader_runner tests/spec/glsl-1.40/uniform_buffer/vs-struct-copy-complicated.shader_test -auto bin/shader_runner tests/spec/glsl-1.50/uniform_buffer/gs-struct-copy-complicated.shader_test -auto Now all segfault....

Tested with: MESA_EXTENSION_OVERRIDE=GL_ARB_gpu_shader5 ./shader_runner ../tests/spec/arb_gpu_shader5/execution/built-in-functions/fs-bitfieldReverse.shader_test -> green output, so this should be ok the test was not change though... On 29.05.2014 21:47, Ilia Mirkin wrote: > Can you verify that you tested how the HW handles this, as well as > exactly ho...

...his 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.35107421875) does not seem familiar. Even when all the triangles show up, I still see the error on the GK208, so I'm not sure if they're the same is...

...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.35107421875) does not seem familiar. > > Ben pointed out that the 0x3facf000 is a channel address, not a value >...

...shaders (well, related to textures), and there are plenty of other texture2D-using tests. I looked at the mmt traces, and they seem pretty reasonable. What's unique about this test is that it uses a 0.01 value in the texture rather than the more common 1/-1. FWIW the failure looks like: $ bin/shader_runner tests/shaders/glsl-fs-lots-of-tex.shader_test -auto Probe color at (187,187) Expected: 0.400000 0.000000 0.000000 Observed: 0.266667 0.000000 0.000000 PIGLIT: {'result': 'fail' } So it's getting a value... just not the right one. The blit is being done from RGBA32_FLOAT t...

Signed-off-by: Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> --- src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp b/src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp index 58092f4..93f7c2a 100644 ---

...bounds-06 glsl-array-bounds-08 print out success but get a kernel log entry like [ 4653.971680] nouveau E[ PGRAPH][0000:02:00.0] TRAP_MP - TP0: Unhandled ustatus 0x00000001 [ 4653.971688] nouveau E[ PGRAPH][0000:02:00.0] TRAP [ 4653.971695] nouveau E[ PGRAPH][0000:02:00.0] ch 5 [0x0007814000 shader_runner[8809]] subc 3 class 0x8397 mthd 0x15e0 data 0x00000000 found with heavy use of exclude -x feature :) Hardware: Nvidia 8200 Onboard NVAA/NV50 nouveau [ DEVICE][0000:02:00.0] Chipset: MCP77/MCP78 (NVAA) nouveau [ DEVICE][0000:02:00.0] Family : NV50 Software: Linux Mint 15 + xorg-edgers + 3....

https://bugs.freedesktop.org/show_bug.cgi?id=68344 Priority: medium Bug ID: 68344 Assignee: nouveau at lists.freedesktop.org Summary: [piglit] shaders/glsl-fs-texture2d-dependent-4 randomly passes or fails on NVAA/NV50 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified