linaro-kernel March 2014

linaro-kernel@lists.linaro.org

86 participants
221 discussions

[PATCH 1/4] arm64: topology: Initialise default topology state immediately

by Mark Brown

From: Mark Brown <broonie(a)linaro.org> As a legacy of the way 32 bit ARM did things the topology code uses a null topology map by default and then overwrites it by mapping cores with no information to a cluster by themselves later. In order to make it simpler to reset things as part of recovering from parse failures in firmware information directly set this configuration on init. A core will always be its own sibling so there should be no risk of confusion with firmware provided information. Signed-off-by: Mark Brown <broonie(a)linaro.org> --- arch/arm64/kernel/topology.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/arm64/kernel/topology.c b/arch/arm64/kernel/topology.c index 3e06b0be4ec8..ff662b23af5f 100644 --- a/arch/arm64/kernel/topology.c +++ b/arch/arm64/kernel/topology.c @@ -43,9 +43,6 @@ static void update_siblings_masks(unsigned int cpuid) * reset it to default behaviour */ pr_debug("CPU%u: No topology information configured\n", cpuid); - cpuid_topo->core_id = 0; - cpumask_set_cpu(cpuid, &cpuid_topo->core_sibling); - cpumask_set_cpu(cpuid, &cpuid_topo->thread_sibling); return; } @@ -87,9 +84,12 @@ void __init init_cpu_topology(void) struct cpu_topology *cpu_topo = &cpu_topology[cpu]; cpu_topo->thread_id = -1; - cpu_topo->core_id = -1; + cpu_topo->core_id = 0; cpu_topo->cluster_id = -1; + cpumask_clear(&cpu_topo->core_sibling); + cpumask_set_cpu(cpu, &cpu_topo->core_sibling); cpumask_clear(&cpu_topo->thread_sibling); + cpumask_set_cpu(cpu, &cpu_topo->thread_sibling); } } -- 1.9.1

10 years, 3 months

[PATCH v3 0/6] rework sched_domain topology description

by Vincent Guittot

This patchset was previously part of the larger tasks packing patchset [1]. I have splitted the latter in 3 different patchsets (at least) to make the thing easier. -configuration of sched_domain topology (this patchset) -update and consolidation of cpu_power -tasks packing algorithm Based on Peter Z's proposal [2][3], this patchset modifies the way to configure the sched_domain level in order to let architectures to add specific level like the current BOOK level or the proposed power gating level for ARM architecture. [1] https://lkml.org/lkml/2013/10/18/121 [2] https://lkml.org/lkml/2013/11/5/239 [3] https://lkml.org/lkml/2013/11/5/449 Change since v2: - remove patch 1 as it has been already applied to metag tree for v3.15 - updates some commit messages - add new flag description in TOPOLOGY_SD_FLAGS description Change since v1: - move sched_domains_curr_level back under #ifdef CONFIG_NUMA - use function pointer to set flag instead of a plain value. - add list of tunable flags in the commit message of patch 2 - add SD_SHARE_POWER_DOMAIN flag for powerpc's SMT level Vincent Guittot (6): sched: rework of sched_domain topology definition sched: s390: create a dedicated topology table sched: powerpc: create a dedicated topology table sched: add a new SD_SHARE_POWERDOMAIN for sched_domain sched: ARM: create a dedicated scheduler topology table sched: powerpc: Add SD_SHARE_POWERDOMAIN for SMT level arch/arm/kernel/topology.c | 26 +++++ arch/ia64/include/asm/topology.h | 24 ---- arch/powerpc/kernel/smp.c | 31 +++-- arch/s390/include/asm/topology.h | 13 +-- arch/s390/kernel/topology.c | 20 ++++ arch/tile/include/asm/topology.h | 33 ------ include/linux/sched.h | 49 +++++++- include/linux/topology.h | 128 +++----------------- kernel/sched/core.c | 244 ++++++++++++++++++++------------------- 9 files changed, 255 insertions(+), 313 deletions(-) -- 1.9.0

10 years, 3 months

Re: [RFC v3 0/5] cpufreq:LAB: Support for LAB governor.

by Viresh Kumar

[Adding Linaro lists in cc as there are few people here working on power/thermal stuff.] On 24 March 2014 15:30, Lukasz Majewski <l.majewski(a)samsung.com> wrote: >> On 4 March 2014 15:57, Lukasz Majewski <l.majewski(a)samsung.com> wrote: > I think, that "LAB" name is with us for some time, so it would be a > pity to discard it. It doesn't matter with Mainline how you do naming initially for your code :) We need to pick the right name now, and the decision should be made now (after discussions obviously) :) >> What about making it as simple as: >> - changing the ondemand governor only instead of adding a new governor > > My goal is to not touch the ondemand code. It has matured, so I would > like to leave it as it is. Because the boost feature is already part of CPUFreq core, I think its better if we enhance current governors to use it. So, I would like to make this part of existing governors. Not only ondemand but maybe conservative as well.. Also, I feel we maynot necessarily move this piece of code into cpufreq. All you are doing is thermal management here :) If we are sure we will not burn out our SoC (When many cores are idle), run at max freq (if there is enough load of course :)).. And if there are chances that we might burn our chip (when very few cores are idle), don't run on boost frequencies.. This is actually a 'cooling' device :) Think of it this way: CPUFreq will provide a range of frequency which SoC's can use. And then based on some conditions we may or may not want to run on these frequencies. @Zhang/Eduardo: Can we have your inputs here as well ? This may look hard but we need to design things in the best possible way for managing things better in future. Lets see what others have to say on this.

10 years, 3 months

[PATCH V5 0/3] cpufreq: Introduce cpufreq_freq_transition_{begin|end}()

by Viresh Kumar

Whenever we change the frequency of a CPU, we call the PRECHANGE and POSTCHANGE notifiers. They must be serialized, i.e. PRECHANGE and POSTCHANGE notifiers should strictly alternate, thereby preventing two different sets of PRECHANGE or POSTCHANGE notifiers from interleaving arbitrarily. The following examples illustrate why this is important: Scenario 1: ----------- A thread reading the value of cpuinfo_cur_freq, will call __cpufreq_cpu_get()->cpufreq_out_of_sync()->cpufreq_notify_transition() The ondemand governor can decide to change the frequency of the CPU at the same time and hence it can end up sending the notifications via ->target(). If the notifiers are not serialized, the following sequence can occur: - PRECHANGE Notification for freq A (from cpuinfo_cur_freq) - PRECHANGE Notification for freq B (from target()) - Freq changed by target() to B - POSTCHANGE Notification for freq B - POSTCHANGE Notification for freq A We can see from the above that the last POSTCHANGE Notification happens for freq A but the hardware is set to run at freq B. Where would we break then?: adjust_jiffies() in cpufreq.c & cpufreq_callback() in arch/arm/kernel/smp.c (which also adjusts the jiffies). All the loops_per_jiffy calculations will get messed up. Scenario 2: ----------- The governor calls __cpufreq_driver_target() to change the frequency. At the same time, if we change scaling_{min|max}_freq from sysfs, it will end up calling the governor's CPUFREQ_GOV_LIMITS notification, which will also call __cpufreq_driver_target(). And hence we end up issuing concurrent calls to ->target(). Typically, platforms have the following logic in their ->target() routines: (Eg: cpufreq-cpu0, omap, exynos, etc) A. If new freq is more than old: Increase voltage B. Change freq C. If new freq is less than old: decrease voltage Now, if the two concurrent calls to ->target() are X and Y, where X is trying to increase the freq and Y is trying to decrease it, we get the following race condition: X.A: voltage gets increased for larger freq Y.A: nothing happens Y.B: freq gets decreased Y.C: voltage gets decreased X.B: freq gets increased X.C: nothing happens Thus we can end up setting a freq which is not supported by the voltage we have set. That will probably make the clock to the CPU unstable and the system might not work properly anymore. This patchset introduces a new set of routines cpufreq_freq_transition_begin() and cpufreq_freq_transition_end(), which will guarantee that calls to frequency transition routines are serialized. Later patches force other drivers to use these new routines. V4: https://lkml.org/lkml/2014/3/21/23 V4->V5: - Replaced false with 0 as the variable was of int type instead of bool. - There were some discussions about requirement of a barrier, but it looks like overkill for now. So, leaving that unless we have a real problem. Srivatsa S. Bhat (1): cpufreq: Make sure frequency transitions are serialized Viresh Kumar (2): cpufreq: Convert existing drivers to use cpufreq_freq_transition_{begin|end} cpufreq: Make cpufreq_notify_transition & cpufreq_notify_post_transition static drivers/cpufreq/cpufreq-nforce2.c | 4 +-- drivers/cpufreq/cpufreq.c | 52 +++++++++++++++++++++++++++++------- drivers/cpufreq/exynos5440-cpufreq.c | 4 +-- drivers/cpufreq/gx-suspmod.c | 4 +-- drivers/cpufreq/integrator-cpufreq.c | 4 +-- drivers/cpufreq/longhaul.c | 4 +-- drivers/cpufreq/pcc-cpufreq.c | 4 +-- drivers/cpufreq/powernow-k6.c | 4 +-- drivers/cpufreq/powernow-k7.c | 4 +-- drivers/cpufreq/powernow-k8.c | 4 +-- drivers/cpufreq/s3c24xx-cpufreq.c | 4 +-- drivers/cpufreq/sh-cpufreq.c | 4 +-- drivers/cpufreq/unicore2-cpufreq.c | 4 +-- include/linux/cpufreq.h | 12 ++++++--- 14 files changed, 76 insertions(+), 36 deletions(-) -- 1.7.12.rc2.18.g61b472e

10 years, 3 months

[PATCH] cpufreq: resume drivers before enabling governors

by Viresh Kumar

