Comment 22 for bug 1491654

Thanks for the update. We can perform a "Reverse" bisect to identify the commit that fixes the bug in v4.10-rc3. We first need to identify the last bad kernel and first good one.

Can you test the following kernels:

3.14 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/
3.16 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-utopic/
4.0 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/
4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
4.8-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/
4.10-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/

You don't have to test every kernel, just up until the kernel that first kernel that does not have this bug.