Can you see if this bug still exists with the 16.04.3 release? I'm thinking it should not, since prior testing showed that 4.9 and newer kernels did not have the bug.
16.04.3 is available from: http://releases.ubuntu.com/16.04.3/
Can you see if this bug still exists with the 16.04.3 release? I'm thinking it should not, since prior testing showed that 4.9 and newer kernels did not have the bug.
16.04.3 is available from: releases. ubuntu. com/16. 04.3/
http://