From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Running kexec on mx6
Date: Fri, 12 Jun 2015 15:01:23 +0100 [thread overview]
Message-ID: <20150612140123.GA7557@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOMZO5A0+SSdT5mfy7fmO4DUQKimQpFCSu16EVLkxR+qh6137A@mail.gmail.com>
On Fri, Jun 12, 2015 at 10:53:13AM -0300, Fabio Estevam wrote:
> On Thu, Jun 11, 2015 at 9:08 PM, Fabio Estevam <festevam@gmail.com> wrote:
> > Hi,
> >
> > I am trying to load a kernel and dtb via kexec on a mx6solo wandboard
> > board running 4.1-rc7:
> >
> > root at wandboard-solo:~# kexec -d -l /mnt/zImage --dtb /mnt/imx6dl-wandboard.dtb -
> > -command-line="console=ttymxc0,115200 root=/dev/mmcblk2p2 rootwait rw"
> > my_load:667: do
> > kernel: 0x75da4008 kernel_size: 0x5be000
> > kexec_load: entry = 0x10008000 flags = 0x280000
> > nr_segments = 2
> > segment[0].buf = 0x75da4008
> > segment[0].bufsz = 0x5be000
> > segment[0].mem = 0x10008000
> > segment[0].memsz = 0x5be000
> > segment[1].buf = 0x1ce9008
> > segment[1].bufsz = 0x6c87
> > segment[1].mem = 0x116f9000
> > segment[1].memsz = 0x7000
> > root at wandboard-solo:~# kexec -e
> > [ 62.581795] kexec: Starting new kernel
> > [ 62.585570] Disabling non-boot CPUs ...
> > [ 62.589485] Bye!
> >
> > And then nothing comes out.
>
> If I use a 4.1-rc7 to be loaded via kexec then I get the
> "Uncompressing Linux... done, booting the kernel" message.
>
> Initially I was loading a 3.10 kernel from a running 4.1-rc7.
>
> Now I see:
>
> root at wandboard-solo:~# kexec -d -l /tmp/zImage --dtb /tmp/imx6dl-wandboard.dtb -
> -command-line="console=ttymxc0,115200 root=/dev/mmcblk0p2 rootwait rw"
> my_load:667: do
> kernel: 0x75d95008 kernel_size: 0x5c99d8
> kexec_load: entry = 0x10008000 flags = 0x280000
> nr_segments = 2
> segment[0].buf = 0x75d95008
> segment[0].bufsz = 0x5c99d8
> segment[0].mem = 0x10008000
> segment[0].memsz = 0x5ca000
> segment[1].buf = 0x1f4008
> segment[1].bufsz = 0x6d63
> segment[1].mem = 0x11728000
> segment[1].memsz = 0x7000
> root at wandboard-solo:~# kexec -e
> [ 27.591555] kexec: Starting new kernel
> [ 27.595331] Disabling non-boot CPUs ...
> [ 27.599250] Bye!
> Uncompressing Linux... done, booting the kernel.
Has it ever worked, or is this a regression?
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-06-12 14:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 0:08 Running kexec on mx6 Fabio Estevam
2015-06-12 13:53 ` Fabio Estevam
2015-06-12 14:01 ` Russell King - ARM Linux [this message]
2015-06-12 14:06 ` Fabio Estevam
2015-06-12 17:54 ` Robert Schwebel
2015-06-15 13:12 ` Fabio Estevam
2015-06-12 14:02 ` Fabio Estevam
2015-06-15 21:40 ` Fabio Estevam
2015-06-15 22:43 ` Fabio Estevam
2015-06-16 4:18 ` Fabio Estevam
2015-06-16 9:42 ` Russell King - ARM Linux
2015-06-16 11:15 ` Fabio Estevam
2015-06-16 12:46 ` Fabio Estevam
2015-06-16 16:13 ` Russell King - ARM Linux
2015-06-16 18:01 ` Fabio Estevam
2015-06-16 19:58 ` Russell King - ARM Linux
2015-06-16 20:13 ` Fabio Estevam
2015-06-16 20:45 ` Russell King - ARM Linux
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=20150612140123.GA7557@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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