This may be a duplicate of bug 1741934, which was fixed in the 4.4.0-109 kernel. Can you upgrade to the 4.4.0-109 kernel and see if this bug still exists?
This may be a duplicate of bug 1741934, which was fixed in the 4.4.0-109 kernel. Can you upgrade to the 4.4.0-109 kernel and see if this bug still exists?