** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Tags removed: needs-reverse-bisect
** Tags added: cherry-pick reverse-bisect-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/13
Hi Christopher,
I eventually managed to find the fix commit (this took me ages).
$ git bisect bad
751109aad5834375ca9ed0dcfcd85a00cbf872b5 is the first bad commit
commit 751109aad5834375ca9ed0dcfcd85a00cbf872b5
Author: Rafael J. Wysocki
Date: Thu Jun 5 22:47:35 2014 +0200
ACPI / video: Cha
Ok, I followed the 'Reverse bisecting upstream kernel versions' section and
found that:
* v3.15.3-utopic is the last bad version
* v3.16-rc1-utopic is the first good version.
Working on 'Reverse commit bisecting upstream kernel versions' ...
--
You received this bug notification because you are
Florent Flament, the next step is to fully reverse commit bisect the
kernel in order to identify the fix commit. Could you please do this
following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
?
** Tags added: needs-reverse-bisect
** Changed in: li
Oh this bug is fixed upstream (Linux 3.16-rc3), thanks !
Florent
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-3.16-rc3
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Florent Flament, could you please test the latest upstream kernel available
from the very top line at the top of the page (not the daily folder) following
https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
upstream developers to examine the issue. Once you've tested the upst
