I found a way to trigger the issue with 4.4.0-113.136 and am glad to report that the -proposed kernel 4.4.0-116.140 fixes the issue, thanks!
I found a way to trigger the issue with 4.4.0-113.136 and am glad to report that the -proposed kernel 4.4.0-116.140 fixes the issue, thanks!