Comment 44 for bug 1316221

Aaron Wolf, if you tested it on 3.18 (which version number specifically?) and it's not reproducible, then this is considered fixed. As well, this wouldn't be an issue to report upstream, but a downstream (Ubuntu) one.

Hence, the next step is to fully reverse commit bisect from kernel 3.15-rc6 to the 3.18 kernel you tested fixed in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release.

Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs