From: Bernhard Walle <bwalle@suse.de>
To: kexec@lists.infradead.org
Subject: Re: kdump: quad core Opteron
Date: Tue, 7 Oct 2008 15:06:36 +0200 [thread overview]
Message-ID: <20081007150636.287cc364@halley.suse.de> (raw)
In-Reply-To: <48EB5B68.8010401@in.ibm.com>
* Chandru [2008-10-07 18:21]:
>
> kdump on a quad core Opteron blade machine doesn't give a complete
> vmcore on the system. All works well until we attempt to copy
> /proc/vmcore to some target place ( disk , n/w ). The system immediately
> resets without any OS messages after having copied few mb's of vmcore
> file. Problem also occurs with 2.6.27-rc8 and latest kexec-tools. If
> we pass 'mem=4G' as boot parameter to the first kernel, then kdump
> succeeds in copying a readable vmcore to /var/crash.
Maybe extend the copy process to print out the address, and then look
at which address it crashes. Then look in the memory map, maybe there's
something special there.
Regards,
Bernhard
--
Bernhard Walle, SUSE Linux Products GmbH, Architecture Development
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-10-07 13:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 12:51 kdump: quad core Opteron Chandru
2008-10-07 13:06 ` Bernhard Walle [this message]
2008-10-07 13:24 ` Vivek Goyal
2008-10-07 15:59 ` Bob Montgomery
2008-10-08 13:51 ` Chandru
2008-12-08 15:56 ` Chandru
2008-12-08 21:54 ` Vivek Goyal
2008-12-09 12:12 ` Chandru
2008-12-09 18:55 ` Bob Montgomery
2008-12-08 23:35 ` Bob Montgomery
2008-12-09 1:32 ` Neil Horman
2008-12-09 11:59 ` Chandru
2008-10-08 13:40 ` Chandru
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=20081007150636.287cc364@halley.suse.de \
--to=bwalle@suse.de \
--cc=kexec@lists.infradead.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