Comment 8 for bug 1330530

I have tested 28 mainline kernels from 9 branches currently maintained (3.2, 3.4, 3.10, 3.11, 3.12, 3.13, 3.14, 3.15, 3.16), focusing on those that were built around the time the problematic commit was introduced (May-June 2014). The bug appears to affect the 3.2 branch exclusively. Thus I will now try to forward bisect commits from 3.2.58 (last good) to 3.2.59 (first bad).

Just for reference, here are results of my testing. "Bad" means that bug was reproducible in the given kernel, "good" that it was not.
3.2.58 good
3.2.59 bad
3.2.60 bad
3.4.89 good
3.4.90 good
3.4.91 good
3.4.92 good
3.4.93 good
3.4.94 good
3.10.44 good
3.11.10.11 good
3.13.22 good
3.13.11 good
3.13.11.1 good
3.13.11.2 good
3.13.11.3 good
3.14.8 good
3.15-rc1 good
3.15-rc2 good
3.15-rc3 good
3.15-rc4 good
3.15-rc5 good
3.15-rc6 good
3.15-rc7 good
3.15-rc8 good
3.15 good
3.15.1 good
3.16-rc1 good