Comment 20 for bug 1167019

Do you still get this issue if you run a 3.2 kernel on Raring, like mentioned in comment #15? If so, it might be a good test to try the Raring kernel on a Precise install. Do you have the option of putting Precise on this machine to perform this test? I would expect the bug to happen in this case if the bug is kernel related. If it does't, it could suggest an issue in another package, such as network-manager.