This might be related to #1773392.
On the other hand, the issue in #1773392 appears to have been introduced in more recent kernels (16.04 not affected).
This might be related to #1773392.
On the other hand, the issue in #1773392 appears to have been introduced in more recent kernels (16.04 not affected).