From: Bernhard Walle <bwalle@suse.de>
To: jidong xiao <jidong.xiao@gmail.com>
Cc: kexec@lists.infradead.org, linux-ia64@vger.kernel.org
Subject: Re: Zero size vmcore on ia64
Date: Wed, 27 Aug 2008 10:14:43 +0000 [thread overview]
Message-ID: <20080827121443.396d8bac@halley.suse.de> (raw)
In-Reply-To: <4104961b0808270251n1e7250dbn656ae77d2f8bc3d3@mail.gmail.com>
* jidong xiao [2008-08-27 17:51]:
>
> On Wed, Aug 27, 2008 at 5:27 PM, Bernhard Walle <bwalle@suse.de> wrote:
> > Hi Jidong,
> >
> > * jidong xiao [2008-08-27 17:01]:
> >>
> >> I encountered the zero-size-vmcore issue on IA64. I remember last year
> >> Nanhai submitted a patch which was intended to fix this issue, and I
> >> noticed that patch is merged into mainline kernel. I am using
> >> 2.6.27-rc2, which means that patch is included in my kernel.And after
> >> the system
> >> completed rebooting, there is nothing generated in KDUMP_SAVEDIR. Let
> >> me know if I need to provide more information.Thanks.
> >
> > Which version of kexec-tools do you use?
> >
> Well I am using SLES10SP2,(I tried the experiments on SLES10SP2
> default kernel and also 2.6.27-rc2 mainline kernel, result is the
> same.)
With the SP2 default kernel, it should work. At lest /proc/vmcore
should have a normal size. Can you set KDUMP_IMMEDIATE_REBOOT to "no",
then log in in the serial console and execute
# ls -l /proc/vmcore
For 2.6.27 kernel on IA64, you have to update kexec-tools. I don't know
the exact version when the change was included, but 2.0.0 is safe. :)
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
next prev parent reply other threads:[~2008-08-27 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 9:01 Zero size vmcore on ia64 jidong xiao
2008-08-27 9:16 ` jidong xiao
2008-08-27 9:27 ` Bernhard Walle
2008-08-27 9:51 ` jidong xiao
2008-08-27 10:14 ` Bernhard Walle [this message]
2008-08-27 10:54 ` jidong xiao
2008-08-27 11:24 ` Bernhard Walle
2008-08-27 17:07 ` Jay Lan
2008-08-28 4:55 ` jidong xiao
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=20080827121443.396d8bac@halley.suse.de \
--to=bwalle@suse.de \
--cc=jidong.xiao@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox