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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAANLjFpbk=jNi4xxqo+YGWwGic3OAAWbcmb_rCTNZ7VsZML2SQ@mail.gmail.com>
Date:   Wed, 11 Jan 2017 12:35:55 -0700
From:   Robert LeBlanc <robert@...lancnet.us>
To:     xlpang@...hat.com
Cc:     kexec@...ts.infradead.org,
        "Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
        Baoquan He <bhe@...hat.com>, linux-doc@...r.kernel.org
Subject: Re: [PATCH] Add +~800M crashkernel explaination

On Wed, Dec 14, 2016 at 4:17 PM, Xunlei Pang <xpang@...hat.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@...0000000

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.

Thanks

----------------
Robert LeBlanc
PGP Fingerprint 79A2 9CA4 6CC4 45DD A904  C70E E654 3BB2 FA62 B9F1