All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Subject: Kernel 3.15: Boot problems with a PA6T board
Date: Sat, 31 May 2014 13:01:26 +0200	[thread overview]
Message-ID: <5389B686.7070305@xenosoft.de> (raw)
In-Reply-To: <5389AEB6.4030500@xenosoft.de>

On 31.05.2014 12:28, Christian Zigotzky wrote:
> On 29.05.2014 04:48, Michael Ellerman wrote:
>> 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.
> OK :-)
>
> git bisect bad
> Bisecting: 2902 revisions left to test after this (roughly 12 steps)
> [b22f136071b1a797e96b3ee6fb0dc32625bd152e] staging: rtl8821ae: Fix 
> quoted string split across lines <- Kernel boots :-)
>
> What shall I do next?
OK, I know it: git bisect good

-- Christian

  reply	other threads:[~2014-05-31 11:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04 16:02 Boot problems with a PA6T board Christian Zigotzky
2014-05-05  5:48 ` Michael Ellerman
2014-05-05  9:41   ` Christian Zigotzky
2014-05-13 12:06   ` Christian Zigotzky
2014-05-26 12:26     ` Michael Ellerman
2014-05-27 23:08       ` Kernel 3.15: " Christian Zigotzky
2014-05-28  4:23         ` Michael Ellerman
2014-05-28  8:53           ` Christian Zigotzky
2014-05-28 11:25             ` Christian Zigotzky
2014-05-29  2:48               ` Michael Ellerman
2014-05-31 10:28                 ` Christian Zigotzky
2014-05-31 11:01                   ` Christian Zigotzky [this message]
2014-05-31 22:33                     ` Christian Zigotzky
2014-06-10 10:58                       ` Christian Zigotzky
2014-06-10 13:20                         ` Christian Zigotzky
2014-06-18  6:51                           ` Michael Ellerman
2014-06-18  8:57                             ` Christian Zigotzky
2014-06-18  9:26                               ` Christian Zigotzky
     [not found] <25927053.1589.1403105603389.JavaMail.adrian@Gurnard>
2014-06-18 17:42 ` Christian Zigotzky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5389B686.7070305@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.