The Ubuntu 3.11.0-11.17 kernel was rebased to upstream 3.11.3. This regression may have been introduced in one of the stable updates.
I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.
Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug:
The Ubuntu 3.11.0-11.17 kernel was rebased to upstream 3.11.3. This regression may have been introduced in one of the stable updates.
I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.
Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug:
Upstream v3.11 Final: http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v3.11-saucy/ kernel. ubuntu. com/~kernel- ppa/mainline/ v3.11.1- saucy/ kernel. ubuntu. com/~kernel- ppa/mainline/ v3.11.2- saucy/
Upstream v3.11.1: http://
Upstream v3.11.2: http://
If none of these version exhibit the bug, we will need to look at Ubuntu specific SAUCE patches.