From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Rajasekaran P <rajasekaran83@gmail.com>
Cc: kexec@lists.infradead.org
Subject: Re: Fwd: Kexec support for PS3 (ppc64)
Date: Fri, 07 Mar 2008 11:01:40 -0800 [thread overview]
Message-ID: <47D19114.1090700@am.sony.com> (raw)
In-Reply-To: <4574cb3d0803062155k7da6be9al30ee3f35d01f9f0@mail.gmail.com>
Hi,
I maintain kexec for PS3, but have just done what was needed to
make it work for kboot. I am not a kexec expert, and have
never tried to use kdump, or other features of kexec, only the
things needed for kboot.
On 03/06/2008 09:55 PM, Rajasekaran P wrote:
>> On Thu, Mar 06, 2008 at 04:55:04PM +0530, Rajasekaran Periyasamy
> wrote:
>> > Hi,
>> > I put a printk() in the early lines of early_parse_crashk() with
>> > KERN_EMERG, but not able to see that on the boot screen. I think the
>> > control is not transferred to early_parse_crashk() at all. With out
> this
>> > "crashkernel" argument, the same kernel boots up properly.
This kind of thing is what kboot uses, and is known to work:
kexec -l -t elf-ppc64 --append='root=XXX video=YYY' /boot/vmlinux.strip
kexec -e
I recommend you get it to work first.
>> Looks strange.
>>
>> Could you please include more debug printks in the function
>> do_early_param in init/main.c to check whether early_parse_crashk is
>> called or not?
That won't work, since it is hanging before the video driver is up,
and you'll never see those.
> I've tried, but no result... Please have a look at the snapshot of boot
> process.
>
> I think the kernel is not at all getting initiated to boot up.
Your photo shows that the first stage kernel has gone down, and it
hung up either very late going down, or early coming back up in the
second stage.
> Whatever you see in the snapshot,
> 1. "Modified cmdline:" is from
> "kexec-tools-1.101/kexec/arch/ppc64/fs2dt.c" putnode() function,
I guess that version of exec-tools (kexec-tools-1.101) may be too old,
and doesn't have the bug-fixes I needed to make to kexec-tools for it
to work with PS3. Those fixes were merged into kexec-tools several
month ago.
I recommend you try with an up-to-date kexec from here:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/kexec-tools-testing.git
I have tested both 32 and 64 bit builds.
I also recommend to start with a known good second stage kernel.
I tested Linux 2.6.25-rc4 built with ps3_defconfig and it works.
Do not use an initrd at first try.
-Geoff
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-03-07 19:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C5065F118AFB3D478B052FC1E9810D9CA9041B@tec-mail.ttec.soc-soft.com>
2008-03-07 5:55 ` Fwd: Kexec support for PS3 (ppc64) Rajasekaran P
2008-03-07 19:01 ` Geoff Levand [this message]
2008-03-11 10:25 ` Rajasekaran P
2008-03-11 16:54 ` Geoff Levand
2008-03-11 18:48 ` Geoff Levand
2008-03-12 1:21 ` Pete/Piet Delaney
2008-03-12 1:40 ` Geoff Levand
2008-03-12 3:47 ` Piet Delaney
2008-03-12 5:25 ` Mohan Kumar M
2008-03-12 5:40 ` Geoff Levand
2008-03-12 5:56 ` Mohan Kumar M
2008-03-14 10:36 ` Rajasekaran P
2008-03-14 11:02 ` Mohan Kumar M
2008-03-14 11:18 ` Rajasekaran P
2008-03-14 11:22 ` Mohan Kumar M
2008-03-16 6:19 ` Rajasekaran P
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=47D19114.1090700@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=kexec@lists.infradead.org \
--cc=rajasekaran83@gmail.com \
/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.