Comment 27 for bug 1152736

I can perform a "Reverse" kernel bisect to identify the commit that fixes this bug in the v3.9 kernel. We first need to identify the first kernel version that fixes this issue.

It looks like the bug is fixed in v3.9-rc2. The next step would be to test v3.9-rc1:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc1-raring/

If v3.9-rc1 has the bug, I will bisect between v3.9-rc1 and v3.9-rc2. If v3.9-rc1 does not have the bug, I will bisect between v3.8 final and v3.9-rc1.

The reverse bisect will require the testing of 8 - 12 test kernels, but it should track down the exact commit that fixes the bug.