Comment 5 for bug 1214931

Hi Olli,

We can perform a kernel bisect to identify the commit that introduced this bug. It will require testing about 7 - 10 test kernels. We first need to identify the first bad and last good kernel versions. The current Saucy kernel was based off of v3.11-rc6. Can you test v3.11-rc1 to see if that is the release candidate that first introduced this? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/

If v3.11-rc1 does not have the bug, we would want to test v3.11-rc2, then 3.11-rc3 and so on, until we hit the first bad kernel:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc2-saucy/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc3-saucy/

If 3.11-rc1 does have the bug, we would want to test v3.10 final, just to confirm it does not have the bug:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-saucy/