[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y6ge63ya.wl%vmayatsk@redhat.com>
Date: Fri, 23 Apr 2010 09:08:45 +0200
From: Vitaly Mayatskikh <v.mayatskih@...il.com>
To: Vivek Goyal <vgoyal@...hat.com>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
Vitaly Mayatskikh <v.mayatskih@...il.com>,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Haren Myneni <hbabu@...ibm.com>,
Neil Horman <nhorman@...driver.com>,
Cong Wang <amwang@...hat.com>, kexec@...ts.infradead.org
Subject: Re: [PATCH 0/5] Add second memory region for crash kernel
At Thu, 22 Apr 2010 18:45:25 -0400, Vivek Goyal wrote:
> Vitaly, have you really run into cases where 2G upper limit is a concern.
> What is the configuration you have, how much memory it has and how much
> memory are you planning to reserve for kdump kernel?
I tried it on system with 96G of RAM. When I reserved 512M for kdump
kernel, system stopped loading somewhere in user space. With larger
reserved area /sbin/kexec can't load kernel (because of hardcoded
limitation in /sbin/kexec). After removing this limitation kernel was
loaded below 2G, but system even hasn't booted.
Unfortunately, I don't remember exact details now and have no access
to that machine temporarily. Will try to get access and come back with
details.
--
wbr, Vitaly
--
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