Comment 70 for bug 1201528

Thanks for testing, Natalia. So it sounds like this bug was introduced in a Sauce patch added in Raring. However, it also sounds like this is broken in the current mainline kernel, since you were able to reproduce the bug with 3.11-rc4.

It would be helpful if you could test some additional kernels. First the -proposed Raring kernel, just to confirm it wasn't fixed yet:
https://launchpad.net/ubuntu/+source/linux/3.8.0-28.41

If it still exists in -proposed, we have two options, we can bisect the Raring kernels to find the commit that introduced the regrssion and/or we can bisect the current mainline kernel to find the commit that breaks it there. It may be the same patch that breaks audio in both instances.

It might be best to find the commit that breaks this in mainline first, since it is going to affect Saucy and we can work with upstream to get it fixed before release. We can then see if that same patch was applied to Raring as a Sauce patch.

Can you test the v3.11-rc1 kernel to see if the bug also exists there:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/

If 3.11-rc1 is good, can you test v3.11-rc2:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc2-saucy/

If 3.11-rc2 is good, we should next test v3.11-rc3:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc3-saucy/

Based on these tests, we should know the two 3.11 kernels we should bisect between.