All of lore.kernel.org
 help / color / mirror / Atom feed
From: Piet Delaney <pdelaney@bluelane.com>
To: Geoff Levand <geoffrey.levand@am.sony.com>
Cc: Rajasekaran P <rajasekaran83@gmail.com>,
	kexec@lists.infradead.org, piet@bluelane.com
Subject: Re: Fwd: Kexec support for PS3 (ppc64)
Date: Tue, 11 Mar 2008 19:47:06 -0800	[thread overview]
Message-ID: <47D7523A.9080102@bluelane.com> (raw)
In-Reply-To: <47D7349E.90409@am.sony.com>


[-- Attachment #1.1: Type: text/plain, Size: 1784 bytes --]

Geoff Levand wrote:
> Pete/Piet Delaney wrote:
>   
>> 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 \x13e
>> |>>
>> |>> 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.
>>     
>
> When the first stage kernel goes down it releases all hypervisor
> resources so that whatever boots next can successful open those
> resources.  The frame buffer is one of those resources that are
> released, and after it is, there will be no more output to the
> display until the second stage image brings up its display.  It
> is not a matter of adding print statements or string formatting.
>   

Oh, I thought you experienced the same problem I had
with printk() calls in some of the kexec functions making
it no longer work. I was considering changing my KEXEC_DEBUG()
macros to using printf() instead of printk() and importing
the purgatory printf() code.
> -Geoff
>
>   


[-- Attachment #1.2: Type: text/html, Size: 2339 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2008-03-12  4:00 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
2008-03-12  1:40             ` Geoff Levand
2008-03-12  3:47               ` Piet Delaney [this message]
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=47D7523A.9080102@bluelane.com \
    --to=pdelaney@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.