All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <danielwa@cisco.com>
To: Maxim Uvarov <muvarov@gmail.com>
Cc: "xe-kernel@external.cisco.com" <xe-kernel@external.cisco.com>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: IO memory read from /proc/vmcore leads to hang.
Date: Thu, 21 Jul 2016 08:19:43 -0700	[thread overview]
Message-ID: <5790E80F.7080109@cisco.com> (raw)
In-Reply-To: <CAJGZr0KwbB+2Qdv4AAp1qVr60PQPGiJqQum5awSFrptATmHYUA@mail.gmail.com>


  There appears to be no code which checks what is or is not System ram, 
there is nothing that checks the device tree to see what is IO memory, 
and nothing reads /proc/iomem .. So AFAIK nothing cares if it's IO 
memory, or system ram, and there's no method to config things to skip 
any memory in the system, except in makedumpfile which can skip symbols 
not IO memory.


On 07/21/2016 12:34 AM, Maxim Uvarov wrote:
> Second kernel should already know that it's not system ram of the
> first kernel and in that case makedumpfile will not dump that memory.
> Simple way is to pass additional kernel argument to kexec is when you
> load the kernel. If it works than you can think how it's better to
> pass this parameter.  Variants might be request_resource() in first
> kernel or add some logic to kexec tools.
>
> Best regards,
> Maxim.
>
> 2016-07-20 22:18 GMT+03:00 Daniel Walker <danielwa@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
>
>


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2016-07-21 15:20 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
2016-07-21  7:34   ` Maxim Uvarov
2016-07-21 15:19     ` Daniel Walker [this message]
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=5790E80F.7080109@cisco.com \
    --to=danielwa@cisco.com \
    --cc=kexec@lists.infradead.org \
    --cc=muvarov@gmail.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.