From: Michael Ellerman <mpe@ellerman.id.au>
To: Christian Zigotzky <chzigotzky@xenosoft.de>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Boot problems with a PA6T board
Date: Mon, 26 May 2014 22:26:06 +1000 [thread overview]
Message-ID: <1401107166.23096.1.camel@concordia> (raw)
In-Reply-To: <53720AAC.1000100@xenosoft.de>
On Tue, 2014-05-13 at 14:06 +0200, Christian Zigotzky wrote:
> On 05.05.2014 07:48, Michael Ellerman wrote:
> > On Sun, 2014-05-04 at 18:02 +0200, Christian Zigotzky wrote:
> >> Hi All,
> >>
> >> The RC 1, 2, and 3 of the kernel 3.15 don't boot on my PA6T board with a
> >> Radeon HD 6870 graphics card.
> >>
> >> Screenshot:
> >> http://forum.hyperion-entertainment.biz/download/file.php?id=1060&mode=view
> >>
> >> The kernel 3.14 starts without any problems. Has anyone a tip for me,
> >> please?
> > The line that says "starting cpu hw idx 0... failed" looks a little worrying.
> > Do you see that on 3.14 as well?
> >
> > Otherwise bisection is probably your best bet.
> Hi All,
>
> I have found out which patch is responsible for the boot problems. It's
> patch 9000c17dc0f9c910267d2661225c9d33a227b27e. Link:
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9000c17dc0f9c910267d2661225c9d33a227b27e
Hi Christian,
I'm almost certain that is not the commit which breaks your machine. Or if it
is, something *really* weird is going on.
The code changed in that commit should never run on a PA6T.
> Experimental protocol:
>
> git checkout -f 01d8885785a60ae8f4c37b0ed75bdc96d0fc6a44; git clean -fdx
> (from 02/04/14) -> Kernel boots
> git checkout -f f1553174a207f68a4ec19d436003097e0a4dc405; git clean -fdx
> (from 03/04/14) -> Kernel boots
> git checkout -f d40326f4b9f9617cdfd30f83a2db57d47e9c5bac; git clean -fdx
> (from 04/04/14) -> Kernel boots
> git checkout -f 930b440cd8256f3861bdb0a59d26efaadac7941a; git clean -fdx
> (from 05/04/14) -> doesn't boot (rtc error)
> git checkout -f 2b3a8fd735f86ebeb2b9d061054003000c36b654; git clean -fdx
> (from 06/04/14) -> doesn't boot (rtc error)
> git checkout -f 26c12d93348f0bda0756aff83f4867d9ae58a5a6; git clean -fdx
> (from 07/04/14) -> doesn't boot (rtc error)
> git checkout -f a6c8aff022d4d06e4b41455ae9b2a5d3d503bf76; git clean -fdx
> (from 08/04/14) -> Kernel boots
> git checkout -f 035328c202d26a824b8632fd3b00635db5aee5a2; git clean -fdx
> (from 08/04/14) -> Kernel boots
> git checkout -f 9000c17dc0f9c910267d2661225c9d33a227b27e; git clean -fdx
> (from 08/04/14) powerpc/powernv: Fix endian issues with sensor code
> One OPAL call and one device tree property needed byte swapping. ->
> doesn't boot (prom_init)
> git checkout -f d3d35d957a9d0733dc51f14b5abc0bff5d3c5f3a; git clean -fdx
> (from 08/04/14) -> doesn't boot (prom_init)
> git checkout -f c4586256f0c440bc2bdb29d2cbb915f0ca785d26; git clean -fdx
> (from 09/04/14) -> doesn't boot (prom_init)
So it looks like you manually picked commits based on the date?
That's a good start, but if you want to find the actual problem commit you need
to do a proper bisect.
> I'm not a programmer but what can I do to solve this boot problem?
To start with you can probably narrow it down a bit by testing the following
commits:
18a1a7a1d862ae0794a0179473d08a414dd49234
d8ff9cdf68fd119d491f3de90e1a612afc2f3b2b
0f5a869600141a0d5575e3190af01a050c081b07
c7e64b9ce04aa2e3fad7396d92b5cb92056d16ac
d3e144532703fe2454b56eddb56f30d2d620187b
cheers
next prev parent reply other threads:[~2014-05-26 12:26 UTC|newest]
Thread overview: 18+ 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 [this message]
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
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
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=1401107166.23096.1.camel@concordia \
--to=mpe@ellerman.id.au \
--cc=chzigotzky@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).