From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Message-ID: <51658B1A.6090706@wwwdotorg.org> Date: Wed, 10 Apr 2013 09:54:02 -0600 From: Stephen Warren MIME-Version: 1.0 Subject: Re: Kexec couldn't reboot capture kernel on pandaboard ES with OMAP4460 References: In-Reply-To: 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=twosheds.infradead.org@lists.infradead.org To: Li Haifeng Cc: linux-omap@vger.kernel.org, pandaboard@googlegroups.com, kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org On 04/10/2013 03:35 AM, Li Haifeng wrote: > Hi, everyone. > > Recently, I try to run kdump on pandaboard ES with omap4460. After > load capture kernel by "kexec -l" and execute "kexec -e", the serial > port output "Starting new kernel" and "Bye", then the system hangs up. > > I have tried the upstream Linux Kernel v3.4 and v3.8. All are with this issue. This is a shot in the dark. I assume you have SMP enabled. Can you use hotplug to remove all CPUs other than CPU0, so that the kexec happens on the boot CPU? That is certainly necessary for kexec to work correctly on Tegra. _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: Kexec couldn't reboot capture kernel on pandaboard ES with OMAP4460 Date: Wed, 10 Apr 2013 09:54:02 -0600 Message-ID: <51658B1A.6090706@wwwdotorg.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from avon.wwwdotorg.org ([70.85.31.133]:59283 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934856Ab3DJPyH (ORCPT ); Wed, 10 Apr 2013 11:54:07 -0400 In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Li Haifeng Cc: pandaboard@googlegroups.com, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kexec@lists.infradead.org On 04/10/2013 03:35 AM, Li Haifeng wrote: > Hi, everyone. > > Recently, I try to run kdump on pandaboard ES with omap4460. After > load capture kernel by "kexec -l" and execute "kexec -e", the serial > port output "Starting new kernel" and "Bye", then the system hangs up. > > I have tried the upstream Linux Kernel v3.4 and v3.8. All are with this issue. This is a shot in the dark. I assume you have SMP enabled. Can you use hotplug to remove all CPUs other than CPU0, so that the kexec happens on the boot CPU? That is certainly necessary for kexec to work correctly on Tegra. From mboxrd@z Thu Jan 1 00:00:00 1970 From: swarren@wwwdotorg.org (Stephen Warren) Date: Wed, 10 Apr 2013 09:54:02 -0600 Subject: Kexec couldn't reboot capture kernel on pandaboard ES with OMAP4460 In-Reply-To: References: Message-ID: <51658B1A.6090706@wwwdotorg.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 04/10/2013 03:35 AM, Li Haifeng wrote: > Hi, everyone. > > Recently, I try to run kdump on pandaboard ES with omap4460. After > load capture kernel by "kexec -l" and execute "kexec -e", the serial > port output "Starting new kernel" and "Bye", then the system hangs up. > > I have tried the upstream Linux Kernel v3.4 and v3.8. All are with this issue. This is a shot in the dark. I assume you have SMP enabled. Can you use hotplug to remove all CPUs other than CPU0, so that the kexec happens on the boot CPU? That is certainly necessary for kexec to work correctly on Tegra.