From: Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>
To: kexec@lists.infradead.org
Subject: Re: IO memory read from /proc/vmcore leads to hang.
Date: Fri, 15 Jul 2016 12:53:57 +0530 [thread overview]
Message-ID: <bcc40ddc-885e-a61d-e900-90fab3c0de29@linux.vnet.ibm.com> (raw)
In-Reply-To: <57841399.1030703@cisco.com>
On 07/12/2016 03:16 AM, Daniel Walker wrote:
>
> Hi,
>
> I found found that on my Powerpc machine there is some IO memory which
> will cause the box to hang if I read it. It's a custom device that was
> added to the board for a special purpose.
>
> I was looking for a way to exclude this memory from the dump, and while
> doing that I found that kexec makes a list of memory segments that go
> into the core file. I was wondering why most of the kexec architecture
> don't appear to exclude device memory like what's listed in /proc/iomem.
>
> Is there a good reason why that's not the case?
Kexec/Kdump is designed to capture entire old kernel's memory that will
be available in /proc/vmcore. There is a different userspace tool called
'makedumpfile' (https://sourceforge.net/projects/makedumpfile/), which
can be used to exclude certain memory pages from the dump while reading
from /proc/vmcore. See if that helps you.
Thanks,
-Mahesh.
>
> Daniel
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-07-15 7:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 21:46 IO memory read from /proc/vmcore leads to hang Daniel Walker
2016-07-15 7:23 ` Mahesh Jagannath Salgaonkar [this message]
2016-07-20 19:18 ` Daniel Walker
2016-07-21 7:34 ` Maxim Uvarov
2016-07-21 15:19 ` Daniel Walker
2016-07-21 19:33 ` Maxim Uvarov
2016-07-21 20:04 ` Daniel Walker
2016-07-22 11:11 ` Maxim Uvarov
2016-07-25 17:06 ` Daniel Walker
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=bcc40ddc-885e-a61d-e900-90fab3c0de29@linux.vnet.ibm.com \
--to=mahesh@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).