Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759361Ab3CZD44 (ORCPT ); Mon, 25 Mar 2013 23:56:56 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42585 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753969Ab3CZD4y (ORCPT ); Mon, 25 Mar 2013 23:56:54 -0400 Message-ID: <51511C6A.1000001@redhat.com> Date: Tue, 26 Mar 2013 11:56:26 +0800 From: WANG Chao User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 MIME-Version: 1.0 To: =?UTF-8?B?5ZGo5rSy5Luq?= CC: zhouzhouyi@gmail.com, kexec@lists.infradead.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, vgoyal@redhat.com Subject: Re: [PATCH 1/1 v1] the recommended crash memory reservation is too small for x86_64. References: <5150350A.5050002@redhat.com> <1364209009-11592-1-git-send-email-zhouzhouyi@gmail.com> <1cd75ef.b411.13da1646593.Coremail.yizhouzhou@ict.ac.cn> In-Reply-To: <1cd75ef.b411.13da1646593.Coremail.yizhouzhou@ict.ac.cn> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2715 Lines: 70 On 03/25/2013 07:52 PM, 周洲仪 wrote: > Thanks for reviewing > Is it sounds good to add following line into section "Boot into System Kernel": > > The memory reserved for crash kernel should be no less than the unpacked init ram disk size > that loaded with dump-capture kernel plus wired memory used by kernel itself. Sorry, that is just basic knowledge for everyone. > > ################# > After all, I have been trapped into "hang after capture" problem when sticking strictly to this document. > Cheers > Zhouyi > >> >> On 03/25/2013 06:56 PM, zhouzhouyi@gmail.com wrote: >> > From: root >> > >> > >> > On Documentation/kdump/kdump.txt, section Boot into System Kernel: On x86 and x86_64, use >> > "crashkernel=64M@16M", but some OSes like ubuntu 12.10 use ram fs larger than 64M, so in these cases the >> > memory reserved for crashkernel should be at least 128M. >> >> People use different initramfs generators for different purpose. That means >> the size of initramfs and also its memory consuming can vary very much from >> each other. You just can't list all these generators and their recommended >> reserved memory here. Though I have to say crashkernel=128M is good choice. >> >> I think it would be better to leave this to user or distribution itself to >> determine how much memory should be reserved for crash kernel, then export >> this value to kernel in some ways. >> >> Thanks, >> WANG Chao >> >> > >> > >> > Signed-off-by: Zhouyi Zhou >> > --- >> > Documentation/kdump/kdump.txt | 4 +++- >> > 1 file changed, 3 insertions(+), 1 deletion(-) >> > >> > diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt >> > index 13f1aa0..1e850e0 100644 >> > --- a/Documentation/kdump/kdump.txt >> > +++ b/Documentation/kdump/kdump.txt >> > @@ -290,7 +290,9 @@ Boot into System Kernel >> > "crashkernel=64M@16M" tells the system kernel to reserve 64 MB of memory >> > starting at physical address 0x01000000 (16MB) for the dump-capture kernel. >> > >> > - On x86 and x86_64, use "crashkernel=64M@16M". >> > + On x86 and x86_64, use "crashkernel=64M@16M" (some OSes use init ram fs larger >> > +than 64M, for example ubuntu-12.10, use crashkernel=128M@16M instead, or dump-capture >> > +kernel will out of memory). >> > >> > On ppc64, use "crashkernel=128M@32M". >> > >> > >> > > > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/