On 04/08/2014 04:54 AM, Jason Cooper wrote:
On Mon, Apr 07, 2014 at 10:55:01PM -0700, Kevin's boot bot wrote:
Automated DT boot report for various ARM defconfigs.
Tree/Branch: queue Git describe: v3.12.17 Failed boot tests (console logs at the end) =========================================== armada-370-mirabox: FAIL: mvebu_defconfig
...
Console logs for failures
mvebu_defconfig
armada-370-mirabox: FAIL: last 80 lines of boot log:
phy16= 72 phy16= 72 MMC: MRVL_MMC: 0 Net: egiga0 [PRIME], egiga1 Hit any key to stop autoboot: 3 0 Marvell>> Marvell>> version version
U-Boot 2009.08 (Sep 16 2012 - 22:50:06)Marvell version: 1.1.2 NQ Marvell>> setenv bootargs console=ttyS0,115200 debug earlyprintk setenv bootargs console=ttyS0,115200 debug earlyprintk Marvell>setenv initrd_high 0xffffffff
setenv initrd_high 0xffffffff
Marvell>> if test -n ${initenv}; then run initenv; fi if test -n ${initenv}; then run initenv; fi Marvell>> if test -n ${preboot}; then run preboot; fi if test -n ${preboot}; then run preboot; fi Marvell>setenv autoload no; setenv autoboot no
setenv autoload no; setenv autoboot no
Marvell>>dhcp dhcp phyaddr= 0 BOOTP broadcast 1 DHCP client bound to address 192.168.1.183 Marvell>> setenv serverip 192.168.1.2 setenv serverip 192.168.1.2 Marvell>>if test -n ${netargs}; then run netargs; fi if test -n ${netargs}; then run netargs; fi Marvell>> tftp 0x02000000 192.168.1.2:tmp/mirabox-wVO2nj/tmp0l2RnB-uImage tftp 0x02000000 192.168.1.2:tmp/mirabox-wVO2nj/tmp0l2RnB-uImage Using egiga0 device TFTP from server 192.168.1.2; our IP address is 192.168.1.183 Filename 'tmp/mirabox-wVO2nj/tmp0l2RnB-uImage'. Load address: 0x2000000 Loading: *################################################################# ################################################################# ################################################### done Bytes transferred = 2654005 (287f35 hex) Marvell>> tftp 0x03000000 192.168.1.2:buildroot.cpio.gz.uboot tftp 0x03000000 192.168.1.2:buildroot.cpio.gz.uboot Using egiga0 device TFTP from server 192.168.1.2; our IP address is 192.168.1.183 Filename 'buildroot.cpio.gz.uboot'. Load address: 0x3000000 Loading: *############################################ done Bytes transferred = 642602 (9ce2a hex) Marvell>> printenv bootargs printenv bootargs bootargs=console=ttyS0,115200 debug earlyprintk Marvell>bootm 0x02000000 0x03000000
bootm 0x02000000 0x03000000
## Booting kernel from Legacy Image at 02000000 ... Image Name: Linux Created: 2014-04-08 5:54:12 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2653941 Bytes = 2.5 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 03000000 ... Image Name: Created: 2014-02-07 19:37:29 UTC Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 642538 Bytes = 627.5 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK
Starting kernel ...
~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 47.65 seconds. # PYBOOT: Result: FAIL
Kevin,
any insight what happened here?
hmm, nope. Looks like it's been failing on v3.12.y since v3.12.10.
After bisecting, the finger is pointing at the commit below[1]. Smells like another patch missing from stable?
Kevin
[1] 710398e3b203763d847a6310a65006bba7205d27 is the first bad commit commit 710398e3b203763d847a6310a65006bba7205d27 Author: Gregory CLEMENT gregory.clement@free-electrons.com Date: Thu Jan 2 15:08:59 2014 +0100
ARM: mvebu: Add support to get the ID and the revision of a SoC