omap:am335x: unable to start kernel via kexec

Yegor Yefremov yegorslists at googlemail.com
Wed May 21 06:19:39 PDT 2014


On Wed, May 21, 2014 at 12:26 PM, Yegor Yefremov
<yegorslists at googlemail.com> wrote:
> Kernel: vanilla 3.15-rc5
> kexec: latest git (21.05.2014)
>
> I can load the zImage + dtb from u-boot, but invoking kexec prints
> following data and nothing happens after "Bye!":
>
> # kexec -d -f --dtb=/mnt/boot/am335x-evmsk.dtb /mnt/boot/zImage
> kernel: 0xb5eab008 kernel_size: 0x2036c
> kexec_load: entry = 0x80008000 flags = 0x280000
> nr_segments = 2
> segment[0].buf   = 0xb5eab008
> segment[0].bufsz = 0x43d328
> segment[0].mem   = 0x80008000
> segment[0].memsz = 0x43e000
> segment[1].buf   = 0x29008
> segment[1].bufsz = 0x7e89
> segment[1].mem   = 0x810f6000
> segment[1].memsz = 0x8000
> Starting new kernel
> Bye!
>
> u-boot output for the same kernel+dtb:
>
> SD/MMC found on device 0
> reading uEnv.txt
> 582 bytes read in 8 ms (70.3 KiB/s)
> Loaded environment from uEnv.txt
> Importing environment from mmc ...
> Running uenvcmd ...
> 4444968 bytes read in 466 ms (9.1 MiB/s)
> 32393 bytes read in 46 ms (687.5 KiB/s)
> Kernel image @ 0x82000000 [ 0x000000 - 0x43d328 ]
> ## Flattened Device Tree blob at 80000000
>    Booting using the fdt blob at 0x80000000
>    Loading Device Tree to 8f618000, end 8f622e88 ... OK
>
> Wang, what hardware do you use?

Everything is working now. I think it has something to do with wrong
kernel parameters. Sorry for the noise.

FIT support can be undertaken.

Regards,
Yegor



More information about the kexec mailing list