From: Vitaly Mayatskikh <v.mayatskih@gmail.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Vitaly Mayatskikh <v.mayatskih@gmail.com>,
Cong Wang <amwang@redhat.com>,
Neil Horman <nhorman@tuxdriver.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Haren Myneni <hbabu@us.ibm.com>, Ingo Molnar <mingo@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/5] Add second memory region for crash kernel
Date: Fri, 23 Apr 2010 09:08:45 +0200 [thread overview]
Message-ID: <87y6ge63ya.wl%vmayatsk@redhat.com> (raw)
In-Reply-To: <20100422224525.GJ3228@redhat.com>
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
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Vitaly Mayatskikh <v.mayatskih@gmail.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Vitaly Mayatskikh <v.mayatskih@gmail.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Haren Myneni <hbabu@us.ibm.com>,
Neil Horman <nhorman@tuxdriver.com>,
Cong Wang <amwang@redhat.com>,
kexec@lists.infradead.org
Subject: Re: [PATCH 0/5] Add second memory region for crash kernel
Date: Fri, 23 Apr 2010 09:08:45 +0200 [thread overview]
Message-ID: <87y6ge63ya.wl%vmayatsk@redhat.com> (raw)
In-Reply-To: <20100422224525.GJ3228@redhat.com>
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
next prev parent reply other threads:[~2010-04-23 7:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 16:23 [PATCH 0/5] Add second memory region for crash kernel Vitaly Mayatskikh
2010-04-22 16:23 ` Vitaly Mayatskikh
2010-04-22 16:23 ` [PATCH 1/5] Introduce second memory resource " Vitaly Mayatskikh
2010-04-22 16:23 ` Vitaly Mayatskikh
2010-04-22 16:23 ` [PATCH 2/5] Modify parse_crashkernel* for new syntax Vitaly Mayatskikh
2010-04-22 16:23 ` Vitaly Mayatskikh
2010-04-22 16:23 ` [PATCH 3/5] Support second memory region in crash_shrink_memory() Vitaly Mayatskikh
2010-04-22 16:23 ` Vitaly Mayatskikh
2010-04-22 16:23 ` [PATCH 4/5] x86: use second memory region for dump-capture kernel Vitaly Mayatskikh
2010-04-22 16:23 ` Vitaly Mayatskikh
2010-04-22 16:23 ` [PATCH 5/5] kexec: update documentation Vitaly Mayatskikh
2010-04-22 16:23 ` Vitaly Mayatskikh
2010-04-22 22:07 ` [PATCH 0/5] Add second memory region for crash kernel Eric W. Biederman
2010-04-22 22:07 ` Eric W. Biederman
2010-04-22 22:37 ` H. Peter Anvin
2010-04-22 22:37 ` H. Peter Anvin
2010-04-22 22:45 ` Vivek Goyal
2010-04-22 22:45 ` Vivek Goyal
2010-04-23 0:48 ` Eric W. Biederman
2010-04-23 0:48 ` Eric W. Biederman
2010-04-23 5:21 ` Cong Wang
2010-04-23 5:21 ` Cong Wang
2010-04-23 5:42 ` Eric W. Biederman
2010-04-23 5:42 ` Eric W. Biederman
2010-04-23 6:43 ` Vitaly Mayatskikh
2010-04-23 6:43 ` Vitaly Mayatskikh
2010-04-23 14:44 ` Vivek Goyal
2010-04-23 14:44 ` Vivek Goyal
2010-04-23 7:08 ` Vitaly Mayatskikh [this message]
2010-04-23 7:08 ` Vitaly Mayatskikh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y6ge63ya.wl%vmayatsk@redhat.com \
--to=v.mayatskih@gmail.com \
--cc=amwang@redhat.com \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nhorman@tuxdriver.com \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.