Oh I almost forgot. I removed the funky "(elapsed >= 3000)" conditional
which funnily did not mean a hardlock. I don't understand what it was meant
to be and what it was for. Any idea?
Marek
On Sun, Sep 12, 2010 at 5:09 AM, Marek Ol??k wrote:
> One subtest of mesa/demos/gltestperf takes 9
One subtest of mesa/demos/gltestperf takes 9 seconds to complete,
so to prevent an unnecessary gpu reset followed by a hardlock, I am
increasing the interval to 10 seconds after which a GPU is considered
in a locked-up state. This is on RV530. However, with a little slower GPU,
we would surpass
One subtest of mesa/demos/gltestperf takes 9 seconds to complete,
so to prevent an unnecessary gpu reset followed by a hardlock, I am
increasing the interval to 10 seconds after which a GPU is considered
in a locked-up state. This is on RV530. However, with a little slower GPU,
we would surpass
Oh I almost forgot. I removed the funky (elapsed = 3000) conditional
which funnily did not mean a hardlock. I don't understand what it was meant
to be and what it was for. Any idea?
Marek
On Sun, Sep 12, 2010 at 5:09 AM, Marek Olšák mar...@gmail.com wrote:
One subtest of mesa/demos/gltestperf