Comment 18 for bug 1640200

This issue has been around my stock Ubuntu installation at least since 15.04 and continues to persist after the upgrade to 16.10. I have tried all the workarounds of #1464917 without success.

I have my doubts that the kernel upgrade as suggested by Joseph will remedy the situation but will give it a try and report back.

Given the severity of this and the old issue especially in production environments, it would be great if we can bump up the importance.