[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130327122856.GK17248@verge.net.au>
Date: Wed, 27 Mar 2013 21:28:57 +0900
From: Simon Horman <horms@...ge.net.au>
To: zhouzhouyi@...il.com
Cc: kexec@...ts.infradead.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, vgoyal@...hat.com,
yizhouzhou@....ac.cn
Subject: Re: [PATCH 1/1 v1] the recommended crash memory reservation is too
small for x86_64.
On Mon, Mar 25, 2013 at 06:56:49PM +0800, zhouzhouyi@...il.com wrote:
> From: root <root@...-Lenovo.(none)>
The above line is bogus.
> 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.
The above lines are way to wide. Something less than 80 columns is normal.
> Signed-off-by: Zhouyi Zhou <yizhouzhou@....ac.cn>
> ---
> 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).
I believe lines of kdmump.txt should also be 80 columns wide or less.
> On ppc64, use "crashkernel=128M@32M".
>
> --
> 1.7.10.4
>
>
> _______________________________________________
> kexec mailing list
> kexec@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
>
--
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/
Powered by blists - more mailing lists