On Wed, 2014-05-28 at 13:25 +0200, Christian Zigotzky wrote: > On 28.05.2014 10:53, Christian Zigotzky wrote: > > Hi Michael, > > > > Thank you for your answer and thank you for your help. :-) > > > > On 28.05.2014 06:23, Michael Ellerman wrote: > >> On Wed, 2014-05-28 at 01:08 +0200, Christian Zigotzky wrote: > >> > >> I'm going to guess that cd427485357c0c4b99f69719251baacf25946e11 is > >> BAD. Can > >> you please confirm or deny that? > > > It's not BAD. It boots.
Hmm, interesting. > >> If cd42748 is *good*, then you'll need to do a bigger bisect from > >> d8ff9cd to > >> 18a1a7a. > OK :-) > > -> git clone > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git linux2-git > -> git bisect start > -> git bisect good d8ff9cdf68fd119d491f3de90e1a612afc2f3b2b > -> git bisect bad 18a1a7a1d862ae0794a0179473d08a414dd49234 > > Output: > Bisecting: 5900 revisions left to test after this (roughly 13 steps) > [cb1595563880a81dab6eab9a5ecb4520d2e76077] Merge tag 'tty-3.15-rc1' of > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty > > Unfortunately it doesn't boot. :-( OK. So you do: $ git bisect bad And it will pick a new commit for you to test. Repeat that ~13 times and you should have identified the bad commit. cheers _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev