It would be good to first identify which mainline kernel introduce the regression. The 3.2.0-18.28 kernel was based off of upstream 3.2.9. The 3.2.0-19.31 kernel was rebased to 3.2.10, 3.2.11 and 3.2.12.
Could you test the mainline 3.2.11[0] kernel and see if the bug was introduce in that version? If it was not, please test the 3.2.12[1] kernel. There was a build issue with the mainline 3.2.10 kernel, so there is not a prebuilt kernel to test that version.
Once we know what version introduced the bug, we can bisect to find the exact commit.
It would be good to first identify which mainline kernel introduce the regression. The 3.2.0-18.28 kernel was based off of upstream 3.2.9. The 3.2.0-19.31 kernel was rebased to 3.2.10, 3.2.11 and 3.2.12.
Could you test the mainline 3.2.11[0] kernel and see if the bug was introduce in that version? If it was not, please test the 3.2.12[1] kernel. There was a build issue with the mainline 3.2.10 kernel, so there is not a prebuilt kernel to test that version.
Once we know what version introduced the bug, we can bisect to find the exact commit.
[0] http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v3.2.11- precise/ kernel. ubuntu. com/~kernel- ppa/mainline/ v3.2.12- precise/
[1] http://