From: Marc Dietrich <marvin24@gmx.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Geoff Levand <geoff@infradead.org>,
Declan Malone <declan.malone@gmail.com>,
cbe-oss-dev@lists.ozlabs.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: Time to remove platforms/cell?
Date: Fri, 23 Oct 2015 10:00:33 +0200 [thread overview]
Message-ID: <4305015.PtpKCQxEF8@fb07-iapwap2> (raw)
In-Reply-To: <1445565296.27586.3.camel@ellerman.id.au>
[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]
Am Freitag, 23. Oktober 2015, 12:54:56 schrieb Michael Ellerman:
> On Thu, 2015-10-22 at 12:15 -0700, Geoff Levand wrote:
> > Hi,
> >
> > On Fri, 2015-10-09 at 23:13 +0200, Marc Dietrich wrote:
> > > Am Freitag, 9. Oktober 2015, 10:45:42 schrieb Geoff Levand:
> > > > With the 4.2-rc4 kernel, kexec seems to work when CONFIG_SPU_FS=n.
> > > >
> > > > I
> > > >
> > > > have not tried with petitboot release white-09.09.01-15.56 yet though.
> > >
> > > I guess you mean 4.3-rc4. Still no luck with CONFIG_SPU_FS=n. No output
> > > even with direct calling kexec. Can you put a working kernel/initrd to
> > > some place so I can try this?
> >
> > I did some more work on this, but still did not find out what the problem
> > is. Kexec from 4.3 -> 4.3 works, but with the white-09.09.01-15.56
> >
> > petitboot (2.6.30.9) -> 4.3 gets a kernel panic:
> > -> early_setup(), dt_ptr: 0x7fff000
> >
> > Kernel panic - not syncing: BUG: Failed verifying flat device tree, bad
> > version?
> >
> > I'll look at it some more as I find time.
>
> That says that the device tree firmware gave you (ie. from kexec), is using
> an old version of the device tree format.
>
> I can't remember off the top of my head which version you need, but
> basically newer kernels require a newer device tree format. So your kexec
> might be too old?
that reminds me about a different question. I said before that I use plain
vmlinux for the kernel image. This works at least with 2.6.35 (the newest
kernel I got booting so far). But I also saw that a device tree is being
compiled and linked with the kernel to produce a dt image in
arch/powerpc/boot. Is it possible that newer kernels require a device tree?
Marc
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-10-23 8:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 5:28 Time to remove platforms/cell? Michael Ellerman
2015-09-17 8:43 ` Marc Dietrich
2015-09-17 9:31 ` Arnd Bergmann
2015-09-17 10:05 ` Michael Ellerman
2015-09-17 11:01 ` Arnd Bergmann
2015-09-17 17:50 ` Geoff Levand
2015-09-17 9:45 ` Michael Ellerman
2015-09-17 10:28 ` Marc Dietrich
2015-09-17 11:15 ` Arnd Bergmann
2015-09-21 9:42 ` Michael Ellerman
2015-09-21 9:44 ` Michael Ellerman
2015-10-04 19:27 ` Geoff Levand
2015-10-05 10:27 ` Marc Dietrich
2015-10-07 17:20 ` Geoff Levand
2015-10-08 18:10 ` Geoff Levand
2015-10-09 17:45 ` Geoff Levand
2015-10-09 21:13 ` Marc Dietrich
2015-10-22 19:15 ` Geoff Levand
2015-10-23 1:54 ` Michael Ellerman
2015-10-23 8:00 ` Marc Dietrich [this message]
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=4305015.PtpKCQxEF8@fb07-iapwap2 \
--to=marvin24@gmx.de \
--cc=cbe-oss-dev@lists.ozlabs.org \
--cc=declan.malone@gmail.com \
--cc=geoff@infradead.org \
--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).