I tried linux-image-4.4.0-38-generic package (version 4.4.0-38.57) from xenial-proposed and can't reproduce this bug on it, looks like it is fixed in proposed version.
Thanks for the help, this issue should be resolved when linux-image-4.4.0-38-generic will reach xenial-updates channel.
Tim, thank you for the quick response!
I tried linux-image- 4.4.0-38- generic package (version 4.4.0-38.57) from xenial-proposed and can't reproduce this bug on it, looks like it is fixed in proposed version.
Thanks for the help, this issue should be resolved when linux-image- 4.4.0-38- generic will reach xenial-updates channel.