The lkml tread you referenced in the bug description was for commit 37b12910dd11d9ab969f2c310dc9160b7f3e3405. That commit landed upstream in v4.3.rc1, so it is already in the 4.4 based Xenial kernel.
Did this issue start happening after a recent upgrade, or after applying updates?
The lkml tread you referenced in the bug description was for commit 37b12910dd11d9a b969f2c310dc916 0b7f3e3405. That commit landed upstream in v4.3.rc1, so it is already in the 4.4 based Xenial kernel.
Did this issue start happening after a recent upgrade, or after applying updates?