Comment 30 for bug 1667323

It is probably best to perform a "Reverse" bisect instead of a standard bisect, since we know this bug is fixed in 4.10 final.

A "Reverse" bisect will identify the commit that fixes the bug instead of identifying the commit that introduced the bug. We just need to do the oppisite of a standard bisect. We need to know the last Bad kernel and the first Good one.

Like in comment #28, can you test the following kernels. We are looking for the last bad version and the first good one:

v4.5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
v4.7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/
v4.9: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/