From: Dave Young <dyoung@redhat.com>
To: Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>
Cc: kexec@lists.infradead.org
Subject: Re: ppc64 kexec -p failed
Date: Tue, 08 Nov 2011 14:30:28 +0800 [thread overview]
Message-ID: <4EB8CC84.6090001@redhat.com> (raw)
In-Reply-To: <4EB8C329.1010509@linux.vnet.ibm.com>
On 11/08/2011 01:50 PM, Mahesh Jagannath Salgaonkar wrote:
> On 11/04/2011 12:35 PM, Dave Young wrote:
>> Hi,
Thanks for your reply.
>>
>> When use crashkernel=128M@256M at a ppc64 machine, kexec -p vmlinuz
>> failed with:
>> Could not find a free area of memory of faa448 bytes...
>> Could not find a free area of memory of 142721d bytes...
>>
>> Is this a know issue or Is there limitation of the crashkernel base addr?
>
> On Power, crashkernel base addr must fall inside RMO region. The is
> because ppc64 kernel needs some of its memory in the RMO region. The
> memory ranges below shows that the system has RMO region of size 128M,
> Hence crashkernel base addr @64M should work just fine.
Then what about let kernel reservation just fail with such case? And
better at the same time give out a warning about base addr from cmdline
is out of RMO
Or at least we should add this info into kernel doc.
>
>>
>> Detail info as below (define DEBUG when building):
>>
> ...
> ...
>> 0000000000000000-0000000008000000 : 0
> ...
> ...
>
> Thanks,
> -Mahesh.
>
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
--
Thanks
Dave
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2011-11-08 6:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 7:05 ppc64 kexec -p failed Dave Young
2011-11-08 2:22 ` Dave Young
2011-11-08 14:24 ` Vivek Goyal
2011-11-08 5:50 ` Mahesh Jagannath Salgaonkar
2011-11-08 6:30 ` Dave Young [this message]
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=4EB8CC84.6090001@redhat.com \
--to=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=mahesh@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox