Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756209Ab0DWHIu (ORCPT ); Fri, 23 Apr 2010 03:08:50 -0400 Received: from ey-out-2122.google.com ([74.125.78.26]:42386 "EHLO ey-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756129Ab0DWHIt convert rfc822-to-8bit (ORCPT ); Fri, 23 Apr 2010 03:08:49 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:message-id:from:to:cc:subject:in-reply-to:references :user-agent:mime-version:content-type:content-transfer-encoding; b=owyFle4LeQtWozzVAQ2MCO91G/cYrwKft/DCUwXSO4PLdtY++Y8QYeAPlZ4O8zulzt NZzwsoMDwvR8gXKp8WE4Q5AZVqUU5MsRkTePsWstXazsjv5HqskfYVx7KUVrt2deU6qf YyzX0qKk8wzgcK0PdmTyxNThFKTenN4DxlnqU= Date: Fri, 23 Apr 2010 09:08:45 +0200 Message-ID: <87y6ge63ya.wl%vmayatsk@redhat.com> From: Vitaly Mayatskikh To: Vivek Goyal Cc: "Eric W. Biederman" , Vitaly Mayatskikh , linux-kernel@vger.kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Haren Myneni , Neil Horman , Cong Wang , kexec@lists.infradead.org Subject: Re: [PATCH 0/5] Add second memory region for crash kernel In-Reply-To: <20100422224525.GJ3228@redhat.com> References: <1271953392-6324-1-git-send-email-v.mayatskih@gmail.com> <20100422224525.GJ3228@redhat.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/23.1 Mule/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") 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: 994 Lines: 22 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/