Further on this.. actually tcl looks to be involved as well, I found
another bug unrelated to the vblank_mode in a certain screen of my
application, entering the screen and leaving it twice in a row, causes a
chip lockup, disabling TCL makes it go away
so does anyone know offhand from
I have an application that has been running for 2-3 days no worries
with vblank_mode=0, but of course chews CPU and tears the screen, I
recently started running it with vblank_mode=2 or 3 and it hangs
in the glXSwapBuffers after a few hours, it looks like it is repeatedly
calling the
On Tue, 2005-01-18 at 08:28 +, Dave Airlie wrote:
I have an application that has been running for 2-3 days no worries
with vblank_mode=0, but of course chews CPU and tears the screen, I
recently started running it with vblank_mode=2 or 3 and it hangs
in the glXSwapBuffers after a
Have you ruled out simple logic bugs causing a spurious failure?
well I'm doing a code review of the code over the next while also, I do
wonder is thers some amount of interrupts that I'm failing after or if
there is maybe some small race in the interrupt handling.., so
consistency tests are
On Mon, 2004-11-22 at 22:26 +, Dave Airlie wrote:
Hi all,
I'm just wondering how much testing anyone has done on the Radeon
M7/7500 and vblanks,
IIRC that was what I had when I originally wrote the wait for vblank
code, but it's changed a lot since then.
I have an application that
Have you tried adding some debugging output to find out why that is?
that'll be my next trick, finding the exact place to put the debugging is
the tricky bit, else it produces a lot of info.. I think I can attach a
debugger after the fact, I'll start digging around the sarea for what the
Hi all,
I'm just wondering how much testing anyone has done on the Radeon
M7/7500 and vblanks, I have an application that has been running for 2-3
days no worries with vblank_mode=0, but of course chews CPU and tears the
screen, I recently started running it with vblank_mode=2 or 3 and it
