From: Bernhard Walle <bwalle@suse.de>
To: kexec@lists.infradead.org
Cc: jlan@sgi.com
Subject: Re: IA64: copying /proc/vmcore caused kernel MCA'ed
Date: Tue, 9 Sep 2008 10:19:00 +0200 [thread overview]
Message-ID: <20080909101900.76f843ec@kepler.site> (raw)
In-Reply-To: <48C56F55.5000503@sgi.com>
* Jay Lan <jlan@sgi.com> [2008-09-08]:
> Any input helping me speed up debugging is appreciated.
I would start with comparing the ELF program headers of /proc/vmcore
which you get with "readelf -l /proc/vmcore" in kdump environment and
the /proc/iomem which kexec uses to set up the ELF core headers.
If both does contain the memory regions which should not be accessed,
then it's a bug in the ressource assignment of the kernel, and
if /proc/iomem does not, the kexec tool has a bug.
Hope that helps a bit, I don't have time to look deeper into that now.
Bernhard
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-09-09 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 18:30 IA64: copying /proc/vmcore caused kernel MCA'ed Jay Lan
2008-09-09 8:19 ` Bernhard Walle [this message]
2008-09-09 16:03 ` Jay Lan
2008-09-09 16:22 ` Bernhard Walle
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=20080909101900.76f843ec@kepler.site \
--to=bwalle@suse.de \
--cc=jlan@sgi.com \
--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 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.