From: Michael Ellerman <michael@ellerman.id.au>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Linux/PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: kexec: proc/device-tree/chosen/linux,kernel-end: No such file or directory
Date: Wed, 01 Apr 2009 10:52:51 +1100 [thread overview]
Message-ID: <1238543571.6522.12.camel@localhost> (raw)
In-Reply-To: <alpine.LRH.2.00.0903311808310.32461@vixen.sonytel.be>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
On Tue, 2009-03-31 at 18:25 +0200, Geert Uytterhoeven wrote:
> With today's kernel, I can no longer kexec any kernel on PS3:
>
> | /proc/device-tree/chosen/linux,kernel-end: No such file or directory
> | Could not get memory layout
>
> Today's bad version: 15f7176eb1cccec0a332541285ee752b935c1c85
> Yesterday's good version: 0d34fb8e93ceba7b6dad0062dbb4a0813bacd75b
>
> Before I start bisecting (tomorrow or the day thereafter), anyone with an idea?
Hmm, not really.
Looking at the code the only obvious way you could end up without that
property is if you didn't have a /chosen?
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-31 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 16:25 kexec: proc/device-tree/chosen/linux,kernel-end: No such file or directory Geert Uytterhoeven
2009-03-31 23:52 ` Michael Ellerman [this message]
2009-04-01 0:45 ` Geoff Levand
2009-04-02 16:25 ` [PATCH] powerpc: Correct dependency of KEXEC (was: Re: kexec: proc/device-tree/chosen/linux,kernel-end: No such file or directory) Geert Uytterhoeven
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=1238543571.6522.12.camel@localhost \
--to=michael@ellerman.id.au \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linuxppc-dev@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).