Automated DT boot report for various ARM defconfigs.
Tree/Branch: arm-soc Git describe: v3.14-rc4-695-g7c79649 Failed boot tests (console logs at the end) =========================================== sun7i-a20-cubieboard2: FAIL: multi_lpae_defconfig sun7i-a20-cubieboard2: FAIL: sunxi_defconfig sun4i-a10-cubieboard: FAIL: sunxi_defconfig ste-snowball: FAIL: multi_v7_defconfig sun7i-a20-cubieboard2: FAIL: multi_v7_defconfig sun4i-a10-cubieboard: FAIL: multi_v7_defconfig
Full Report ===========
da8xx_omapl_defconfig --------------------- da850-evm PASS: 0 min 15.1 sec
omap2plus_defconfig ------------------- legacy,3730xm PASS: 0 min 53.3 sec am335x-boneblack PASS: 0 min 25.6 sec omap3-beagle-xm PASS: 1 min 3.1 sec legacy,3530beagle PASS: 0 min 42.9 sec omap4-panda PASS: 1 min 8.7 sec omap3-overo-tobi PASS: 0 min 22.9 sec am335x-bone PASS: 0 min 27.1 sec omap3-overo-storm-tobi PASS: 0 min 22.0 sec omap4-panda-es PASS: 1 min 6.4 sec legacy,3730storm PASS: 0 min 23.9 sec legacy,3530overo PASS: 0 min 21.3 sec
multi_lpae_defconfig -------------------- sun7i-a20-cubieboard2 FAIL: 0 min 19.6 sec
tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.0 sec
imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 18.4 sec imx6dl-wandboard,wand-solo PASS: 0 min 18.4 sec imx6q-wandboard PASS: 0 min 16.9 sec
sunxi_defconfig --------------- sun7i-a20-cubieboard2 FAIL: 0 min 17.5 sec sun4i-a10-cubieboard FAIL: 0 min 17.5 sec
bcm_defconfig ------------- bcm28155-ap PASS: 0 min 53.8 sec
mvebu_v7_defconfig ------------------ armada-xp-openblocks-ax3-4 PASS: 0 min 22.1 sec armada-370-mirabox PASS: 0 min 20.4 sec
exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 30.0 sec
multi_v7_defconfig ------------------ ste-snowball FAIL: 0 min 33.6 sec tegra30-beaver PASS: 0 min 16.9 sec am335x-boneblack PASS: 0 min 23.6 sec omap3-beagle-xm PASS: 0 min 50.7 sec sun7i-a20-cubieboard2 FAIL: 0 min 31.4 sec armada-370-mirabox PASS: 0 min 22.4 sec omap4-panda PASS: 0 min 57.2 sec armada-xp-openblocks-ax3-4 PASS: 0 min 25.1 sec sun4i-a10-cubieboard FAIL: 0 min 22.4 sec bcm28155-ap PASS: 1 min 14.7 sec omap3-overo-tobi PASS: 0 min 21.7 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.6 sec am335x-bone PASS: 0 min 26.2 sec omap3-overo-storm-tobi PASS: 0 min 24.3 sec imx6q-wandboard PASS: 0 min 16.6 sec omap4-panda-es PASS: 0 min 51.2 sec imx6dl-wandboard,wand-dual PASS: 0 min 17.9 sec
u8500_defconfig --------------- ste-snowball PASS: 0 min 32.8 sec
sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.2 sec
davinci_all_defconfig --------------------- legacy,dm365evm PASS: 0 min 16.5 sec
Console logs for failures =========================
multi_lpae_defconfig --------------------
sun7i-a20-cubieboard2: FAIL: last 80 lines of boot log: -------------------------------------------------------
setenv ethaddr 22:71:81:DA:53:EA sun7i#setenv bootargs console=ttyS0,115200 debug earlyprintk rw root=/dev/mmcblk0p2 rootwait rootfstype=ext4 setenv bootargs console=ttyS0,115200 debug earlyprintk rw root=/dev/mmcblk0p2 rootwait rootfstype=ext4 sun7i# setenv netargs 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}::::192.168.1.254:none' setenv netargs 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}::::192.168.1.254:none' sun7i# setenv initrd_high 0xffffffff setenv initrd_high 0xffffffff sun7i# if test -n ${initenv}; then run initenv; fi if test -n ${initenv}; then run initenv; fi sun7i# if test -n ${preboot}; then run preboot; fi if test -n ${preboot}; then run preboot; fi sun7i# setenv autoload no; setenv autoboot no setenv autoload no; setenv autoboot no sun7i# dhcp dhcp ENET Speed is 100 Mbps - FULL duplex connection BOOTP broadcast 1 DHCP client bound to address 192.168.1.153 sun7i# setenv serverip 192.168.1.2 setenv serverip 192.168.1.2 sun7i# if test -n ${netargs}; then run netargs; fi if test -n ${netargs}; then run netargs; fi sun7i# tftp 0x40008000 192.168.1.2:tmp/cubie2-VkUIpc/zImage tftp 0x40008000 192.168.1.2:tmp/cubie2-VkUIpc/zImage Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.153 Filename 'tmp/cubie2-VkUIpc/zImage'. Load address: 0x40008000 Loading: *################################################################# ################################################################# ################################################################# ################################################################# ################################################## 2.7 MiB/s done Bytes transferred = 4544400 (455790 hex) sun7i# tftp 0x42000000 192.168.1.2:buildroot.cpio.gz.uboot tftp 0x42000000 192.168.1.2:buildroot.cpio.gz.uboot Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.153 Filename 'buildroot.cpio.gz.uboot'. Load address: 0x42000000 Loading: *############################################ 2.7 MiB/s done Bytes transferred = 642602 (9ce2a hex) sun7i# tftp 0x41000000 192.168.1.2:tmp/cubie2-VkUIpc/sun7i-a20-cubieboard2.dtb tftp 0x41000000 192.168.1.2:tmp/cubie2-VkUIpc/sun7i-a20-cubieboard2.dtb Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.153 Filename 'tmp/cubie2-VkUIpc/sun7i-a20-cubieboard2.dtb'. Load address: 0x41000000 Loading: *## 2.1 MiB/s done Bytes transferred = 15599 (3cef hex) sun7i# printenv bootargs printenv bootargs bootargs=console=ttyS0,115200 debug earlyprintk rw root=/dev/mmcblk0p2 rootwait rootfstype=ext4 ip=192.168.1.153:192.168.1.2:192.168.1.254:255.255.255.0::::192.168.1.254:none sun7i# bootz 0x40008000 0x42000000 0x41000000 bootz 0x40008000 0x42000000 0x41000000 Kernel image @ 0x40008000 [ 0x000000 - 0x455790 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: Created: 2014-02-07 19:37:29 UTC Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 642538 Bytes = 627.5 KiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 41000000 Booting using the fdt blob at 0x41000000 Loading Device Tree to 40ff9000, end 40fffcee ... OK
Starting kernel ...
~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 19.58 seconds. # PYBOOT: Result: FAIL
sunxi_defconfig ---------------
sun7i-a20-cubieboard2: FAIL: last 80 lines of boot log: -------------------------------------------------------
arm-linux-gnueabi-gcc (Ubuntu/Linaro 4.7.2-1ubuntu1) 4.7.2 GNU ld (GNU Binutils for Ubuntu) 2.22.90.20120919 sun7i#setenv ethaddr 22:71:81:DA:53:EA setenv ethaddr 22:71:81:DA:53:EA sun7i# setenv bootargs console=ttyS0,115200 debug earlyprintk rw root=/dev/mmcblk0p2 rootwait rootfstype=ext4 setenv bootargs console=ttyS0,115200 debug earlyprintk rw root=/dev/mmcblk0p2 rootwait rootfstype=ext4 sun7i#setenv netargs 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}::::192.168.1.254:none' setenv netargs 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}::::192.168.1.254:none' sun7i# setenv initrd_high 0xffffffff setenv initrd_high 0xffffffff sun7i# if test -n ${initenv}; then run initenv; fi if test -n ${initenv}; then run initenv; fi sun7i# if test -n ${preboot}; then run preboot; fi if test -n ${preboot}; then run preboot; fi sun7i# setenv autoload no; setenv autoboot no setenv autoload no; setenv autoboot no sun7i# dhcp dhcp ENET Speed is 100 Mbps - FULL duplex connection BOOTP broadcast 1 DHCP client bound to address 192.168.1.153 sun7i# setenv serverip 192.168.1.2 setenv serverip 192.168.1.2 sun7i# if test -n ${netargs}; then run netargs; fi if test -n ${netargs}; then run netargs; fi sun7i# tftp 0x40008000 192.168.1.2:tmp/cubie2-V2_gKm/zImage tftp 0x40008000 192.168.1.2:tmp/cubie2-V2_gKm/zImage Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.153 Filename 'tmp/cubie2-V2_gKm/zImage'. Load address: 0x40008000 Loading: *################################################################# ######################################################## 2.7 MiB/s done Bytes transferred = 1774424 (1b1358 hex) sun7i# tftp 0x42000000 192.168.1.2:buildroot.cpio.gz.uboot tftp 0x42000000 192.168.1.2:buildroot.cpio.gz.uboot Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.153 Filename 'buildroot.cpio.gz.uboot'. Load address: 0x42000000 Loading: *############################################ 2.7 MiB/s done Bytes transferred = 642602 (9ce2a hex) sun7i# tftp 0x41000000 192.168.1.2:tmp/cubie2-V2_gKm/sun7i-a20-cubieboard2.dtb tftp 0x41000000 192.168.1.2:tmp/cubie2-V2_gKm/sun7i-a20-cubieboard2.dtb Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.153 Filename 'tmp/cubie2-V2_gKm/sun7i-a20-cubieboard2.dtb'. Load address: 0x41000000 Loading: *## 2.1 MiB/s done Bytes transferred = 15599 (3cef hex) sun7i# printenv bootargs printenv bootargs bootargs=console=ttyS0,115200 debug earlyprintk rw root=/dev/mmcblk0p2 rootwait rootfstype=ext4 ip=192.168.1.153:192.168.1.2:192.168.1.254:255.255.255.0::::192.168.1.254:none sun7i# bootz 0x40008000 0x42000000 0x41000000 bootz 0x40008000 0x42000000 0x41000000 Kernel image @ 0x40008000 [ 0x000000 - 0x1b1358 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: Created: 2014-02-07 19:37:29 UTC Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 642538 Bytes = 627.5 KiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 41000000 Booting using the fdt blob at 0x41000000 Loading Device Tree to 40ff9000, end 40fffcee ... OK
Starting kernel ...
~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 17.53 seconds. # PYBOOT: Result: FAIL
sun4i-a10-cubieboard: FAIL: last 80 lines of boot log: ------------------------------------------------------
arm-linux-gnueabi-gcc (Ubuntu/Linaro 4.7.2-1ubuntu1) 4.7.2 GNU ld (GNU Binutils for Ubuntu) 2.22.90.20120919 sun4i# setenv ethaddr 2e:40:70:f0:12:08 setenv ethaddr 2e:40:70:f0:12:08 sun4i# setenv bootargs console=ttyS0,115200 debug earlyprintk rw root=/dev/mmcblk0p2 rootwait rootfstype=ext4 setenv bootargs console=ttyS0,115200 debug earlyprintk rw root=/dev/mmcblk0p2 rootwait rootfstype=ext4 sun4i# setenv netargs 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}::::192.168.1.254:none' setenv netargs 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}::::192.168.1.254:none' sun4i# setenv initrd_high 0xffffffff setenv initrd_high 0xffffffff sun4i# if test -n ${initenv}; then run initenv; fi if test -n ${initenv}; then run initenv; fi sun4i# if test -n ${preboot}; then run preboot; fi if test -n ${preboot}; then run preboot; fi sun4i# setenv autoload no; setenv autoboot no setenv autoload no; setenv autoboot no sun4i# dhcp dhcp ENET Speed is 100 Mbps - FULL duplex connection BOOTP broadcast 1 DHCP client bound to address 192.168.1.193 sun4i# setenv serverip 192.168.1.2 setenv serverip 192.168.1.2 sun4i# if test -n ${netargs}; then run netargs; fi if test -n ${netargs}; then run netargs; fi sun4i# tftp 0x40008000 192.168.1.2:tmp/cubie-0FzzZk/zImage tftp 0x40008000 192.168.1.2:tmp/cubie-0FzzZk/zImage Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.193 Filename 'tmp/cubie-0FzzZk/zImage'. Load address: 0x40008000 Loading: *################################################################# ######################################################## 2.7 MiB/s done Bytes transferred = 1774424 (1b1358 hex) sun4i# tftp 0x42000000 192.168.1.2:buildroot.cpio.gz.uboot tftp 0x42000000 192.168.1.2:buildroot.cpio.gz.uboot Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.193 Filename 'buildroot.cpio.gz.uboot'. Load address: 0x42000000 Loading: *############################################ 2.7 MiB/s done Bytes transferred = 642602 (9ce2a hex) sun4i# tftp 0x41000000 192.168.1.2:tmp/cubie-0FzzZk/sun4i-a10-cubieboard.dtb tftp 0x41000000 192.168.1.2:tmp/cubie-0FzzZk/sun4i-a10-cubieboard.dtb Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.193 Filename 'tmp/cubie-0FzzZk/sun4i-a10-cubieboard.dtb'. Load address: 0x41000000 Loading: *# 2 MiB/s done Bytes transferred = 12602 (313a hex) sun4i# printenv bootargs printenv bootargs bootargs=console=ttyS0,115200 debug earlyprintk rw root=/dev/mmcblk0p2 rootwait rootfstype=ext4 ip=192.168.1.193:192.168.1.2:192.168.1.254:255.255.255.0::::192.168.1.254:none sun4i# bootz 0x40008000 0x42000000 0x41000000 bootz 0x40008000 0x42000000 0x41000000 Kernel image @ 0x40008000 [ 0x000000 - 0x1b1358 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: Created: 2014-02-07 19:37:29 UTC Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 642538 Bytes = 627.5 KiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 41000000 Booting using the fdt blob at 0x41000000 Loading Device Tree to 40ff9000, end 40fff139 ... OK
Starting kernel ...
~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 17.49 seconds. # PYBOOT: Result: FAIL
multi_v7_defconfig ------------------
ste-snowball: FAIL: last 80 lines of boot log: ----------------------------------------------
CPU: ST-Ericsson db8500 v2 (Dual ARM Cortex A9) 998.400 Mhz I2C: ready DRAM: 1 GB MMC: MCDE: startup failed sec_bridge: ISSWAPI_FLUSH_BOOT_CODE: 2 EMMC: 0, MMC: 1 In: serial Out: serial Err: serial Net: smc911x-0 Hit any key to stop autoboot: 1 0 U8500 $ U8500 $ version version
U-Boot 2009.11 (sept. 19 2011 - 17:03:11) U8500 $ setenv ethaddr 6e:e6:84:36:8e:9e setenv ethaddr 6e:e6:84:36:8e:9e Can't overwrite "ethaddr" U8500 $ setenv bootargs console=ttyAMA2,115200n8 debug earlyprintk rw root=/dev/mmcblk0p3 rootwait rootfstype=ext4 setenv bootargs console=ttyAMA2,115200n8 debug earlyprintk rw root=/dev/mmcblk0p3 rootwait rootfstype=ext4 U8500 $ setenv netargs 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}::::192.168.1.254:none' setenv netargs 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}::::192.168.1.254:none' U8500 $ if test -n ${initenv}; then run initenv; fi if test -n ${initenv}; then run initenv; fi U8500 $if test -n ${preboot}; then run preboot; fi if test -n ${preboot}; then run preboot; fi U8500 $ setenv autoload no; setenv autoboot no setenv autoload no; setenv autoboot no U8500 $ dhcp dhcp smc911x: detected LAN9221 controller smc911x: phy initialized smc911x: MAC 6e:e6:84:36:8e:9e BOOTP broadcast 1 BOOTP broadcast 2 DHCP client bound to address 192.168.1.159 U8500 $ setenv serverip 192.168.1.2 setenv serverip 192.168.1.2 U8500 $ if test -n ${netargs}; then run netargs; fi if test -n ${netargs}; then run netargs; fi U8500 $ tftp 0x00800000 192.168.1.2:tmp/snowball-D0xMLh/tmpWwtvVM-uImage tftp 0x00800000 192.168.1.2:tmp/snowball-D0xMLh/tmpWwtvVM-uImage smc911x: detected LAN9221 controller smc911x: phy initialized smc911x: MAC 6e:e6:84:36:8e:9e Using smc911x-0 device TFTP from server 192.168.1.2; our IP address is 192.168.1.159 Filename 'tmp/snowball-D0xMLh/tmpWwtvVM-uImage'. Load address: 0x800000 Loading: *################################################################# ################################################################# ################################################################# ################################################################# ################################################### done Bytes transferred = 4559841 (4593e1 hex) U8500 $ printenv bootargs printenv bootargs bootargs=console=ttyAMA2,115200n8 debug earlyprintk rw root=/dev/mmcblk0p3 rootwait rootfstype=ext4 ip=192.168.1.159:192.168.1.2:192.168.1.254:255.255.255.0::::192.168.1.254:none U8500 $ bootm 0x00800000 bootm 0x00800000 ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4559777 Bytes = 4.3 MB Load Address: 00008000 Entry Point: 00008000 Loading Kernel Image ... OK OK
Starting kernel ...
~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 33.61 seconds. # PYBOOT: Result: FAIL
sun7i-a20-cubieboard2: FAIL: last 80 lines of boot log: -------------------------------------------------------
Connected to cubie2 console [channel connected] (~$quit to exit) (user:khilman) is already connected
~$hardreset
Command(cubie2 console)> hardreset (user:khilman) Reboot cubie2 Reboot: cubie2 ; phidget 3 0 : off, sleep, on 0 sun7i# ~$off # PYBOOT: Exception: ERROR: Could not break into autoboot. # PYBOOT: Time: 31.38 seconds. # PYBOOT: Result: FAIL
sun4i-a10-cubieboard: FAIL: last 80 lines of boot log: ------------------------------------------------------
sun4i# setenv bootargs console=ttyS0,115200 debug earlyprintk rw root=/dev/mmcblk0p2 rootwait rootfstype=ext4 setenv bootargs console=ttyS0,115200 debug earlyprintk rw root=/dev/mmcblk0p2 rootwait rootfstype=ext4 sun4i# setenv netargs 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}::::192.168.1.254:none' setenv netargs 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}::::192.168.1.254:none' sun4i# setenv initrd_high 0xffffffff setenv initrd_high 0xffffffff sun4i# if test -n ${initenv}; then run initenv; fi if test -n ${initenv}; then run initenv; fi sun4i# if test -n ${preboot}; then run preboot; fi if test -n ${preboot}; then run preboot; fi sun4i# setenv autoload no; setenv autoboot no setenv autoload no; setenv autoboot no sun4i# dhcp dhcp ENET Speed is 100 Mbps - FULL duplex connection BOOTP broadcast 1 BOOTP broadcast 2 DHCP client bound to address 192.168.1.193 sun4i# setenv serverip 192.168.1.2 setenv serverip 192.168.1.2 sun4i# if test -n ${netargs}; then run netargs; fi if test -n ${netargs}; then run netargs; fi sun4i# tftp 0x40008000 192.168.1.2:tmp/cubie-0_XyAn/zImage tftp 0x40008000 192.168.1.2:tmp/cubie-0_XyAn/zImage Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.193 Filename 'tmp/cubie-0_XyAn/zImage'. Load address: 0x40008000 Loading: *################################################################# ################################################################# ################################################################# ################################################################# ################################################ 2.7 MiB/s done Bytes transferred = 4518528 (44f280 hex) sun4i# tftp 0x42000000 192.168.1.2:buildroot.cpio.gz.uboot tftp 0x42000000 192.168.1.2:buildroot.cpio.gz.uboot Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.193 Filename 'buildroot.cpio.gz.uboot'. Load address: 0x42000000 Loading: *############################################ 2.7 MiB/s done Bytes transferred = 642602 (9ce2a hex) sun4i# tftp 0x41000000 192.168.1.2:tmp/cubie-0_XyAn/sun4i-a10-cubieboard.dtb tftp 0x41000000 192.168.1.2:tmp/cubie-0_XyAn/sun4i-a10-cubieboard.dtb Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.193 Filename 'tmp/cubie-0_XyAn/sun4i-a10-cubieboard.dtb'. Load address: 0x41000000 Loading: *# 2 MiB/s done Bytes transferred = 12602 (313a hex) sun4i# printenv bootargs printenv bootargs bootargs=console=ttyS0,115200 debug earlyprintk rw root=/dev/mmcblk0p2 rootwait rootfstype=ext4 ip=192.168.1.193:192.168.1.2:192.168.1.254:255.255.255.0::::192.168.1.254:none sun4i# bootz 0x40008000 0x42000000 0x41000000 bootz 0x40008000 0x42000000 0x41000000 Kernel image @ 0x40008000 [ 0x000000 - 0x44f280 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: Created: 2014-02-07 19:37:29 UTC Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 642538 Bytes = 627.5 KiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 41000000 Booting using the fdt blob at 0x41000000 Loading Device Tree to 40ff9000, end 40fff139 ... OK
Starting kernel ...
~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 22.37 seconds. # PYBOOT: Result: FAIL
Hi,
On Sun, Mar 09, 2014 at 11:58:04PM -0700, Kevin's boot bot wrote:
Automated DT boot report for various ARM defconfigs.
Tree/Branch: arm-soc Git describe: v3.14-rc4-695-g7c79649 Failed boot tests (console logs at the end) =========================================== sun7i-a20-cubieboard2: FAIL: multi_lpae_defconfig sun7i-a20-cubieboard2: FAIL: sunxi_defconfig sun4i-a10-cubieboard: FAIL: sunxi_defconfig ste-snowball: FAIL: multi_v7_defconfig sun7i-a20-cubieboard2: FAIL: multi_v7_defconfig sun4i-a10-cubieboard: FAIL: multi_v7_defconfig
Hmmm, I think I handled this one badly.
This is actually because of the commit bf6534a180d6d596521b0bfa6de29da5e18314a6, merged through arm-soc, while the associated commit has been taken through the clk tree. Obviously this doesn't work very well.
I guess the easiest would be to revert the DT patch in arm-soc, and have Emilio merge it in his clk tree. Emilio, are you ok doing so?
Hi,
El 11/03/14 06:39, Maxime Ripard escribió:
Hi,
On Sun, Mar 09, 2014 at 11:58:04PM -0700, Kevin's boot bot wrote:
Automated DT boot report for various ARM defconfigs.
Tree/Branch: arm-soc Git describe: v3.14-rc4-695-g7c79649 Failed boot tests (console logs at the end) =========================================== sun7i-a20-cubieboard2: FAIL: multi_lpae_defconfig sun7i-a20-cubieboard2: FAIL: sunxi_defconfig sun4i-a10-cubieboard: FAIL: sunxi_defconfig ste-snowball: FAIL: multi_v7_defconfig sun7i-a20-cubieboard2: FAIL: multi_v7_defconfig sun4i-a10-cubieboard: FAIL: multi_v7_defconfig
Hmmm, I think I handled this one badly.
This is actually because of the commit bf6534a180d6d596521b0bfa6de29da5e18314a6, merged through arm-soc, while the associated commit has been taken through the clk tree. Obviously this doesn't work very well.
I guess the easiest would be to revert the DT patch in arm-soc, and have Emilio merge it in his clk tree. Emilio, are you ok doing so?
If Mike and the arm-soc guys are OK with it, I'm ok with it. My only fear is that doing this may bring conflicts galore between the trees (considering we also renamed nodes and other stuff).
Cheers,
Emilio
Emilio López emilio@elopez.com.ar writes:
Hi,
El 11/03/14 06:39, Maxime Ripard escribió:
Hi,
On Sun, Mar 09, 2014 at 11:58:04PM -0700, Kevin's boot bot wrote:
Automated DT boot report for various ARM defconfigs.
Tree/Branch: arm-soc Git describe: v3.14-rc4-695-g7c79649 Failed boot tests (console logs at the end) =========================================== sun7i-a20-cubieboard2: FAIL: multi_lpae_defconfig sun7i-a20-cubieboard2: FAIL: sunxi_defconfig sun4i-a10-cubieboard: FAIL: sunxi_defconfig ste-snowball: FAIL: multi_v7_defconfig sun7i-a20-cubieboard2: FAIL: multi_v7_defconfig sun4i-a10-cubieboard: FAIL: multi_v7_defconfig
Hmmm, I think I handled this one badly.
This is actually because of the commit bf6534a180d6d596521b0bfa6de29da5e18314a6, merged through arm-soc, while the associated commit has been taken through the clk tree. Obviously this doesn't work very well.
I guess the easiest would be to revert the DT patch in arm-soc, and have Emilio merge it in his clk tree. Emilio, are you ok doing so?
If Mike and the arm-soc guys are OK with it, I'm ok with it. My only fear is that doing this may bring conflicts galore between the trees (considering we also renamed nodes and other stuff).
Yeah, I'd rather keep the DT changes in the arm-soc tree.
As long as Mike has merged these, the better way is for us to just track the dependency in a depends/* branch of arm-soc, which is how we normally handle this.
Please let us know a stable point of Mike's tree (or the pull request that you sent to Mike if Mike's branch isn't stable) and we can track the dependency in arm-soc.
Thanks,
Kevin
Hi Kevin,
El 11/03/14 21:28, Kevin Hilman escribió:
Yeah, I'd rather keep the DT changes in the arm-soc tree.
As long as Mike has merged these, the better way is for us to just track the dependency in a depends/* branch of arm-soc, which is how we normally handle this.
Please let us know a stable point of Mike's tree (or the pull request that you sent to Mike if Mike's branch isn't stable) and we can track the dependency in arm-soc.
I have not sent the pull request yet. I can CC you on it when I do so if you want.
Cheers,
Emilio
[adding Mike, hopefully he will see the rest of the thread as well]
On Tue, Mar 11, 2014 at 5:31 PM, Emilio López emilio@elopez.com.ar wrote:
Hi Kevin,
El 11/03/14 21:28, Kevin Hilman escribió:
Yeah, I'd rather keep the DT changes in the arm-soc tree.
As long as Mike has merged these, the better way is for us to just track the dependency in a depends/* branch of arm-soc, which is how we normally handle this.
Please let us know a stable point of Mike's tree (or the pull request that you sent to Mike if Mike's branch isn't stable) and we can track the dependency in arm-soc.
I have not sent the pull request yet. I can CC you on it when I do so if you want.
Yea, please send it to arm@kernel.org so we can both pull it in (Mike and us).
-Olof
On Tue, Mar 11, 2014 at 6:02 PM, Olof Johansson olof@lixom.net wrote:
[adding Mike, hopefully he will see the rest of the thread as well]
On Tue, Mar 11, 2014 at 5:31 PM, Emilio López emilio@elopez.com.ar wrote:
Hi Kevin,
El 11/03/14 21:28, Kevin Hilman escribió:
Yeah, I'd rather keep the DT changes in the arm-soc tree.
As long as Mike has merged these, the better way is for us to just track the dependency in a depends/* branch of arm-soc, which is how we normally handle this.
Please let us know a stable point of Mike's tree (or the pull request that you sent to Mike if Mike's branch isn't stable) and we can track the dependency in arm-soc.
I have not sent the pull request yet. I can CC you on it when I do so if you want.
Yea, please send it to arm@kernel.org so we can both pull it in (Mike and us).
Is there a pull request coming for this any time soon? Or do we need to back out the changes that were merged into arm-soc that introduced this breakage while waiting?
Kevin
El 18/03/14 20:34, Kevin Hilman escribió:
On Tue, Mar 11, 2014 at 6:02 PM, Olof Johansson olof@lixom.net wrote:
[adding Mike, hopefully he will see the rest of the thread as well]
On Tue, Mar 11, 2014 at 5:31 PM, Emilio López emilio@elopez.com.ar wrote:
Hi Kevin,
El 11/03/14 21:28, Kevin Hilman escribió:
Yeah, I'd rather keep the DT changes in the arm-soc tree.
As long as Mike has merged these, the better way is for us to just track the dependency in a depends/* branch of arm-soc, which is how we normally handle this.
Please let us know a stable point of Mike's tree (or the pull request that you sent to Mike if Mike's branch isn't stable) and we can track the dependency in arm-soc.
I have not sent the pull request yet. I can CC you on it when I do so if you want.
Yea, please send it to arm@kernel.org so we can both pull it in (Mike and us).
Is there a pull request coming for this any time soon? Or do we need to back out the changes that were merged into arm-soc that introduced this breakage while waiting?
Yes, I'm going to send it today. Sorry for the delay.
Emilio
Hi Mike, arm-soc people:
Here's the clk pull request for sunxi, to go along with Maxime's one to arm-soc. I just tested armsoc/for-next plus this merged on top and my Cubietruck is happy to boot and GMAC can ping Google correctly.
--->8---
The following changes since commit 38dbfb59d1175ef458d006556061adeaa8751b72:
Linus 3.14-rc1 (2014-02-02 16:42:13 -0800)
are available in the git repository at:
https://bitbucket.org/emiliolopez/linux.git tags/sunxi-clk-for-3.15
for you to fetch changes up to fd1b22f6fb3b31980b80505ac9d86521569ed2ee:
clk: sunxi: Add new clock compatibles (2014-02-18 10:34:28 -0300)
---------------------------------------------------------------- Allwinner sunXi SoCs clock changes
This adds support for the new, more correct clock node naming and gets the A10 compatibles in line with the rest of the other SoCs. It also adds support for the USB, GMAC and A31's PLL6 clocks. Some of these changes also require DT modifications that will be merged via arm-soc.
---------------------------------------------------------------- Chen-Yu Tsai (5): clk: sunxi: add clock-output-names dt property support clk: sunxi: update clock-output-names dt binding documentation clk: sunxi: add names for pll5, pll6 parent clocks to factors_data clk: sunxi: get divs parent clock name from parent factor clock clk: sunxi: Add Allwinner A20/A31 GMAC clock unit
Hans de Goede (1): clk: sunxi: Add support for USB clock-register reset bits
Maxime Ripard (2): clk: sunxi: Add support for PLL6 on the A31 clk: sunxi: Add new clock compatibles
Roman Byshko (1): clk: sunxi: Add USB clock register defintions
Documentation/devicetree/bindings/clock/sunxi.txt | 102 ++++++-- drivers/clk/sunxi/clk-sunxi.c | 290 ++++++++++++++++++++-- 2 files changed, 344 insertions(+), 48 deletions(-)
Quoting Emilio López (2014-03-19 06:03:44)
Hi Mike, arm-soc people:
Here's the clk pull request for sunxi, to go along with Maxime's one to arm-soc. I just tested armsoc/for-next plus this merged on top and my Cubietruck is happy to boot and GMAC can ping Google correctly.
Looks good. I've taken this into clk-next towards 3.15. Just FYI I have applied the clk patches from your "[PATCH 0/4] sunxi clock fixes" series on top of this pull request.
Regards, Mike
--->8---
The following changes since commit 38dbfb59d1175ef458d006556061adeaa8751b72:
Linus 3.14-rc1 (2014-02-02 16:42:13 -0800)
are available in the git repository at:
https://bitbucket.org/emiliolopez/linux.git tags/sunxi-clk-for-3.15
for you to fetch changes up to fd1b22f6fb3b31980b80505ac9d86521569ed2ee:
clk: sunxi: Add new clock compatibles (2014-02-18 10:34:28 -0300)
Allwinner sunXi SoCs clock changes
This adds support for the new, more correct clock node naming and gets the A10 compatibles in line with the rest of the other SoCs. It also adds support for the USB, GMAC and A31's PLL6 clocks. Some of these changes also require DT modifications that will be merged via arm-soc.
Chen-Yu Tsai (5): clk: sunxi: add clock-output-names dt property support clk: sunxi: update clock-output-names dt binding documentation clk: sunxi: add names for pll5, pll6 parent clocks to factors_data clk: sunxi: get divs parent clock name from parent factor clock clk: sunxi: Add Allwinner A20/A31 GMAC clock unit
Hans de Goede (1): clk: sunxi: Add support for USB clock-register reset bits
Maxime Ripard (2): clk: sunxi: Add support for PLL6 on the A31 clk: sunxi: Add new clock compatibles
Roman Byshko (1): clk: sunxi: Add USB clock register defintions
Documentation/devicetree/bindings/clock/sunxi.txt | 102 ++++++-- drivers/clk/sunxi/clk-sunxi.c | 290 ++++++++++++++++++++-- 2 files changed, 344 insertions(+), 48 deletions(-)
El 19/03/14 16:39, Mike Turquette escribió:
Quoting Emilio López (2014-03-19 06:03:44)
Hi Mike, arm-soc people:
Here's the clk pull request for sunxi, to go along with Maxime's one to arm-soc. I just tested armsoc/for-next plus this merged on top and my Cubietruck is happy to boot and GMAC can ping Google correctly.
Looks good. I've taken this into clk-next towards 3.15. Just FYI I have applied the clk patches from your "[PATCH 0/4] sunxi clock fixes" series on top of this pull request.
Yes, that's alright. Thanks!
Emilio
On Wed, Mar 19, 2014 at 12:39:09PM -0700, Mike Turquette wrote:
Quoting Emilio López (2014-03-19 06:03:44)
Hi Mike, arm-soc people:
Here's the clk pull request for sunxi, to go along with Maxime's one to arm-soc. I just tested armsoc/for-next plus this merged on top and my Cubietruck is happy to boot and GMAC can ping Google correctly.
Looks good. I've taken this into clk-next towards 3.15. Just FYI I have applied the clk patches from your "[PATCH 0/4] sunxi clock fixes" series on top of this pull request.
Excellent. I'll pull this in as a depends/sunxi-clk branch as well, even though the dependency came in the wrong order in some ways. :)
-Olof
On Tue, Mar 11, 2014 at 2:39 AM, Maxime Ripard maxime.ripard@free-electrons.com wrote:
Hi,
On Sun, Mar 09, 2014 at 11:58:04PM -0700, Kevin's boot bot wrote:
Automated DT boot report for various ARM defconfigs.
Tree/Branch: arm-soc Git describe: v3.14-rc4-695-g7c79649 Failed boot tests (console logs at the end) =========================================== sun7i-a20-cubieboard2: FAIL: multi_lpae_defconfig sun7i-a20-cubieboard2: FAIL: sunxi_defconfig sun4i-a10-cubieboard: FAIL: sunxi_defconfig ste-snowball: FAIL: multi_v7_defconfig sun7i-a20-cubieboard2: FAIL: multi_v7_defconfig sun4i-a10-cubieboard: FAIL: multi_v7_defconfig
Hmmm, I think I handled this one badly.
This is actually because of the commit bf6534a180d6d596521b0bfa6de29da5e18314a6, merged through arm-soc, while the associated commit has been taken through the clk tree. Obviously this doesn't work very well.
I guess the easiest would be to revert the DT patch in arm-soc, and have Emilio merge it in his clk tree. Emilio, are you ok doing so?
Aaargh, turns out my script has had a bug for a while such that it doesn't actually report failure on these boot breakages. I was wondering why Kevin had errors and I didn't, but I was brushing it off as network setup issues since I didn't look closer.
-Olof
linaro-kernel@lists.linaro.org
-
Emilio López -
Kevin Hilman -
Kevin's boot bot
-
Maxime Ripard -
Mike Turquette -
Olof Johansson