<MoeIcenowy>
the mainline th1520 support still lacks clock tree driver
cphealy_ has quit []
Emantor has quit [Ping timeout: 480 seconds]
Emantor has joined #etnaviv
cmeissl[m] has joined #etnaviv
tomeu has joined #etnaviv
<tomeu>
I'm seeing substantial flakiness after having implemented a cache in my test suite that means that jobs are submitted much faster to the NPU
<tomeu>
this flakiness increases as I increase parallelism in deqp-runner
* austriancoder
seeing also some flakiness in CI .. but had not the time yet to really have a look at it
<tomeu>
has anybody else noticed this? wonder how often people have more than one job queued in the kernel
frieder has joined #etnaviv
<tomeu>
hmm, guess that with deqp, the HW is quite idle as the tests first sw render to have something to compare the HW results with
<tomeu>
there was some thoughts on caching the deqp golden renders, but I don't know if anybody started working on that
pcercuei has joined #etnaviv
frieder has quit [Ping timeout: 480 seconds]
frieder has joined #etnaviv
frieder has quit [Ping timeout: 480 seconds]
frieder has joined #etnaviv
mvlad has joined #etnaviv
<tomeu>
ok, seems to be correlated to jobs submitted in quick succession, as it doesn't happen right after boot or after dropping the fs caches
<tomeu>
as the cache is on NFS along with the rest of the rootfs, I guess having to access the cache via the network serializes things enough to not hit the bug
<tomeu>
so "echo 3 > /proc/sys/vm/drop_caches" before running deqp-runner gives me reliable runs
<tomeu>
this is on 5.17, btw
tlwoerner_ has joined #etnaviv
tlwoerner has quit [Ping timeout: 480 seconds]
frieder has quit [Remote host closed the connection]
sravn has quit []
sravn has joined #etnaviv
mvlad has quit [Remote host closed the connection]