In answer to your qeustion https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/3
* Yes, the problem is NOT encountered when using Kernel linux-image-4.10.0-21-generic 4.10.0-21.23.
* The problem is encountered when using 4.10.0-22-generic
In response to your request https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/4
I have tested with upstream kernel 4.10.17
linux-headers-4.10.17-041017_4.10.17-041017.201705201051_all.deb linux-headers-4.10.17-041017-generic_4.10.17-041017.201705201051_amd64.deb linux-image-4.10.17-041017-generic_4.10.17-041017.201705201051_amd64.deb
and equally encountered the problem. I therefore added the tag: 'kernel-bug-exists-upstream'.
In answer to your qeustion https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1697556/ comments/ 3
* Yes, the problem is NOT encountered when using Kernel linux-image- 4.10.0- 21-generic 4.10.0-21.23.
* The problem is encountered when using 4.10.0-22-generic
In response to your request https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1697556/ comments/ 4
I have tested with upstream kernel 4.10.17
linux-headers- 4.10.17- 041017_ 4.10.17- 041017. 201705201051_ all.deb 4.10.17- 041017- generic_ 4.10.17- 041017. 201705201051_ amd64.deb 4.10.17- 041017- generic_ 4.10.17- 041017. 201705201051_ amd64.deb
linux-headers-
linux-image-
and equally encountered the problem. I therefore added the tag: 'kernel- bug-exists- upstream' .