Thanks for testing mainline. The stack trace looks the same as prior kernels. We should perform a regular kernel bisect to identify the commit that introduced this regression.
It sounds like none of the upstream kernels exhibit this bug per comment #6, is that correct?
If that is the case, it may be due to an Ubuntu SAUCE patch. Can you give an early 17.10 kernel a test:
Thanks for testing mainline. The stack trace looks the same as prior kernels. We should perform a regular kernel bisect to identify the commit that introduced this regression.
It sounds like none of the upstream kernels exhibit this bug per comment #6, is that correct?
If that is the case, it may be due to an Ubuntu SAUCE patch. Can you give an early 17.10 kernel a test:
https:/ /launchpad. net/~canonical- kernel- team/+archive/ ubuntu/ unstable/ +build/ 13358561