Comment 15 for bug 1035172

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Thanks for the update, Adam.

Since you believe the regression was introduced in v3.3, can you test the following release candidates? That will allow us to identify a begin and end version for the bisect:

v3.3-rc1 http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc1-precise/
v3.3-rc2 http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc2-precise/
v3.3-rc3 http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc1-precise/
...

Basically we want to identify the first release candidate that introduced this bug. Then that will be our 'BAD' for the bisect with the prior release candidate being the 'GOOD' SHA1.