Thanks for testing -proposed! The 4.15.0-35 kernel contains the 4.15.18 upstream stable updates, which resolve this bug per comment #27. This might indicate this bug was introduced by an Ubuntu SAUCE patch, since it does not exist upstream.
We can perform a kernel bisect to identify the SAUCE patch that introduced this regression. To do that, we first need to identify the last Ubuntu kernel that did not have this bug, and the first version that does.
Thanks for testing -proposed! The 4.15.0-35 kernel contains the 4.15.18 upstream stable updates, which resolve this bug per comment #27. This might indicate this bug was introduced by an Ubuntu SAUCE patch, since it does not exist upstream.
We can perform a kernel bisect to identify the SAUCE patch that introduced this regression. To do that, we first need to identify the last Ubuntu kernel that did not have this bug, and the first version that does.
Can you test the following kernels: /launchpad. net/~canonical- kernel- security- team/+archive/ ubuntu/ ppa/+build/ 14271945
4.13.0-32.35: https:/
4.14.0-16.19: https:/ /launchpad. net/~canonical- kernel- security- team/+archive/ ubuntu/ ppa2/+build/ 14223014
If the 4.13.0-32 kernel also has the bug, we will have to work further back and test older kernel versions.
Thanks in advance!