Comment 11 for bug 562145

currently i cannot try what you suggested but i can provide some informations from some previous testing.

i found out that with the latest ubuntu kernel (i guess) 2.6.32.22 (right?) this issue is still active. but using kernels 2.6.33 or above (including latest kernel.org upstream kernel) the issue has gone.
so this problem only occures with the 2.6.32 kernels.

i cannot say when i have the time to test it with the suggested methods to give you more information. currently i got too much to do.