Comment 22 for bug 1491654

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

Thanks for the update. We can perform a "Reverse" bisect to identify the commit that fixes the bug in v4.10-rc3. We first need to identify the last bad kernel and first good one.

Can you test the following kernels:

3.14 final:
3.16 final:
4.0 final:
4.5 final:

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