From: Pete/Piet Delaney <pete@bluelane.com>
To: Geoff Levand <geoffrey.levand@am.sony.com>
Cc: Rajasekaran P <rajasekaran83@gmail.com>, kexec@lists.infradead.org
Subject: Re: Fwd: Kexec support for PS3 (ppc64)
Date: Tue, 11 Mar 2008 17:21:07 -0800 [thread overview]
Message-ID: <47D73003.8060208@bluelane.com> (raw)
In-Reply-To: <47D6D406.8050209@am.sony.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Geoff Levand wrote:
| Geoff Levand wrote:
|> Rajasekaran P wrote:
|>> Hi Geoff,
|>> Thanks for your information.
|>>
|>> I used latest kexec tools with 2.6.23 kernel built with ps3_defconfig.
|>> This kernel boots normally on PS3. But when I add "crashkernel"
|>> argument, it goes on hang.
|>>
|>> # kexec --command-line="video=ps3fb:mode:166 rhgb root=/dev/ps3da3
|>> crashkernel=128M@32M" \
|>> --initrd=/boot/initrd-2.6.23.img \
|>> -l /boot/vmlinux-2.6.23
|>>
|>> # taskset 1 kexec –e
|>>
|>> Nothing happens after this. As you said earlier in your mail, I am not
|>> getting any PRINTK outputs from kernel on screen.
I was wondering about bringing in the printf() code from purgatory
and using that to print info about what's going on in the kexec code.
The standalone printf() might come in handy in other places; Ex: kgdb
stub. If it was in a library it could also be used during kernel
decompression to inform on problems occurring, like checksum errors.
- -piet
|> As I said, this usage is currently unsupported. Could you tell me
what you
|> want to do? I mean, why do you want to use this 'crashkernel=' option?
|>
|> As a note, the ps3 has 128MiB of boot memory, so I guess 128M@32M won't
|> work.
|
| Just FYI, I tried this and the kernel booted:
|
| ./kexec -l -t elf-ppc64 --append='crashkernel=64M@32M root=/dev/nfs rw
ip=dhcp video=wuxga' /boot/vmlinux.strip
|
| I saw this output:
|
| kexec: waiting for cpu 1 (physical 1) to go down
| Reserving 64MB of memory at 32MB for crashkernel (System RAM: 128MB)
| ...
| Kernel command line: crashkernel=64M@32M root=/dev/nfs rw ip=dhcp
video=wuxga
|
| -Geoff
|
|
| _______________________________________________
| kexec mailing list
| kexec@lists.infradead.org
| http://lists.infradead.org/mailman/listinfo/kexec
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH1zACJICwm/rv3hoRAtyQAJ9E+nFUBAtTpmRCYoXTCNXNeuRm7ACfXOUa
YX3Ipj6hDj9Cfwli6H/E1Gg=
=SMaU
-----END PGP SIGNATURE-----
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-03-12 1:21 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
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 [this message]
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=47D73003.8060208@bluelane.com \
--to=pete@bluelane.com \
--cc=geoffrey.levand@am.sony.com \
--cc=kexec@lists.infradead.org \
--cc=piet@bluelane.com \
--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.