That's good news that 4.10-rc3 fixes the bug. I think it would be best to perform a "Reverse" bisect to identify the fix that is already upstream versus continuing a regular bisect to find the commit that introduced the bug.
For a reverse bisect, we need to find the last bad kernel version and first good one. We now know that v4.10-rc3 is good. Can you next text 4.10-rc1? It is available from:
That's good news that 4.10-rc3 fixes the bug. I think it would be best to perform a "Reverse" bisect to identify the fix that is already upstream versus continuing a regular bisect to find the commit that introduced the bug.
For a reverse bisect, we need to find the last bad kernel version and first good one. We now know that v4.10-rc3 is good. Can you next text 4.10-rc1? It is available from:
http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v4.10-rc1
If 4.10-rc1 is good, we would want to test 4.9 and it's release candidates, then if needed, 4.8, etc.