The Xenial kernel is now at 4.4.0-64.85. Can you apply the latest updates and see if the bug still exists?
The Xenial kernel is now at 4.4.0-64.85. Can you apply the latest updates and see if the bug still exists?