Comment 11 for bug 1529266

Here are the results of the reverse bisect:

 $ git bisect start
 $ git bisect bad v4.4-rc6
 $ git bisect good v4.2.6
Bisecting: a merge base must be tested
[64291f7db5bd8150a74ad2036f1037e6a0428df2] Linux 4.2
 $ cp /boot/config-4.2.0-22-generic .config
 $ make oldconfig
 $ make clean
 $ time make -j5 deb-pkg LOCALVERSION=-custom-1
 $ cd ..
 $ ls
 $ sudo dpkg -i linux-image-4.2.0-custom-1_4.2.0-custom-1-2_amd64.deb linux-headers-4.2.0-custom-1_4.2.0-custom-1-2_amd64.deb
 $ sudo reboot
 $ git bisect bad
The merge base 64291f7db5bd8150a74ad2036f1037e6a0428df2 is bad.
This means the bug has been fixed between 64291f7db5bd8150a74ad2036f1037e6a0428df2 and [1c02865136fee1d10d434dc9e3616c8e39905e9b].

Looks like I need to do a forward bisect from 4.2 to 4.2.6 to determine when the bug was introduced?