Re: [PATCH] Add +~800M crashkernel explaination

From	Xunlei Pang <xpang@redhat.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH] Add +~800M crashkernel explaination
Date	2017-01-12 04:30 +0100
Message-ID	<sYEfo-7bu-9@gated-at.bofh.it> (permalink)
References	(2 earlier) <sMIoq-4xC-25@gated-at.bofh.it> <sO877-14y-9@gated-at.bofh.it> <sOm0q-1bT-33@gated-at.bofh.it> <sOr06-6CZ-19@gated-at.bofh.it> <sYwUx-2va-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: [PATCH] Add +~800M crashkernel explaination Robert LeBlanc <robert@leblancnet.us> - 2017-01-11 20:40 +0100
  Re: [PATCH] Add +~800M crashkernel explaination Xunlei Pang <xpang@redhat.com> - 2017-01-12 04:30 +0100

csiph-web