This bug is fixed in the mainline 3.2.12 kernel.
The Ubuntu kernel has been rebased to 3.2.12 in version 3.2.0-19.31. Can folks affected by this bug upgrade to the latest Precise kernel and report back if this bug is resolved?
This bug is fixed in the mainline 3.2.12 kernel.
The Ubuntu kernel has been rebased to 3.2.12 in version 3.2.0-19.31. Can folks affected by this bug upgrade to the latest Precise kernel and report back if this bug is resolved?