Comment 3 for bug 1194649

Joseph Salisbury (jsalisbury) wrote :

I'd like to perform a bisect to figure out what commit caused this regression. It would be very helpful to know 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 earliest kernel version that exhibits this bug:


If v3.10-rc4 does not exhibit the bug then test v3.8-rc6:

If v3.10-rc4 does exhibit the bug then test v3.8-rc2:

You don't have to test every kernel, just up until the kernel that first has this bug.

Thanks in advance!