Yes, the bug was not happening with -proposed in comment #16.
On official kernel 4.4.0-31, we use below command to upgrade the newest kernel. The bug still happened. sudo apt-get update sudo apt-get dist-upgrade
Yes, the bug was not happening with -proposed in comment #16.
On official kernel 4.4.0-31, we use below command to upgrade the newest kernel. The bug still happened.
sudo apt-get update
sudo apt-get dist-upgrade