public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Li Haifeng <omycle@gmail.com>
Cc: linux-omap@vger.kernel.org, pandaboard@googlegroups.com,
	kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org
Subject: Re: Kexec couldn't reboot capture kernel on pandaboard ES with OMAP4460
Date: Wed, 10 Apr 2013 09:54:02 -0600	[thread overview]
Message-ID: <51658B1A.6090706@wwwdotorg.org> (raw)
In-Reply-To: <CAFNq8R5FFUyH+JgjoGc5ctgEfiLvxzi7fzawM7+wFX5nEyTv-w@mail.gmail.com>

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

  reply	other threads:[~2013-04-10 15:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  9:35 Kexec couldn't reboot capture kernel on pandaboard ES with OMAP4460 Li Haifeng
2013-04-10 15:54 ` Stephen Warren [this message]
2013-04-11  4:46   ` Li Haifeng
2013-04-11 16:19     ` Stephen Warren
2013-04-12 10:45       ` Will Deacon
2013-04-12 15:22         ` Stephen Warren

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=51658B1A.6090706@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=omycle@gmail.com \
    --cc=pandaboard@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox