Would it be possible for you to test a few upstream kernels? I'd first like to have you test the latest mainline kernels, to see if this bug is already fixed:
v3.5-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc3-quantal/
Also, since this appears to be a regression, can you test the following two kernels to see if they are the proper ones to bisect between:
v3.2.16: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.16-precise/ and v3.2.17: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.17-precise/
I expect 3.2.16 to not have the bug. It would be good to know if 3.2.17 is when the bug was introduced.
Would it be possible for you to test a few upstream kernels? I'd first like to have you test the latest mainline kernels, to see if this bug is already fixed:
v3.5-rc3: http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v3.5-rc3- quantal/
Also, since this appears to be a regression, can you test the following two kernels to see if they are the proper ones to bisect between:
v3.2.16: http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v3.2.16- precise/ kernel. ubuntu. com/~kernel- ppa/mainline/ v3.2.17- precise/
and
v3.2.17: http://
I expect 3.2.16 to not have the bug. It would be good to know if 3.2.17 is when the bug was introduced.