During suspend, we first stop governors and then suspend cpufreq drivers and resume must be exactly opposite of that. i.e. resume drivers first and then start governors. But the current code in resume enables governors first and then resume drivers. Fix it be changing code sequence there. Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org> --- For 3.15-rc2 .. drivers/cpufreq/cpufreq.c | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c index 3aa7a7a..d8d6bc9 100644 --- a/drivers/cpufreq/cpufreq.c +++ b/drivers/cpufreq/cpufreq.c @@ -1652,14 +1652,13 @@ void cpufreq_resume(void) cpufreq_suspended = false; list_for_each_entry(policy, &cpufreq_policy_list, policy_list) { - if (__cpufreq_governor(policy, CPUFREQ_GOV_START) + if (cpufreq_driver->resume && cpufreq_driver->resume(policy)) + pr_err("%s: Failed to resume driver: %p\n", __func__, + policy); + else if (__cpufreq_governor(policy, CPUFREQ_GOV_START) || __cpufreq_governor(policy, CPUFREQ_GOV_LIMITS)) pr_err("%s: Failed to start governor for policy: %p\n", __func__, policy); - else if (cpufreq_driver->resume - && cpufreq_driver->resume(policy)) - pr_err("%s: Failed to resume driver: %p\n", __func__, - policy); /* * schedule call cpufreq_update_policy() for boot CPU, i.e. last -- 1.7.12.rc2.18.g61b472e

10 years, 3 months

Re: [RFC v3 0/5] cpufreq:LAB: Support for LAB governor.

by Viresh Kumar

On 17 March 2014 21:08, Lukasz Majewski <l.majewski(a)samsung.com> wrote: >> Despite this patch set is working and applicable on top of 3.14-rc5, >> please regard it solely as a pure RFC. >> >> This patch provides support for LAB governor build on top of ondemand. >> Previous version of LAB can be found here: >> http://thread.gmane.org/gmane.linux.kernel/1484746/match=cpufreq >> >> LAB short reminder: >> >> LAB uses information about how many cores are in "idle" state (the >> core idleness is represented as the value between 0 and 100) and the >> overall load of the system (from 0 to 100) to decide about frequency >> to be set. It is extremely useful with SoCs like Exynos4412, which >> can set only one frequency for all cores. >> >> Important design decisions: >> >> - Reuse well established ondemand governor's internal code. To do this >> I had to expose some previously static internal ondemand code. >> This allowed smaller LAB code when compared to previous version. >> >> - LAB works on top of ondemand, which means that one via device tree >> attributes can specify if and when e.g. BOOST shall be enabled or >> if any particular frequency shall be imposed. For situation NOT >> important from the power consumption reduction viewpoint the ondemand >> is used to set proper frequency. >> >> - It is only possible to either compile in or not the LAB into the >> kernel. There is no "M" option for Kconfig. It is done on purpose, >> since ondemand itself can be also compiled as a module and then it >> would be possible to remove ondemand when LAB is working on top of it. >> >> - The LAB operation is specified (and thereof extendable) via device >> tree lab-ctrl-freq attribute defined at /cpus/cpu0. >> >> >> Problems: >> - How the governor will work for big.LITTLE systems (especially >> Global Task Scheduling). >> - Will there be agreement to expose internal ondemand code to be >> reused for more specialized governors. >> >> Test HW: >> Exynos4412 - Trats2 board. >> Above patches were posted on top of Linux 3.14-rc5 >> (SHA1: 3f9590c281c66162bf8ae9b7b2d987f0a89043c6) >> > > Any comments about those patches? Sorry for being late on reviewing these.. I tried to go through the patches but didn't looked at the minutest of the details. Its been a long time when you first sent this patchset. And the memories have corrupted by now :) .. To get context back, can we discuss again the fundamentals behind this new governor you are proposing. And then we can discuss about it again, its pros/cons, etc.. I tried to go to earlier threads but I think we better do it again.. People are reluctant in getting another governor in and want to give existing governors a try if possible. So, please explain the basics behind your governor again and then we can put our arguments again.. -- viresh

10 years, 3 months

[PATCH V4 0/3] cpufreq: Introduce cpufreq_freq_transition_{begin|end}()

by Viresh Kumar

Whenever we change the frequency of a CPU, we call the PRECHANGE and POSTCHANGE notifiers. They must be serialized, i.e. PRECHANGE and POSTCHANGE notifiers should strictly alternate, thereby preventing two different sets of PRECHANGE or POSTCHANGE notifiers from interleaving arbitrarily. The following examples illustrate why this is important: Scenario 1: ----------- A thread reading the value of cpuinfo_cur_freq, will call __cpufreq_cpu_get()->cpufreq_out_of_sync()->cpufreq_notify_transition() The ondemand governor can decide to change the frequency of the CPU at the same time and hence it can end up sending the notifications via ->target(). If the notifiers are not serialized, the following sequence can occur: - PRECHANGE Notification for freq A (from cpuinfo_cur_freq) - PRECHANGE Notification for freq B (from target()) - Freq changed by target() to B - POSTCHANGE Notification for freq B - POSTCHANGE Notification for freq A We can see from the above that the last POSTCHANGE Notification happens for freq A but the hardware is set to run at freq B. Where would we break then?: adjust_jiffies() in cpufreq.c & cpufreq_callback() in arch/arm/kernel/smp.c (which also adjusts the jiffies). All the loops_per_jiffy calculations will get messed up. Scenario 2: ----------- The governor calls __cpufreq_driver_target() to change the frequency. At the same time, if we change scaling_{min|max}_freq from sysfs, it will end up calling the governor's CPUFREQ_GOV_LIMITS notification, which will also call __cpufreq_driver_target(). And hence we end up issuing concurrent calls to ->target(). Typically, platforms have the following logic in their ->target() routines: (Eg: cpufreq-cpu0, omap, exynos, etc) A. If new freq is more than old: Increase voltage B. Change freq C. If new freq is less than old: decrease voltage Now, if the two concurrent calls to ->target() are X and Y, where X is trying to increase the freq and Y is trying to decrease it, we get the following race condition: X.A: voltage gets increased for larger freq Y.A: nothing happens Y.B: freq gets decreased Y.C: voltage gets decreased X.B: freq gets increased X.C: nothing happens Thus we can end up setting a freq which is not supported by the voltage we have set. That will probably make the clock to the CPU unstable and the system might not work properly anymore. This patchset introduces a new set of routines cpufreq_freq_transition_begin() and cpufreq_freq_transition_end(), which will guarantee that calls to frequency transition routines are serialized. Later patches force other drivers to use these new routines. Srivatsa S. Bhat (1): cpufreq: Make sure frequency transitions are serialized Viresh Kumar (2): cpufreq: Convert existing drivers to use cpufreq_freq_transition_{begin|end} cpufreq: Make cpufreq_notify_transition & cpufreq_notify_post_transition static drivers/cpufreq/cpufreq-nforce2.c | 4 +-- drivers/cpufreq/cpufreq.c | 52 +++++++++++++++++++++++++++++------- drivers/cpufreq/exynos5440-cpufreq.c | 4 +-- drivers/cpufreq/gx-suspmod.c | 4 +-- drivers/cpufreq/integrator-cpufreq.c | 4 +-- drivers/cpufreq/longhaul.c | 4 +-- drivers/cpufreq/pcc-cpufreq.c | 4 +-- drivers/cpufreq/powernow-k6.c | 4 +-- drivers/cpufreq/powernow-k7.c | 4 +-- drivers/cpufreq/powernow-k8.c | 4 +-- drivers/cpufreq/s3c24xx-cpufreq.c | 4 +-- drivers/cpufreq/sh-cpufreq.c | 4 +-- drivers/cpufreq/unicore2-cpufreq.c | 4 +-- include/linux/cpufreq.h | 12 ++++++--- 14 files changed, 76 insertions(+), 36 deletions(-) -- 1.7.12.rc2.18.g61b472e

10 years, 3 months

arm-soc boot: 35 pass, 7 fail (v3.14-rc5-1219-g941704b)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: arm-soc Git describe: v3.14-rc5-1219-g941704b 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 legacy,dm365evm: FAIL: davinci_all_defconfig Full Report =========== omap2plus_defconfig ------------------- legacy,3730xm PASS: 0 min 52.3 sec am335x-boneblack PASS: 0 min 26.1 sec omap3-beagle-xm PASS: 1 min 0.9 sec legacy,3530beagle PASS: 0 min 47.5 sec omap4-panda PASS: 1 min 11.5 sec omap3-overo-tobi PASS: 0 min 23.7 sec am335x-bone PASS: 0 min 27.9 sec omap3-overo-storm-tobi PASS: 0 min 25.9 sec omap4-panda-es PASS: 1 min 9.4 sec legacy,3730storm PASS: 0 min 23.8 sec legacy,3530overo PASS: 0 min 21.7 sec multi_lpae_defconfig -------------------- sun7i-a20-cubieboard2 FAIL: 0 min 20.1 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 22.9 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 18.9 sec imx6dl-wandboard,wand-solo PASS: 0 min 19.2 sec imx6q-wandboard PASS: 0 min 17.4 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 FAIL: 0 min 18.2 sec sun4i-a10-cubieboard FAIL: 0 min 19.0 sec bcm_defconfig ------------- bcm28155-ap PASS: 0 min 54.5 sec mvebu_v7_defconfig ------------------ armada-xp-openblocks-ax3-4 PASS: 0 min 22.3 sec armada-370-mirabox PASS: 0 min 20.5 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 29.9 sec multi_v7_defconfig ------------------ ste-snowball FAIL: 0 min 30.5 sec tegra30-beaver PASS: 0 min 17.0 sec am335x-boneblack PASS: 0 min 24.0 sec omap3-beagle-xm PASS: 0 min 48.8 sec sun7i-a20-cubieboard2 FAIL: 0 min 31.4 sec armada-370-mirabox PASS: 0 min 22.5 sec omap4-panda PASS: 0 min 55.2 sec armada-xp-openblocks-ax3-4 PASS: 0 min 25.0 sec sun4i-a10-cubieboard FAIL: 0 min 19.8 sec bcm28155-ap PASS: 1 min 15.0 sec omap3-overo-tobi PASS: 0 min 22.4 sec imx6dl-wandboard,wand-solo PASS: 0 min 18.2 sec am335x-bone PASS: 0 min 26.8 sec omap3-overo-storm-tobi PASS: 0 min 24.6 sec imx6q-wandboard PASS: 0 min 17.4 sec omap4-panda-es PASS: 0 min 54.3 sec imx6dl-wandboard,wand-dual PASS: 0 min 18.3 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 33.5 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.2 sec davinci_all_defconfig --------------------- legacy,dm365evm FAIL: 0 min 31.4 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-3cdZIw/zImage tftp 0x40008000 192.168.1.2:tmp/cubie2-3cdZIw/zImage Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.153 Filename 'tmp/cubie2-3cdZIw/zImage'. Load address: 0x40008000 Loading: *################################################################# ################################################################# ################################################################# ################################################################# ################################################## 2.7 MiB/s done Bytes transferred = 4546440 (455f88 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-3cdZIw/sun7i-a20-cubieboard2.dtb tftp 0x41000000 192.168.1.2:tmp/cubie2-3cdZIw/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-3cdZIw/sun7i-a20-cubieboard2.dtb'. Load address: 0x41000000 Loading: *## 2.5 MiB/s done Bytes transferred = 18205 (471d 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 - 0x455f88 ] ## 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 40ff8000, end 40fff71c ... OK Starting kernel ... ~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 20.05 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-As9Qlu/zImage tftp 0x40008000 192.168.1.2:tmp/cubie2-As9Qlu/zImage Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.153 Filename 'tmp/cubie2-As9Qlu/zImage'. Load address: 0x40008000 Loading: *################################################################# ######################################################### 2.7 MiB/s done Bytes transferred = 1780312 (1b2a58 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-As9Qlu/sun7i-a20-cubieboard2.dtb tftp 0x41000000 192.168.1.2:tmp/cubie2-As9Qlu/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-As9Qlu/sun7i-a20-cubieboard2.dtb'. Load address: 0x41000000 Loading: *## 2.2 MiB/s done Bytes transferred = 18205 (471d 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 - 0x1b2a58 ] ## 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 40ff8000, end 40fff71c ... OK Starting kernel ... ~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 18.25 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-8Aqx3l/zImage tftp 0x40008000 192.168.1.2:tmp/cubie-8Aqx3l/zImage Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.193 Filename 'tmp/cubie-8Aqx3l/zImage'. Load address: 0x40008000 Loading: *################################################################# ######################################################### 2.7 MiB/s done Bytes transferred = 1780312 (1b2a58 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-8Aqx3l/sun4i-a10-cubieboard.dtb tftp 0x41000000 192.168.1.2:tmp/cubie-8Aqx3l/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-8Aqx3l/sun4i-a10-cubieboard.dtb'. Load address: 0x41000000 Loading: *## 2.1 MiB/s done Bytes transferred = 15168 (3b40 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 - 0x1b2a58 ] ## 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 40fffb3f ... OK Starting kernel ... ~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 19.03 seconds. # PYBOOT: Result: FAIL multi_v7_defconfig ------------------ ste-snowball: FAIL: last 80 lines of boot log: ---------------------------------------------- Command(snowball console)> hardreset (user:khilman) Reboot snowball Reboot: snowball ; ip9258 2 2 : ('off', 6, 'on') , sleep 6, 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 U8500 $ versionsetenv ethaddr 6e:e6:84:36:8e:9e U-Boot 2009.11 (sept. 19 2011 - 17:03:11) U8500 $ setenv ethaddr 6e:e6:84:36:8e:9esetenv bootargs console=ttyAMA2,115200n8 debug earlyprintk rw root=/dev/mmcblk0p3 rootwait rootfstype=ext4 Can't overwrite "ethaddr" U8500 $ setenv bootargs console=ttyAMA2,115200n8 debug earlyprintk rw root=/dev/mmcblk0p3 rootwait rootfstype=ext4setenv netargs 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}::::192.168.1.254:none' U8500 $ setenv netargs 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}::::192.168.1.254:none'if test -n ${initenv}; then run initenv; fi U8500 $ if test -n ${initenv}; then run initenv; fiif test -n ${preboot}; then run preboot; fi U8500 $ if test -n ${preboot}; then run preboot; fisetenv autoload no; setenv autoboot no U8500 $ setenv autoload no; setenv autoboot nodhcp U8500 $ dhcp smc911x: detected LAN9221 controller smc911x: phy initialized smc911x: MAC 6e:e6:84:36:8e:9e BOOTP broadcast 1 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-RzDqk9/tmp0ho1N7-uImage tftp 0x00800000 192.168.1.2:tmp/snowball-RzDqk9/tmp0ho1N7-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-RzDqk9/tmp0ho1N7-uImage'. Load address: 0x800000 Loading: *################################################################# ################################################################# ################################################################# ################################################################# ################################################### done Bytes transferred = 4562425 (459df9 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: 4562361 Bytes = 4.4 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: 30.50 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.39 seconds. # PYBOOT: Result: FAIL sun4i-a10-cubieboard: FAIL: last 80 lines of boot log: ------------------------------------------------------ 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-iVe2Zi/zImage tftp 0x40008000 192.168.1.2:tmp/cubie-iVe2Zi/zImage Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.193 Filename 'tmp/cubie-iVe2Zi/zImage'. Load address: 0x40008000 Loading: *################################################################# ################################################################# ################################################################# ################################################################# ################################################ 2.7 MiB/s done Bytes transferred = 4521112 (44fc98 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-iVe2Zi/sun4i-a10-cubieboard.dtb tftp 0x41000000 192.168.1.2:tmp/cubie-iVe2Zi/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-iVe2Zi/sun4i-a10-cubieboard.dtb'. Load address: 0x41000000 Loading: *## 2.1 MiB/s done Bytes transferred = 15168 (3b40 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 - 0x44fc98 ] ## 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 40fffb3f ... OK Starting kernel ... ~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 19.75 seconds. # PYBOOT: Result: FAIL davinci_all_defconfig --------------------- legacy,dm365evm: FAIL: last 80 lines of boot log: ------------------------------------------------- Connected to dm365evm console [channel connected] (~$quit to exit) (user:khilman) is already connected ~$hardreset Command(dm365evm console)> hardreset (user:khilman) Reboot dm365evm Reboot: dm365evm ; phidget 4 1 : ('off', 4, 'on') , sleep 4, ~$off # PYBOOT: Exception: ERROR: Could not break into autoboot. # PYBOOT: Time: 31.38 seconds. # PYBOOT: Result: FAIL

10 years, 3 months

arm-soc boot: 34 pass, 8 fail (v3.14-rc5-1214-gf08beab)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: arm-soc Git describe: v3.14-rc5-1214-gf08beab 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 bcm28155-ap: FAIL: multi_v7_defconfig legacy,dm365evm: FAIL: davinci_all_defconfig Full Report =========== omap2plus_defconfig ------------------- legacy,3730xm PASS: 0 min 51.8 sec am335x-boneblack PASS: 0 min 26.1 sec omap3-beagle-xm PASS: 1 min 1.8 sec legacy,3530beagle PASS: 1 min 23.0 sec omap4-panda PASS: 1 min 7.0 sec omap3-overo-tobi PASS: 0 min 23.7 sec am335x-bone PASS: 0 min 27.8 sec omap3-overo-storm-tobi PASS: 0 min 24.9 sec omap4-panda-es PASS: 1 min 14.5 sec legacy,3730storm PASS: 0 min 23.8 sec legacy,3530overo PASS: 0 min 21.7 sec multi_lpae_defconfig -------------------- sun7i-a20-cubieboard2 FAIL: 0 min 20.1 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.0 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 19.1 sec imx6dl-wandboard,wand-solo PASS: 0 min 19.0 sec imx6q-wandboard PASS: 0 min 17.5 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 FAIL: 0 min 18.1 sec sun4i-a10-cubieboard FAIL: 0 min 18.9 sec bcm_defconfig ------------- bcm28155-ap PASS: 1 min 4.1 sec mvebu_v7_defconfig ------------------ armada-xp-openblocks-ax3-4 PASS: 0 min 22.2 sec armada-370-mirabox PASS: 0 min 20.5 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 29.9 sec multi_v7_defconfig ------------------ ste-snowball FAIL: 0 min 30.6 sec tegra30-beaver PASS: 0 min 17.0 sec am335x-boneblack PASS: 0 min 24.2 sec omap3-beagle-xm PASS: 0 min 50.0 sec sun7i-a20-cubieboard2 FAIL: 0 min 31.4 sec armada-370-mirabox PASS: 0 min 22.4 sec omap4-panda PASS: 0 min 52.7 sec armada-xp-openblocks-ax3-4 PASS: 0 min 25.1 sec sun4i-a10-cubieboard FAIL: 0 min 23.2 sec bcm28155-ap FAIL: 16 min 16.2 sec omap3-overo-tobi PASS: 0 min 22.5 sec imx6dl-wandboard,wand-solo PASS: 0 min 23.4 sec am335x-bone PASS: 0 min 26.9 sec omap3-overo-storm-tobi PASS: 0 min 24.7 sec imx6q-wandboard PASS: 0 min 17.3 sec omap4-panda-es PASS: 0 min 55.5 sec imx6dl-wandboard,wand-dual PASS: 0 min 19.0 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 30.0 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.1 sec davinci_all_defconfig --------------------- legacy,dm365evm FAIL: 0 min 31.6 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-bzsFdC/zImage tftp 0x40008000 192.168.1.2:tmp/cubie2-bzsFdC/zImage Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.153 Filename 'tmp/cubie2-bzsFdC/zImage'. Load address: 0x40008000 Loading: *################################################################# ################################################################# ################################################################# ################################################################# #################################################### 2.7 MiB/s done Bytes transferred = 4565680 (45aab0 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-bzsFdC/sun7i-a20-cubieboard2.dtb tftp 0x41000000 192.168.1.2:tmp/cubie2-bzsFdC/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-bzsFdC/sun7i-a20-cubieboard2.dtb'. Load address: 0x41000000 Loading: *## 2.2 MiB/s done Bytes transferred = 18205 (471d 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 - 0x45aab0 ] ## 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 40ff8000, end 40fff71c ... OK Starting kernel ... ~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 20.07 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-ZYvpkm/zImage tftp 0x40008000 192.168.1.2:tmp/cubie2-ZYvpkm/zImage Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.153 Filename 'tmp/cubie2-ZYvpkm/zImage'. Load address: 0x40008000 Loading: *################################################################# ######################################################### 2.7 MiB/s done Bytes transferred = 1780312 (1b2a58 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-ZYvpkm/sun7i-a20-cubieboard2.dtb tftp 0x41000000 192.168.1.2:tmp/cubie2-ZYvpkm/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-ZYvpkm/sun7i-a20-cubieboard2.dtb'. Load address: 0x41000000 Loading: *## 2.2 MiB/s done Bytes transferred = 18205 (471d 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 - 0x1b2a58 ] ## 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 40ff8000, end 40fff71c ... OK Starting kernel ... ~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 18.11 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-N7m_Gy/zImage tftp 0x40008000 192.168.1.2:tmp/cubie-N7m_Gy/zImage Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.193 Filename 'tmp/cubie-N7m_Gy/zImage'. Load address: 0x40008000 Loading: *################################################################# ######################################################### 2.7 MiB/s done Bytes transferred = 1780312 (1b2a58 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-N7m_Gy/sun4i-a10-cubieboard.dtb tftp 0x41000000 192.168.1.2:tmp/cubie-N7m_Gy/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-N7m_Gy/sun4i-a10-cubieboard.dtb'. Load address: 0x41000000 Loading: *## 2.4 MiB/s done Bytes transferred = 15168 (3b40 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 - 0x1b2a58 ] ## 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 40fffb3f ... OK Starting kernel ... ~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 18.95 seconds. # PYBOOT: Result: FAIL multi_v7_defconfig ------------------ ste-snowball: FAIL: last 80 lines of boot log: ---------------------------------------------- U-Boot 2009.11 (sept. 19 2011 - 17:03:11) 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 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-WscmGH/tmpHpYFIO-uImage tftp 0x00800000 192.168.1.2:tmp/snowball-WscmGH/tmpHpYFIO-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-WscmGH/tmpHpYFIO-uImage'. Load address: 0x800000 Loading: *################################################################# ################################################################# ################################################################# ################################################################# ##################################################### done Bytes transferred = 4580665 (45e539 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: 4580601 Bytes = 4.4 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: 30.58 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.39 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-Q6gJ6K/zImage tftp 0x40008000 192.168.1.2:tmp/cubie-Q6gJ6K/zImage Using emac device TFTP from server 192.168.1.2; our IP address is 192.168.1.193 Filename 'tmp/cubie-Q6gJ6K/zImage'. Load address: 0x40008000 Loading: *################################################################# ################################################################# ################################################################# ################################################################# ################################################## 2.7 MiB/s done Bytes transferred = 4539352 (4543d8 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-Q6gJ6K/sun4i-a10-cubieboard.dtb tftp 0x41000000 192.168.1.2:tmp/cubie-Q6gJ6K/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-Q6gJ6K/sun4i-a10-cubieboard.dtb'. Load address: 0x41000000 Loading: *## 2.1 MiB/s done Bytes transferred = 15168 (3b40 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 - 0x4543d8 ] ## 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 40fffb3f ... OK Starting kernel ... ~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 23.21 seconds. # PYBOOT: Result: FAIL bcm28155-ap: FAIL: last 80 lines of boot log: --------------------------------------------- [ 1.020000] devtmpfs: mounted [ 1.030000] Freeing unused kernel memory: 532K (c0a3e000 - c0ac3000) [ 1.060000] Internal error: Oops - undefined instruction: 0 [#1] SMP ARM <LAVA_DISPATCHER>2014-03-21 07:44:36 PM WARNING: Sending newline in case of corruption. <LAVA_DISPATCHER>2014-03-21 07:45:06 PM WARNING: Sending newline in case of corruption. <LAVA_DISPATCHER>2014-03-21 07:45:36 PM WARNING: Sending newline in case of corruption. <LAVA_DISPATCHER>2014-03-21 07:46:07 PM WARNING: Sending newline in case of corruption. <LAVA_DISPATCHER>2014-03-21 07:46:37 PM WARNING: Sending newline in case of corruption. <LAVA_DISPATCHER>2014-03-21 07:47:07 PM WARNING: Sending newline in case of corruption. <LAVA_DISPATCHER>2014-03-21 07:47:37 PM INFO: Boot linaro image failed: Timeout exceeded in read_nonblocking(). <lava_dispatcher.utils.logging_spawn object at 0xa16b02c> version: 2.4 ($Revision: 516 $) command: /usr/bin/conmux-console args: [u'/usr/bin/conmux-console', u'vence/capri'] searcher: searcher_re: 0: re.compile("root@bcm-capri-board:~#") buffer (last 100 chars): 0a3e000 - c0ac3000) [ 1.060000] Internal error: Oops - undefined instruction: 0 [#1] SMP ARM before (last 100 chars): 0a3e000 - c0ac3000) [ 1.060000] Internal error: Oops - undefined instruction: 0 [#1] SMP ARM after: <class 'pexpect.TIMEOUT'> match: None match_index: None exitstatus: None flag_eof: False pid: 6386 child_fd: 3 closed: False timeout: 1200 delimiter: <class 'pexpect.EOF'> logfile: None logfile_read: <lava_dispatcher.context.Flusher object at 0x9a9860c> logfile_send: None maxread: 2000 ignorecase: False searchwindowsize: None delaybeforesend: 0.05 delayafterclose: 0.1 delayafterterminate: 0.1 <LAVA_DISPATCHER>2014-03-21 07:47:37 PM INFO: Booting the test image. Attempt: 2 < waiting for device > <LAVA_DISPATCHER>2014-03-21 07:47:39 PM INFO: Perform hard reset on the system Reboot: capri ; ip9258 1 3 : off, sleep, on < waiting for device > <LAVA_DISPATCHER>2014-03-21 07:57:41 PM ERROR: boot_linaro_image failed Traceback (most recent call last): File "/home/khilman/work.local/lava/lava-dispatcher/lava_dispatcher/actions/boot_control.py", line 105, in run client.boot_linaro_image() File "/home/khilman/work.local/lava/lava-dispatcher/lava_dispatcher/client/base.py", line 508, in boot_linaro_image self._boot_linaro_image() File "/home/khilman/work.local/lava/lava-dispatcher/lava_dispatcher/client/base.py", line 481, in _boot_linaro_image self.proc = self.target_device.power_on() File "/home/khilman/work.local/lava/lava-dispatcher/lava_dispatcher/device/capri.py", line 114, in power_on self.fastboot('reboot') File "/home/khilman/work.local/lava/lava-dispatcher/lava_dispatcher/device/fastboot.py", line 57, in __call__ _call(self.context, command, ignore_failure, timeout) File "/home/khilman/work.local/lava/lava-dispatcher/lava_dispatcher/device/fastboot.py", line 45, in _call context.run_command(cmd, failok=ignore_failure) File "/home/khilman/work.local/lava/lava-dispatcher/lava_dispatcher/context.py", line 153, in run_command rc = subprocess.check_call(command, **output_args) File "/usr/lib/python2.7/subprocess.py", line 511, in check_call raise CalledProcessError(retcode, cmd) CalledProcessError: Command '['nice', 'sh', '-c', u'timeout 600s flock /var/lock/lava-fastboot.lck fastboot -s 1234567890 reboot']' returned non-zero exit status 124 <LAVA_DISPATCHER>2014-03-21 07:57:41 PM INFO: CriticalError <LAVA_DISPATCHER>2014-03-21 07:57:41 PM WARNING: [ACTION-E] boot_linaro_image is finished with error (Failed to boot test image.). ErrorMessage: Failed to boot test image. Lava failed at action boot_linaro_image with error:Failed to boot test image. Traceback (most recent call last): File "/home/khilman/work.local/lava/lava-dispatcher/lava_dispatcher/job.py", line 270, in run action.run(**params) File "/home/khilman/work.local/lava/lava-dispatcher/lava_dispatcher/actions/boot_control.py", line 109, in run raise CriticalError("Failed to boot test image.") CriticalError: Failed to boot test image. Reboot: capri ; ip9258 1 3 : ['off'] <LAVA_DISPATCHER>2014-03-21 07:57:42 PM INFO: Submitting the test result with parameters = {u'token': '<HIDDEN>', u'stream': u'/anonymous/lboot/', u'server': u'http://khilman@lava.lan/RPC2/'} <LAVA_DISPATCHER>2014-03-21 07:57:42 PM INFO: Dashboard : http://lava.lan/dashboard/permalink/bundle/589e215cd844b26ee3c8b892db0609d6… LBOOT: Result: FAIL LBOOT: Time: 976.18 seconds. davinci_all_defconfig --------------------- legacy,dm365evm: FAIL: last 80 lines of boot log: ------------------------------------------------- Connected to dm365evm console [channel connected] (~$quit to exit) (user:khilman) is already connected ~$hardreset Command(dm365evm console)> hardreset (user:khilman) Reboot dm365evm Reboot: dm365evm ; phidget 4 1 : ('off', 4, 'on') , sleep 4, ~$off # PYBOOT: Exception: ERROR: Could not break into autoboot. # PYBOOT: Time: 31.60 seconds. # PYBOOT: Result: FAIL

10 years, 3 months

arm-soc boot: 21 pass, 1 fail (v3.14-rc5-1212-g251ef77)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: arm-soc Git describe: v3.14-rc5-1212-g251ef77 Failed boot tests (console logs at the end) =========================================== legacy,dm365evm: FAIL: davinci_all_defconfig Full Report =========== omap2plus_defconfig ------------------- legacy,3730xm PASS: 0 min 52.4 sec am335x-boneblack PASS: 0 min 26.1 sec omap3-beagle-xm PASS: 0 min 59.6 sec legacy,3530beagle PASS: 0 min 47.8 sec omap4-panda PASS: 1 min 6.6 sec omap3-overo-tobi PASS: 0 min 23.8 sec am335x-bone PASS: 0 min 27.9 sec omap3-overo-storm-tobi PASS: 0 min 23.0 sec omap4-panda-es PASS: 1 min 9.4 sec legacy,3730storm PASS: 0 min 23.6 sec legacy,3530overo PASS: 0 min 21.9 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 19.3 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 18.9 sec imx6dl-wandboard,wand-solo PASS: 0 min 19.1 sec imx6q-wandboard PASS: 0 min 17.5 sec bcm_defconfig ------------- bcm28155-ap PASS: 1 min 9.8 sec mvebu_v7_defconfig ------------------ armada-xp-openblocks-ax3-4 PASS: 0 min 22.5 sec armada-370-mirabox PASS: 0 min 20.4 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 30.2 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 30.3 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.1 sec davinci_all_defconfig --------------------- legacy,dm365evm FAIL: 0 min 31.4 sec Console logs for failures ========================= davinci_all_defconfig --------------------- legacy,dm365evm: FAIL: last 80 lines of boot log: ------------------------------------------------- Connected to dm365evm console [channel connected] (~$quit to exit) (user:khilman) is already connected ~$hardreset Command(dm365evm console)> hardreset (user:khilman) Reboot dm365evm Reboot: dm365evm ; phidget 4 1 : ('off', 4, 'on') , sleep 4, ~$off # PYBOOT: Exception: ERROR: Could not break into autoboot. # PYBOOT: Time: 31.38 seconds. # PYBOOT: Result: FAIL

10 years, 3 months

← Newer
1
...
6
7
8
9
10
11
12
...
23
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel March 2014