linux-kernel - Re: [PATCH 3/3] x86, crash: Allocate enough low-mem when crashkernel=high

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]

Date:	Mon, 9 Feb 2015 13:20:42 +0100
From:	Joerg Roedel <joro@...tes.org>
To:	Joerg Roedel <jroedel@...e.de>
Cc:	Baoquan He <bhe@...hat.com>, Ingo Molnar <mingo@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] x86, crash: Allocate enough low-mem when
 crashkernel=high

Hi Baoquan,

On Wed, Feb 04, 2015 at 03:10:20PM +0100, Joerg Roedel wrote:
> That makes sense. I also asked the customer to test intermediate values,
> we already know that it works with 256MB but also that 128MB are not
> enough. I will report back when I have the results of the intermediate
> values in 32MB steps.

I got the results from the customer, and it turns out that a value of
192MB is sufficient to make the kdump succeed. It fails with 128MB and
160MB. 

So I think we can settle in 192MB for now. What do you think?

Regards,

	Joerg

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/