Did you happen to have a chance to test the latest mainline kernel, posted in comment #2? Mainline is now up to -rc7, so the link to the kernel would be:
If the bug is fixed in mainline, we can perform a reverse bisect to identify the commit that fixes it.
However, if the bug still exists in mainline, we would want to perform a regular kernel bisect to find the commit that introduced the regression. To perform a bisect, we need to identify the last good and first bad kernel versions. Per comment #7 v3.16 is good, but v3.19 is bad. We would want to test the versions in between. So if mainline still has the bug, can you test the following upstream kernels:
Did you happen to have a chance to test the latest mainline kernel, posted in comment #2? Mainline is now up to -rc7, so the link to the kernel would be:
http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v4.6-rc7- wily/
If the bug is fixed in mainline, we can perform a reverse bisect to identify the commit that fixes it.
However, if the bug still exists in mainline, we would want to perform a regular kernel bisect to find the commit that introduced the regression. To perform a bisect, we need to identify the last good and first bad kernel versions. Per comment #7 v3.16 is good, but v3.19 is bad. We would want to test the versions in between. So if mainline still has the bug, can you test the following upstream kernels:
v3.17: http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v3.17-utopic/ kernel. ubuntu. com/~kernel- ppa/mainline/ v3.18-vivid/
v3.18: http://
Once we have these results, we can narrow down the versions further to individual release candidates.
Thanks in advance!