It looks like this issue has already been fixed and is pending in the upstream 
2.6.32-229 kernel.

Reply via email to