From: Bob Montgomery <bob.montgomery@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: IA64 Kexec-Kdump kernel patch
Date: Mon, 14 Aug 2006 21:24:57 +0000 [thread overview]
Message-ID: <1155590697.26951.196.camel@amd.troyhebe> (raw)
In-Reply-To: <1155538073.2585.44.camel@linux-znh>
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.
My "got here" printk's on the console indicate:
SysRq : Trigger a crashdump
machine_crash_shutdown
device_shootdown
machine_kexec type: 1
And then it hangs.
My test system: hp A6870A server rx2600
From /proc/iomem:
04a1f000-3f5e3fff : System RAM
10000000-17ffffff : Crash kernel
# 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
relevant CONFIG settings (from /proc/config.gz)
CONFIG_HOTPLUG=y
CONFIG_IA64_HP_ZX1=y
# CONFIG_IA64_HP_ZX1_SWIOTLB is not set
CONFIG_HOTPLUG_CPU=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
# CONFIG_SPARSEMEM_MANUAL is not set
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
CONFIG_ACPI_HOTPLUG_CPU=y
# CONFIG_HOTPLUG_PCI is not set
CONFIG_AGP_HP_ZX1=y
CONFIG_PROC_VMCORE=y
Bob Montgomery
next prev parent reply other threads:[~2006-08-14 21:24 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 [this message]
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
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=1155590697.26951.196.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