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-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: Kexec couldn't reboot capture kernel on pandaboard ES with OMAP4460
Date: Thu, 11 Apr 2013 10:19:21 -0600 [thread overview]
Message-ID: <5166E289.8070104@wwwdotorg.org> (raw)
In-Reply-To: <CAFNq8R6mRJRygfnYvZgwVWOqsrhrjNUYzyZGU0cVsnE30W_xGg@mail.gmail.com>
On 04/10/2013 10:46 PM, Li Haifeng wrote:
> 2013/4/10 Stephen Warren <swarren@wwwdotorg.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.
>
> 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!
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Li Haifeng <omycle@gmail.com>
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
Date: Thu, 11 Apr 2013 10:19:21 -0600 [thread overview]
Message-ID: <5166E289.8070104@wwwdotorg.org> (raw)
In-Reply-To: <CAFNq8R6mRJRygfnYvZgwVWOqsrhrjNUYzyZGU0cVsnE30W_xGg@mail.gmail.com>
On 04/10/2013 10:46 PM, Li Haifeng wrote:
> 2013/4/10 Stephen Warren <swarren@wwwdotorg.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.
>
> 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!
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: Kexec couldn't reboot capture kernel on pandaboard ES with OMAP4460
Date: Thu, 11 Apr 2013 10:19:21 -0600 [thread overview]
Message-ID: <5166E289.8070104@wwwdotorg.org> (raw)
In-Reply-To: <CAFNq8R6mRJRygfnYvZgwVWOqsrhrjNUYzyZGU0cVsnE30W_xGg@mail.gmail.com>
On 04/10/2013 10:46 PM, Li Haifeng wrote:
> 2013/4/10 Stephen Warren <swarren@wwwdotorg.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.
>
> 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!
next prev parent reply other threads:[~2013-04-11 16:19 UTC|newest]
Thread overview: 19+ 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 9:35 ` Li Haifeng
2013-04-10 9:35 ` Li Haifeng
2013-04-10 15:54 ` Stephen Warren
2013-04-10 15:54 ` Stephen Warren
2013-04-10 15:54 ` Stephen Warren
2013-04-11 4:46 ` Li Haifeng
2013-04-11 4:46 ` Li Haifeng
2013-04-11 4:46 ` Li Haifeng
2013-04-11 16:19 ` Stephen Warren [this message]
2013-04-11 16:19 ` Stephen Warren
2013-04-11 16:19 ` Stephen Warren
2013-04-12 10:45 ` Will Deacon
2013-04-12 10:45 ` Will Deacon
2013-04-12 10:45 ` Will Deacon
2013-04-12 15:22 ` Stephen Warren
2013-04-12 15:22 ` Stephen Warren
2013-04-12 15:22 ` Stephen Warren
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=5166E289.8070104@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.