public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Montgomery <bob.montgomery@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: IA64 Kexec-Kdump kernel patch
Date: Tue, 15 Aug 2006 19:31:09 +0000	[thread overview]
Message-ID: <1155670269.26951.215.camel@amd.troyhebe> (raw)
In-Reply-To: <1155538073.2585.44.camel@linux-znh>

On Tue, 2006-08-15 at 12:46 -0700, Keshavamurthy Anil S wrote:
> On Mon, Aug 14, 2006 at 05:24:57PM -0400, Bob Montgomery wrote:
> > On Mon, 2006-08-14 at 14:47 +0800, Zou Nan hai wrote:
> > > This patch is the kexec-kdump patch re-based to 2.6.18-rc4 kernel.
> > 
> > Contrary to expectations, my experience with this patch on a 2.6.18-rc4
> > kernel is that kexec -l, kexec -e is now working without my adding any
> > delays to mptscsih, and the kexec -p, echo c >/proc/sysrq-trigger case
> > hangs.
> > 
> > # cat /proc/cmdline
> > BOOT_IMAGE=scsi0:/EFI/debian/boot/vmlinuz-2.6.18-rc4-bobm root=/dev/sda4
> > raid=noautodetect crashkernel\x128M@256M panic=1 ro
> 
> Can you change crashkernelQ2M@256 and try
> kexec -p, echo c > /proc/sysrq-trigger case.

04a40000-3f5e3fff : System RAM
  10000000-2fffffff : Crash kernel

bobm@urlp2:~$ cat /proc/cmdline
root=/dev/sda4 crashkernelQ2M@256M panic=1 ro

# kexec -p vmlinux.strip --append="root=/dev/sda4 maxcpus=1 panic=1
irqpoll ro"

# echo c >/proc/sysrq-trigger

Still hangs with no indication on the console after my printk("bye\n")
just before the br.call at the end of machine_kexec.

Bob M.


  parent reply	other threads:[~2006-08-15 19:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14  6:47 IA64 Kexec-Kdump kernel patch Zou Nan hai
2006-08-14 21:24 ` Bob Montgomery
2006-08-15  0:47 ` Zou Nan hai
2006-08-15  1:56 ` Jay Lan
2006-08-15 17:39 ` Bob Montgomery
2006-08-15 19:15 ` Jay Lan
2006-08-15 19:31 ` Bob Montgomery [this message]
2006-08-15 19:46 ` Keshavamurthy Anil S
2006-08-15 22:36 ` Zou Nan hai
2006-08-15 22:40 ` Zou Nan hai
2006-08-16 18:25 ` Bob Montgomery
2006-08-16 22:34 ` Jay Lan
2006-08-16 22:46 ` Jay Lan
2006-08-17  0:34 ` Jay Lan
2006-08-17  0:38 ` Jack Steiner
2006-08-17  2:57 ` Horms
2006-08-17  3:56 ` Zou Nan hai
2006-08-17 18:53 ` Jay Lan

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=1155670269.26951.215.camel@amd.troyhebe \
    --to=bob.montgomery@hp.com \
    --cc=linux-ia64@vger.kernel.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