Thanks for reporting this upstream. In the mean time, we can perform a kernel bisect to identify the commit that caused this. Now that we know it was introduced in v3.10, we need to see which release candidate introduced the bug.
Can you test the following kernels and report back? We are looking for the earliest kernel version that exhibits this bug:
Thanks for reporting this upstream. In the mean time, we can perform a kernel bisect to identify the commit that caused this. Now that we know it was introduced in v3.10, we need to see which release candidate introduced the bug.
Can you test the following kernels and report back? We are looking for the earliest kernel version that exhibits this bug:
v3.10-rc4: http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v3.10-rc4- saucy/
If v3.10-rc4 does not exhibit the bug then test v3.10-rc6: kernel. ubuntu. com/~kernel- ppa/mainline/ v3.10-rc6- saucy/
v3.10-rc6: http://
If v3.10-rc4 does exhibit the bug then test v3.10-rc2: kernel. ubuntu. com/~kernel- ppa/mainline/ v3.10-rc2- saucy
v3.10-rc2: http://
You don't have to test every kernel, just up until the kernel that first has this bug.
Thanks in advance!