public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
* crashkernel reservation failed - No suitable area found
@ 2013-01-24  2:06 Jay Lan
  2013-01-24 15:07 ` Vivek Goyal
  0 siblings, 1 reply; 3+ messages in thread
From: Jay Lan @ 2013-01-24  2:06 UTC (permalink / raw)
  To: kexec; +Cc: Takashi Iwai, xiyou.wangcong, CAI Qian, vgoyal, hpa

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-01-24 15:10 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-24  2:06 crashkernel reservation failed - No suitable area found Jay Lan
2013-01-24 15:07 ` Vivek Goyal
2013-01-24 15:09   ` H. Peter Anvin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox