From: Daniel Mack <zonque@gmail.com>
To: Naresh Bhat <nareshgbhat@gmail.com>
Cc: magnus.damm@gmail.com, kexec@lists.infradead.org
Subject: Re: KEXEC on ARM Cortex-A15 versatile express V2P
Date: Fri, 14 Dec 2012 21:58:24 +0100 [thread overview]
Message-ID: <50CB92F0.40308@gmail.com> (raw)
In-Reply-To: <CAJXQGfKcqFK7hBiKqEhZzvsGbFi44fFYAF+-L5+f4FQ=2V3pmQ@mail.gmail.com>
Hi,
On 14.12.2012 18:33, Naresh Bhat wrote:
> Thanks for the suggestions. I really appreciate your help.
>
> I have tried the following in my below setup
Your should really fix your mailer. The way you quote makes it
impossible to see which lines you added.
> My setup:
> kexec-tools - latest GIT tree with
> http://lists.infradead.org/pipermail/kexec/2012-December/007526.html
> patch
> Kernel version - 3.4.22
Why are you running a kernel from the middle ages?
> Hardware target - V2P-CA15_A7 Cortex A15 (ARM Versatile Express)
>
> That could be just that the new kernel is missing its bootargs cmdline
> with the appropriate console= tag. How are you booting the first
> kernel?
>
> The first kernel command line console=tty0 console=ttyAMA0,38400n8
> root=/dev/mmcblk0p1 rootwait ro mmci.fmax=6000000
>
> Does you bootloader add a /chosen tag?
>
> I did't understand what you are asking here . can you please
> elaborate little more ?
Bootloaders have two ways of passing the command line to the kernel. The
traditional way is to stuff it into a a linked list of boot parameters
(ATAGs), the other is to fill the /chosen/bootargs property in the
device tree and then pass the entire tree.
> Some suggestions:
>
> 1. Add a static CMDLINE to the second kernel, so it doesn't rely on
> that information being passed from the first on.
>
> root@arm-cortex-a15:~# kexec -l uImage --dtb=vexpress.dtb
> --command-line="console=tty0 console=ttyAMA0,38400n8
> root=/dev/mmcblk0p1 rootwait ro mmci.fmax=6000000"
> root@arm-cortex-a15:~# kexec -e
> Starting new kernel
> Uncompressing Linux...
If that doesn't work, your problem is not related to any cmdline issue,
and I might have midlead you here.
Please try a newer kernel and see if that helps. The kernels I was using
with kexec recently were 3.7-rcX.
HTH,
Daniel
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-12-14 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 17:33 KEXEC on ARM Cortex-A15 versatile express V2P Naresh Bhat
2012-12-14 20:58 ` Daniel Mack [this message]
2012-12-14 21:04 ` Daniel Mack
2013-01-02 13:56 ` Naresh Bhat
2013-01-02 14:32 ` Naresh Bhat
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=50CB92F0.40308@gmail.com \
--to=zonque@gmail.com \
--cc=kexec@lists.infradead.org \
--cc=magnus.damm@gmail.com \
--cc=nareshgbhat@gmail.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