https://bugs.freedesktop.org/show_bug.cgi?id=100567
--- Comment #10 from Géza Búza ---
It must be a driver bug, as I see the same error on different kernel and
different graphic hardware.
dmesg output:
nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
nouveau :01:00.0: fifo: runli
Printing without this could lead to the following output, while the values are
not exactly zero:
IMM[5] FLT32 {0., 0., 0., 0.}
IMM[6] FLT32 {0., 0., 0., 0.}
IMM[7] FLT32 {0., 0., 0., 0.}
when printing t
This comes in handy when checking "NV50_PROG_DEBUG=1" outputs with diff!
Signed-off-by: Tobias Klausmann
---
src/gallium/drivers/nouveau/codegen/nv50_ir.cpp| 6 +++---
src/gallium/drivers/nouveau/codegen/nv50_ir.h | 2 +-
src/gallium/drivers/nouveau/codegen/nv50_ir_driver.h
I think it is better to put this behind an environmental variable,
because that way it can also be used without having to dump the TGSI
first and I don't see a good reason why not to.
On Tue, Nov 14, 2017 at 4:01 PM, Tobias Klausmann
wrote:
> This comes in handy when checking "NV50_PROG_DEBUG=1"
Hi Martin,
This is just a quick ACK. I've started an internal email thread and
we'll see if we can get back to you soon.
Yes, our thermal and fan control definitely changes a lot which
the various chip architectures. I'm continually impressed by how much
the SW+HW has been able to improve perform
