All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mohan Kumar M <mohan@in.ibm.com>
To: gib <suchada.pitchayasamanya@toshiba.co.jp>
Cc: kexec@lists.infradead.org
Subject: Re: Question about forcing kernel panic on PowerMac G5 by kexec command
Date: Tue, 22 Apr 2008 11:05:09 +0530	[thread overview]
Message-ID: <480D790D.7080403@in.ibm.com> (raw)
In-Reply-To: <200804210517.m3L5Hq61011769@toshiba.co.jp>

gib wrote:
> Hello all,
> 
>  
> 
> I’m working on PowerMac G5 complied with CONFIG_KEXEC = y.
> 
> It’s work fine with Kexec command option l ( kexec –l /boot/vmlinux… ) 
> but after the capture kernel pre-loading ( by kexec –p /boot/vmlinux… ),
> 
Hi Suchada,

What kernel version you are trying? Also what level of kexec-tools you use?

I hope you are aware that you need two different kernels for kdump, 
first one is meant for normal use and another one is kdump kernel. Did 
you compile the kdump kernel with CONFIG_CRASH_DUMP?

> when I forced kernel panic by “echo c > /proc/sysrq-trigger” the console 
> kept showing “Sending IPI to other CPU” and did not go to the next step.
> 
>  
> 
> According to this list there was some problem about kdump in ppc970 based CPU which PowerMac’s CPU are.

There was a interrupt routing problem with specific ppc970 cpu type, but 
that problem is fixed now.

Regards,
Mohan.


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

  reply	other threads:[~2008-04-22  5:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21  5:17 Question about forcing kernel panic on PowerMac G5 by kexec command gib
2008-04-22  5:35 ` Mohan Kumar M [this message]
2008-04-23  0:41   ` gib
2008-04-23  9:48     ` Mohan Kumar M
2008-05-09  4:06       ` gib
2008-05-14  4:25         ` Mohan Kumar M
2008-05-14  5:02           ` gib
2008-05-21 13:58             ` Mohan Kumar M
2008-05-23  9:04               ` Mohan Kumar M
2008-05-29  0:14                 ` gib

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=480D790D.7080403@in.ibm.com \
    --to=mohan@in.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=suchada.pitchayasamanya@toshiba.co.jp \
    /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.