diff options
| author | Takao Indoh <indou.takao@jp.fujitsu.com> | 2008-04-15 13:59:54 +0400 |
|---|---|---|
| committer | Tony Luck <tony.luck@intel.com> | 2008-04-15 22:20:53 +0400 |
| commit | 072f042df335d7e0da2027637bcf720d7ff1589b (patch) | |
| tree | 0909837c84e84fa051bf78b1302836a1c89f944f /arch/ia64/kernel/crash.c | |
| parent | 98075d245a5bc4aeebc2e9f16fa8b089a5c200ac (diff) | |
| download | linux-072f042df335d7e0da2027637bcf720d7ff1589b.tar.xz | |
[IA64] kdump: Add crash_save_vmcoreinfo for INIT
This patch fixes the problem that kdump by INIT does not work if we use
makedumpfile. The problem is that after INIT is issued, 2nd kernel
starts and makedumpfile fails with the following error message.
/proc/vmcore doesn't contain vmcoreinfo.
'-x' or '-i' must be specified.
makedumpfile Failed.
The cause of this problem is that kernel does not call
crash_save_vmcoreinfo. When kdump starts by panic or sysrq-trigger,
crash_save_vmcoreinfo is called by crash_kexec. But this function is not
called when kdump starts by INIT. The Attached patch fixes this.
This patch just adds crash_save_vmcoreinfo into machine_kdump_on_init so
that crash_save_vmcoreinfo can be called when kdump starts by INIT.
I tested this patch with linux-2.6.25-rc9 and I confirmed it worked.
Signed-off-by: Takao Indoh <indou.takao@jp.fujitsu.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
Diffstat (limited to 'arch/ia64/kernel/crash.c')
| -rw-r--r-- | arch/ia64/kernel/crash.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/ia64/kernel/crash.c b/arch/ia64/kernel/crash.c index e74e15a08892..90ef338cf46f 100644 --- a/arch/ia64/kernel/crash.c +++ b/arch/ia64/kernel/crash.c @@ -119,6 +119,7 @@ machine_crash_shutdown(struct pt_regs *pt) static void machine_kdump_on_init(void) { + crash_save_vmcoreinfo(); local_irq_disable(); kexec_disable_iosapic(); machine_kexec(ia64_kimage); |