Colm Buckley Sat, 24 Nov 2018 05:51:26 -0800
Per upstream; this seems to be a kernel bug which is fixed in 4.18.20. Unclear whether the fix (1e9c75fb9c47a75a9aec0cd17db5f6dc36b58e00) can be cherrypicked back to current stable / bpo kernels; investigating.
