It seems the bug exists in v3.2-rc1, so we will have to test earlier kernels to find when it was introduced. Can you test some of the v3.1 release candidates:
v3.1-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.1-rc2-oneiric/ v3.1-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.1-rc3-oneiric/ v3.1-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.1-rc4-oneiric/
...
Again, you don't have to test every kernel, just up until the kernel that first has this bug.
It seems the bug exists in v3.2-rc1, so we will have to test earlier kernels to find when it was introduced. Can you test some of the v3.1 release candidates:
v3.1-rc2: http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v3.1-rc2- oneiric/ kernel. ubuntu. com/~kernel- ppa/mainline/ v3.1-rc3- oneiric/ kernel. ubuntu. com/~kernel- ppa/mainline/ v3.1-rc4- oneiric/
v3.1-rc3: http://
v3.1-rc4: http://
...
Again, you don't have to test every kernel, just up until the kernel that first has this bug.