From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc Zyngier Subject: Re: [Bug Report] kdump crashes after latest EFI memblock changes on arm64 machines with large number of CPUs Date: Mon, 5 Nov 2018 11:31:37 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Language: en-GB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "kexec" Errors-To: kexec-bounces+glkk-kexec=m.gmane.org-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org To: Ard Biesheuvel , Bhupesh Sharma Cc: Mark Rutland , linux-efi , kexec mailing list , Will Deacon , Bhupesh SHARMA , linux-arm-kernel List-Id: linux-efi@vger.kernel.org On 05/11/18 11:11, Ard Biesheuvel wrote: > (+ Marc) > > On 1 November 2018 at 22:14, Bhupesh Sharma wrote: >> Hi, >> >> With the latest EFI changes for memblock reservation across kdump >> kernel from Ard (Commit 71e0940d52e107748b270213a01d3b1546657d74 >> ["efi: honour memory reservations passed via a linux specific config >> table"]), we hit a panic while trying to boot the kdump kernel on >> machines which have large number of CPUs. >> > > Just for my understanding: why do you boot all 224 CPus when running > the crash kernel? FWIW, I've used these patches to kexec a kernel on a 256 CPUs system, without any issue. Why am I not seeing this problem? Thanks, M. -- Jazz is not dead. It just smells funny... From mboxrd@z Thu Jan 1 00:00:00 1970 From: marc.zyngier@arm.com (Marc Zyngier) Date: Mon, 5 Nov 2018 11:31:37 +0000 Subject: [Bug Report] kdump crashes after latest EFI memblock changes on arm64 machines with large number of CPUs In-Reply-To: References: Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 05/11/18 11:11, Ard Biesheuvel wrote: > (+ Marc) > > On 1 November 2018 at 22:14, Bhupesh Sharma wrote: >> Hi, >> >> With the latest EFI changes for memblock reservation across kdump >> kernel from Ard (Commit 71e0940d52e107748b270213a01d3b1546657d74 >> ["efi: honour memory reservations passed via a linux specific config >> table"]), we hit a panic while trying to boot the kdump kernel on >> machines which have large number of CPUs. >> > > Just for my understanding: why do you boot all 224 CPus when running > the crash kernel? FWIW, I've used these patches to kexec a kernel on a 256 CPUs system, without any issue. Why am I not seeing this problem? Thanks, M. -- Jazz is not dead. It just smells funny... From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Subject: Re: [Bug Report] kdump crashes after latest EFI memblock changes on arm64 machines with large number of CPUs References: From: Marc Zyngier Message-ID: Date: Mon, 5 Nov 2018 11:31:37 +0000 MIME-Version: 1.0 In-Reply-To: Content-Language: en-GB List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Ard Biesheuvel , Bhupesh Sharma Cc: Mark Rutland , linux-efi , kexec mailing list , Will Deacon , Bhupesh SHARMA , linux-arm-kernel On 05/11/18 11:11, Ard Biesheuvel wrote: > (+ Marc) > > On 1 November 2018 at 22:14, Bhupesh Sharma wrote: >> Hi, >> >> With the latest EFI changes for memblock reservation across kdump >> kernel from Ard (Commit 71e0940d52e107748b270213a01d3b1546657d74 >> ["efi: honour memory reservations passed via a linux specific config >> table"]), we hit a panic while trying to boot the kdump kernel on >> machines which have large number of CPUs. >> > > Just for my understanding: why do you boot all 224 CPus when running > the crash kernel? FWIW, I've used these patches to kexec a kernel on a 256 CPUs system, without any issue. Why am I not seeing this problem? Thanks, M. -- Jazz is not dead. It just smells funny... _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec