From: WANG Cong <xiyou.wangcong@gmail.com>
To: kexec@lists.infradead.org
Subject: Re: Kexec & Memory Zones question
Date: Tue, 10 May 2011 09:42:11 +0000 (UTC) [thread overview]
Message-ID: <iqb19j$e10$1@dough.gmane.org> (raw)
In-Reply-To: BANLkTinOd+kmJKMdtW7saW0eWHN9xbO_3w@mail.gmail.com
On Wed, 04 May 2011 11:35:46 -0700, Sujit V wrote:
> On our x86_64 NUMA hardware running linux 2.6.23 with two memory nodes
> have the following zone layout
> DMA 0 - 16MB
> DMA32 16MB to 4GB
> NORMAL 4GB to 96GB
>
> We had the crashkernel boot param as 128M@16M. I am using
> kexec-tools-2.0.0
>
> We observed that the reserved crashkernel memory was getting used by the
> system.
> We found out by kdb that around 17MB of physical memory the memory
> contents were changing which proved that the system was using the memory
> which is actually reserved for crash kernel. [ If I load crash kernel
> using kexec then the system would crash. The back trace was always in
> the megasas driver. ]
>
> My Question is
> 1) Should the crashkernel memory be located past the DMA32 zone.?
Your DMA32 zone looks extremely large, probably due to you enabled NUMA?
What does dmesg say if possible? Also, what is your kernel version?
>
> I have tried the following
> (1) crashkernel=128M@4GB ( So the memory reservation is past DMA32) In
> this scenario the kexec tools gave an error "Could not find a free area
> of memory of xyz bytes"
>
> (2) I changed the max of DMA32 to 1GB
> crashkernel=128M@1G
> Still kexec gave the same error "Could not find a free area of memory of
> xyz bytes"
>
> Is there any specific restriction on where the crashkernel memory could
> be located.?
No, have you tried "crashkernel=128M@0"? Can that reserve the memory
successfully?
>
> Is it ok to be in the DMA32 region OR it should be beyond the DMA32
> region.
>
The reserve memory is unseen by the first kernel nor it should be used,
even if it is in DMA32 zone.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2011-05-10 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 18:35 Kexec & Memory Zones question Sujit V
2011-05-10 9:42 ` WANG Cong [this message]
2011-05-11 15:09 ` Vivek Goyal
2011-05-12 10:03 ` WANG Cong
2011-05-18 2:05 ` Sujit V
2011-05-18 2:40 ` WANG Cong
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='iqb19j$e10$1@dough.gmane.org' \
--to=xiyou.wangcong@gmail.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