In the meanwhile, try new kernels. I only see up to 3.8 tested. Do a bisect. There was a major driver rewrite in 3.7, but it might have been something else that causes the issue. Make sure you're running an updated DDX.
As you might imagine, none of the devs are seeing this, so you'll have to do the debugging if you want it fixed.
Messing with priority just annoys the developers.
In the meanwhile, try new kernels. I only see up to 3.8 tested. Do a bisect. There was a major driver rewrite in 3.7, but it might have been something else that causes the issue. Make sure you're running an updated DDX.
As you might imagine, none of the devs are seeing this, so you'll have to do the debugging if you want it fixed.