From: Jay Lan <jlan@sgi.com>
To: "linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: [IA64] kdump failed to produce vmcore in 2.6.28-rc2
Date: Tue, 28 Oct 2008 17:49:51 -0700 [thread overview]
Message-ID: <4907B32F.4030009@sgi.com> (raw)
Booting up a 2.6.28-rc2 kdump kernel, i observed these
messages at console:
Warning: Core image elf header not found
Kdump: vmcore not initialized
It was a default configuration with a new config flag
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS set to 'y'.
The machine worked fine with 2.6.27.
Regards,
jay
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Jay Lan <jlan@sgi.com>
To: "linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: [IA64] kdump failed to produce vmcore in 2.6.28-rc2
Date: Wed, 29 Oct 2008 00:49:51 +0000 [thread overview]
Message-ID: <4907B32F.4030009@sgi.com> (raw)
Booting up a 2.6.28-rc2 kdump kernel, i observed these
messages at console:
Warning: Core image elf header not found
Kdump: vmcore not initialized
It was a default configuration with a new config flag
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS set to 'y'.
The machine worked fine with 2.6.27.
Regards,
jay
next reply other threads:[~2008-10-29 0:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 0:49 Jay Lan [this message]
2008-10-29 0:49 ` [IA64] kdump failed to produce vmcore in 2.6.28-rc2 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=4907B32F.4030009@sgi.com \
--to=jlan@sgi.com \
--cc=kexec@lists.infradead.org \
--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 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.