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: Wed, 28 May 2014 10:53:08 +0200 [thread overview]
Message-ID: <5385A3F4.8070004@xenosoft.de> (raw)
In-Reply-To: <1401251015.5468.5.camel@concordia>
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:
>> Hi Michael,
>>
>> Thanks a lot for your answer.
>>
>> ...
>>
>> 18a1a7a1d862ae0794a0179473d08a414dd49234 <- It doesn't boot. Error messages: Oops: Machine check, sig: 7 [#1] CPU: 1 PID: 1 Comm: swapper/0 not tainted
>> d8ff9cdf68fd119d491f3de90e1a612afc2f3b2b <- It boots. :-)
>> 0f5a869600141a0d5575e3190af01a050c081b07 <- It boots. :-)
>> c7e64b9ce04aa2e3fad7396d92b5cb92056d16ac <- It boots. :-)
>> d3e144532703fe2454b56eddb56f30d2d620187b <- It boots. :-)
>>
>> I think the machine check is the problem.
> Yes I think it is. Do you get any more info, or just that one line?
>
> So I think the latest working commit we have is d8ff9cdf68fd119d491f3de90e1a612afc2f3b2b.
>
> I'm going to guess that cd427485357c0c4b99f69719251baacf25946e11 is BAD. Can
> you please confirm or deny that?
It's not BAD. It boots.
Rgds,
Christian
>
> Assuming cd42748 is bad, you should do a git bisect between it and 18a1a7a.
> That should be a fairly quick bisect. That would be:
>
> $ git bisect start
> $ git bisect good d8ff9cdf68fd119d491f3de90e1a612afc2f3b2b
> $ git bisect bad cd427485357c0c4b99f69719251baacf25946e11
>
> If cd42748 is *good*, then you'll need to do a bigger bisect from d8ff9cd to
> 18a1a7a.
>
>
> cheers
>
>
>
next prev parent reply other threads:[~2014-05-28 9:06 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 [this message]
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
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=5385A3F4.8070004@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).