I can also confirm that this bug is not reproducible on 2.6.28 and 2.6.29-rc1 vanilla kernels.
It means that this problem occured because of Ubuntu kernel patches and that's why Theodore was not able to reproduce it on his Intrepid machine with updated vanilla kernels.
I can also confirm that this bug is not reproducible on 2.6.28 and 2.6.29-rc1 vanilla kernels.
It means that this problem occured because of Ubuntu kernel patches and that's why Theodore was not able to reproduce it on his Intrepid machine with updated vanilla kernels.