Thanks for your testing so far. All the upstream kernel (mainline) you have tested (4.9, 4.8, 4.4.40, 4.4.35 and 4.4.44) are fine, the two Ubuntu kernels 4.4.0-59 (based on upstream 4.4.35) and 4.4.0-64 (based on upstream 4.4.44) the bug can be reproduced. As #37, we need to find a working Ubuntu kernel to identify where the bug is first introduced, hence the request to test 4.4.0-20.
@nancy-hsu /launchpad. net/~canonical- kernel- team/+archive/ ubuntu/ ppa/+build/ 9583414 you can find download link for 4.4.0-20- generic_ 4.4.0-20. 36_amd64. deb and linux-image- extra-4. 4.0-20- generic_ 4.4.0-20. 36_amd64. deb /launchpad. net/~canonical- kernel- team/+archive/ ubuntu/ ppa/+build/ 9583414/ +files/ linux-image- 4.4.0-20- generic_ 4.4.0-20. 36_amd64. deb /launchpad. net/~canonical- kernel- team/+archive/ ubuntu/ ppa/+build/ 9583414/ +files/ linux-image- extra-4. 4.0-20- generic_ 4.4.0-20. 36_amd64. deb
Scroll down on https:/
linux-image-
Here are the links for your quick reference:
https:/
https:/
Thanks for your testing so far. All the upstream kernel (mainline) you have tested (4.9, 4.8, 4.4.40, 4.4.35 and 4.4.44) are fine, the two Ubuntu kernels 4.4.0-59 (based on upstream 4.4.35) and 4.4.0-64 (based on upstream 4.4.44) the bug can be reproduced. As #37, we need to find a working Ubuntu kernel to identify where the bug is first introduced, hence the request to test 4.4.0-20.