That's curious because I had the problem with both 3.5.0 (current Ubuntu kernel when I filed the bug) and 3.7.0 (latest upstream kernel when I filed the bug).
But it used to work better between december 2012 and april 2013 (when I upgraded to Ubuntu 13.04 and kernel 3.8).
So maybe a few 3.6.* versions are free from this problem.
That's curious because I had the problem with both 3.5.0 (current Ubuntu kernel when I filed the bug) and 3.7.0 (latest upstream kernel when I filed the bug).
But it used to work better between december 2012 and april 2013 (when I upgraded to Ubuntu 13.04 and kernel 3.8).
So maybe a few 3.6.* versions are free from this problem.