There were a couple of kernel fixes for problems matching your description applied to the 2.6.32-18 and 2.6.32-19 kernels. Can you re-test with the current 2.6.32-19 kernel to check whether this problem has been fixed? Thanks.
There were a couple of kernel fixes for problems matching your description applied to the 2.6.32-18 and 2.6.32-19 kernels. Can you re-test with the current 2.6.32-19 kernel to check whether this problem has been fixed? Thanks.