From: Daniel Walker <danielwa@cisco.com>
To: kexec@lists.infradead.org,
"xe-kernel@external.cisco.com" <xe-kernel@external.cisco.com>,
mahesh@linux.vnet.ibm.com
Subject: Re: IO memory read from /proc/vmcore leads to hang.
Date: Wed, 20 Jul 2016 12:18:50 -0700 [thread overview]
Message-ID: <578FCE9A.50305@cisco.com> (raw)
In-Reply-To: <57841399.1030703@cisco.com>
Mahesh, I didn't get your email for some reason . I saw it in the Archives.
makedumpfile doesn't appear to have a way to drop free form memory
areas. So I need to drop 00800000 to 00807fff , but I don't see a way to
do that. Any other suggestions on how to prevent this hang ?
On 07/11/2016 02:46 PM, 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?
>
> Daniel
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-07-20 19:19 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
2016-07-20 19:18 ` Daniel Walker [this message]
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=578FCE9A.50305@cisco.com \
--to=danielwa@cisco.com \
--cc=kexec@lists.infradead.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=xe-kernel@external.cisco.com \
/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.