public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Jay Lan <jay.zen.lan@gmail.com>
To: kexec@lists.infradead.org
Cc: Takashi Iwai <tiwai@suse.de>,
	xiyou.wangcong@gmail.com, CAI Qian <caiqian@redhat.com>,
	vgoyal@redhat.com, hpa@zytor.com
Subject: crashkernel reservation failed - No suitable area found
Date: Wed, 23 Jan 2013 18:06:26 -0800	[thread overview]
Message-ID: <51009722.40600@gmail.com> (raw)

Hi,

I searched the web on this subject, and found a discussion thread
on this matter back in March 12, 2012:
     https://lkml.org/lkml/2012/3/13/36
and it seems I hit the same problem on my machine. :-(

We have a system with 4TB memory. When it was shipped, crashkernel
was set to 512M. The crashkernel memory reservation was successful,
but dumping core ran out of memory.  The system runs sles11sp2,
3.0.51-0.7.9.1.

After I tried to raise the reserved memory to 896M, the system started
to fail reserving the requested memory, even after I set it back to 512M:
     crashkernel reservation failed - No suitable area found

Is there a kernel/kexec-tools patch to address this problem in kernel 3.x
yet? Also, according to Takashi Iwa wrote, "the problem does not happen
always. However, once this happens, it continues to happen" :-(
Yes, yes, it drove me completely crazy trying to figure out how to get the
system out of this trapped state! Please help!

Thanks for any help!

Jay



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

             reply	other threads:[~2013-01-24  2:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24  2:06 Jay Lan [this message]
2013-01-24 15:07 ` crashkernel reservation failed - No suitable area found Vivek Goyal
2013-01-24 15:09   ` H. Peter Anvin

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=51009722.40600@gmail.com \
    --to=jay.zen.lan@gmail.com \
    --cc=caiqian@redhat.com \
    --cc=hpa@zytor.com \
    --cc=kexec@lists.infradead.org \
    --cc=tiwai@suse.de \
    --cc=vgoyal@redhat.com \
    --cc=xiyou.wangcong@gmail.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