public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: CAI Qian <caiqian@redhat.com>, Takashi Iwai <tiwai@suse.de>,
	Jay Lan <jay.zen.lan@gmail.com>,
	kexec@lists.infradead.org, xiyou.wangcong@gmail.com,
	Yinghai Lu <yinghai@kernel.org>
Subject: Re: crashkernel reservation failed - No suitable area found
Date: Thu, 24 Jan 2013 09:09:55 -0600	[thread overview]
Message-ID: <51014EC3.7070805@zytor.com> (raw)
In-Reply-To: <20130124150722.GD3010@redhat.com>

On 01/24/2013 09:07 AM, Vivek Goyal wrote:
>>
>> 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!
> 
> I thought Yinghai Lu worked on some patches to make 512MB reservation
> working again. Not sure where these patches are queued and when are
> they scheduled to be pushed into linus tree. 
> 
> hpa, yinghai should know more.
> 

Yes, I am working through what I'm *hoping* will be the final version
now.  If all goes well, they will probably be in -tip late tomorrow and
pushed into the 3.9 kernel.  If all *doesn't* go well, it depends on
what the hangups are.

	-hpa



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

      reply	other threads:[~2013-01-24 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 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=51014EC3.7070805@zytor.com \
    --to=hpa@zytor.com \
    --cc=caiqian@redhat.com \
    --cc=jay.zen.lan@gmail.com \
    --cc=kexec@lists.infradead.org \
    --cc=tiwai@suse.de \
    --cc=vgoyal@redhat.com \
    --cc=xiyou.wangcong@gmail.com \
    --cc=yinghai@kernel.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