2.6.33 doesn't support vblank events, so you wouldn't be able to run the code that exposes this problem. I'm sure the interrupt issue still exists on 2.6.33 though, you just don't see it because you're not running code that's sensitive to interrupt latency.
2.6.33 doesn't support vblank events, so you wouldn't be able to run the code that exposes this problem. I'm sure the interrupt issue still exists on 2.6.33 though, you just don't see it because you're not running code that's sensitive to interrupt latency.