Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754123Ab3DKQTZ (ORCPT ); Thu, 11 Apr 2013 12:19:25 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:36686 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752270Ab3DKQTY (ORCPT ); Thu, 11 Apr 2013 12:19:24 -0400 Message-ID: <5166E289.8070104@wwwdotorg.org> Date: Thu, 11 Apr 2013 10:19:21 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Li Haifeng CC: pandaboard@googlegroups.com, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: Kexec couldn't reboot capture kernel on pandaboard ES with OMAP4460 References: <51658B1A.6090706@wwwdotorg.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1423 Lines: 35 On 04/10/2013 10:46 PM, Li Haifeng wrote: > 2013/4/10 Stephen Warren : >> 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. > > Thanks for your attention. > > I do disable SMP feature. And the .config file for v3.8 could be found here: > http://pastehtml.com/view/cylyrfejt.txt ... > The output: > [ 57.373687] Starting new kernel > [ 57.377044] Bye! > > Then system hangs. Oh well, you've exhausted my knowledge I'm afraid! I can only suggesting trying to enable earlyprintk and/or uncompressor debug in the kernel you're kexec'ing and see if that yields any clue. Either that, or JTAG! -- 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/