mvebu: 3.10-rc1 and fixes branch doesn't boot on OpenBlocks AX3
Hi,
I've tried 3.10-rc1 andgit://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git fixes branch on my OpenBlocks AX3-4 and failed to boot both kernel
as below.
---
Loading file "uImage" from ide device 0:1 (hda1) 2486993 bytes read
Loading file "uInitrd" from ide device 0:1 (hda1) 1851769 bytes read
## Booting kernel from Legacy Image at 02000000 ...
Image Name: Linux-marvell Created: 2013-05-27 3:43:33 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2486929 Bytes = 2.4 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: Linux-initrd Created: 2013-05-27 7:42:37 UTC Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 1851705 Bytes = 1.8 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x0
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 3.10.0-rc2-00054-gf4ae176 (mhiramat at mhiramat-M0-7522) (gcc version 4.6.3 20120624 (prerelease) (Ubuntu/Linaro 4.6.3-8ubuntu1) ) #99 SMP Mon May 27 12:43:19 JST 2013
CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
Machine: Marvell Armada 370/XP (Device Tree), model: PlatHome OpenBlocks AX3-4 board bootconsole [earlycon0] enabled
debug: skip boot console de-registration.
INITRD: 0x01100040+0x001c4139 is not a memory region - disabling initrd Memory policy: ECC disabled, Data cache writealloc
Kernel panic - not syncing: ERROR: Failed to allocate 0x1000 bytes below 0x0. CPU: 0 PID: 0 Comm: swapper Not tainted 3.10.0-rc2-00054-gf4ae176 #99 Backtrace: invalid frame pointer 0xc0661eb4
---
It seems that newer mvebu kernel has a corrupt description in device tree or should I run mkimage with different parameters for making uInitrd?
I'm using mkimage with parameters below for uimage
scripts/mkuboot.sh -A arm -O linux -T kernel -C none \ -a 0x8000 -e 0x8000 -n "Linux-marvell" -d zImage uImage
and
mkimage -A arm -O linux -T ramdisk -C none -a 0x0000 -e 0x0000 \ -n "Linux-initrd" -d /boot/initrd.img-$KVER /boot/uInitrd-$KVER
for uinitrd.
And boot the image from sata by uboot as below:
---
ide reset
ext2load ide 0:1 0x2000000 uImage
ext2load ide 0:1 0x1100000 uInitrd
setenv bootargs console=ttyS0,115200 earlyprintk=ttyS0 root=/dev/sda3 rootflags=subvol=@ ro keep_bootcon=1
bootm 0x2000000 0x1100000
---
BTW, should I enable CONFIG_ARM_LPAE even if the board has only 3GB memory?
Thank you,
Signature · 4 lines
Masami HIRAMATSU IT Management Research Dept. Linux Technology Center Hitachi, Ltd., Yokohama Research Laboratory E-mail: masami.hiramatsu.pt at hitachi.com
Quoted 1 line · Masami Hiramatsu
Hi,
Hi
Quoted 5 lines
I've tried 3.10-rc1 and
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.gitfixes branch on my OpenBlocks AX3-4 and failed to boot both kernel
as below.
Since 3.10 the memory description for the Armada XP is 64 bits, to allow to use more than 4GB of RAM with LPAE. Unfortunately the ATAGS are 32 bits only.
If you use more than 4GB your only possibility is to disable the ATAG support and only rely on the information written in the dts: disable CONFIG_ARM_ATAG_DTB_COMPAT.
If you don't have more than 4GB of RAM then you can also apply this
patch: https://patchwork.kernel.org/patch/2566771/
It allows to use the ATAG and to keep the CONFIG_ARM_ATAG_DTB_COMPAT option.
Regards,
Quoted 78 lines
---
Loading file "uImage" from ide device 0:1 (hda1) 2486993 bytes read
Loading file "uInitrd" from ide device 0:1 (hda1) 1851769 bytes read
## Booting kernel from Legacy Image at 02000000 ...Image Name: Linux-marvell Created: 2013-05-27 3:43:33 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2486929 Bytes = 2.4 MBLoad Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...Image Name: Linux-initrd Created: 2013-05-27 7:42:37 UTC Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 1851705 Bytes = 1.8 MBLoad Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OKStarting kernel ...
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU0x0
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 3.10.0-rc2-00054-gf4ae176 (mhiramat at mhiramat-M0-7522) (gcc version 4.6.3 20120624 (prerelease) (Ubuntu/Linaro 4.6.3-8ubuntu1) ) #99 SMP Mon May 27 12:43:19 JST 2013
CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
Machine: Marvell Armada 370/XP (Device Tree), model: PlatHome OpenBlocks AX3-4 board bootconsole [earlycon0] enabled
debug: skip boot console de-registration.
INITRD: 0x01100040+0x001c4139 is not a memory region - disabling initrd Memory policy: ECC disabled, Data cache writeallocKernel panic - not syncing: ERROR: Failed to allocate 0x1000 bytes below 0x0. CPU: 0 PID: 0 Comm: swapper Not tainted 3.10.0-rc2-00054-gf4ae176 #99 Backtrace: invalid frame pointer 0xc0661eb4---
It seems that newer mvebu kernel has a corrupt description in device tree or should I run mkimage with different parameters for making uInitrd?
I'm using mkimage with parameters below for uimage
scripts/mkuboot.sh -A arm -O linux -T kernel -C none \ -a 0x8000 -e 0x8000 -n "Linux-marvell" -d zImage uImageand
mkimage -A arm -O linux -T ramdisk -C none -a 0x0000 -e 0x0000 \ -n "Linux-initrd" -d /boot/initrd.img-$KVER /boot/uInitrd-$KVERfor uinitrd.
And boot the image from sata by uboot as below:
---
ide reset
ext2load ide 0:10x2000000uImage
ext2load ide 0:10x1100000uInitrd
setenv bootargs console=ttyS0,115200 earlyprintk=ttyS0 root=/dev/sda3 rootflags=subvol=@ ro keep_bootcon=1
bootm0x20000000x1100000
---BTW, should I enable
CONFIG_ARM_LPAEeven if the board has only 3GB memory?Thank you,
Signature · 4 lines
Gregory Clement, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
Quoted 17 lines · Gregory CLEMENT
Quoted 1 line · Masami Hiramatsu
Hi,
Hi
Quoted 5 lines
I've tried 3.10-rc1 and
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.gitfixes branch on my OpenBlocks AX3-4 and failed to boot both kernel
as below.Since 3.10 the memory description for the Armada XP is 64 bits, to allow to use more than 4GB of RAM with LPAE. Unfortunately the ATAGS are 32 bits only.
If you use more than 4GB your only possibility is to disable the ATAG support and only rely on the information written in the dts: disableCONFIG_ARM_ATAG_DTB_COMPAT.
Quoted 4 lines
If you don't have more than 4GB of RAM then you can also apply this
patch: https://patchwork.kernel.org/patch/2566771/
It allows to use the ATAG and to keep theCONFIG_ARM_ATAG_DTB_COMPAToption.
Thanks for the information!
That patch solves my issue :)
Best regards,
Signature · 4 lines
Masami HIRAMATSU IT Management Research Dept. Linux Technology Center Hitachi, Ltd., Yokohama Research Laboratory E-mail: masami.hiramatsu.pt at hitachi.com