From: Xunlei Pang <xpang@redhat.com>
To: Robert LeBlanc <robert@leblancnet.us>, xlpang@redhat.com
Cc: kexec@lists.infradead.org,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
Baoquan He <bhe@redhat.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Add +~800M crashkernel explaination
Date: Thu, 12 Jan 2017 11:24:17 +0800 [thread overview]
Message-ID: <5876F6E1.4050001@redhat.com> (raw)
In-Reply-To: <CAANLjFpbk=jNi4xxqo+YGWwGic3OAAWbcmb_rCTNZ7VsZML2SQ@mail.gmail.com>
On 01/12/2017 at 03:35 AM, Robert LeBlanc wrote:
> On Wed, Dec 14, 2016 at 4:17 PM, Xunlei Pang <xpang@redhat.com> wrote:
>> As I replied in another post, if you really want to detail the behaviour, should mention
>> "crashkernel=size[KMG][@offset[KMG]]" with @offset[KMG] specified explicitly, after
>> all, it's handled differently with no upper bound limitation, but doing this may put
>> the first kernel at the risk of lacking low memory(some devices require 32bit DMA),
>> must use it with care because the kernel will assume users are aware of what they
>> are doing and make a successful reservation as long as the given range is available.
> crashkernel=1024M@0x10000000
>
> I can't get the offset to work. It seems that it allocates the space
> and loads the crash kernel, but I couldn't get it to actually boot
> into the crash kernel. Does it work for you? I'm using the 4.9 kernel.
Not sure what is the problem you met, but kdump kernel boots well using 4.9 on my x86_64 machine.
Regards,
Xunlei
prev parent reply other threads:[~2017-01-12 3:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 0:22 [PATCH] Add +~800M crashkernel explaination Robert LeBlanc
2016-12-10 2:49 ` Baoquan He
2016-12-10 5:20 ` Robert LeBlanc
2016-12-14 3:08 ` Xunlei Pang
2016-12-14 3:23 ` Xunlei Pang
2016-12-14 17:50 ` Robert LeBlanc
2016-12-14 23:17 ` Xunlei Pang
2017-01-11 19:35 ` Robert LeBlanc
2017-01-12 3:24 ` Xunlei Pang [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=5876F6E1.4050001@redhat.com \
--to=xpang@redhat.com \
--cc=bhe@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert@leblancnet.us \
--cc=xlpang@redhat.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;
as well as URLs for NNTP newsgroup(s).