Full logs are available at http://arm-soc.lixom.net/bootlogs/arm-soc/v3.16-rc6-1009-g709032a/
Failed boards:
bbb arm-multi_v7_defconfig : FAILED 1:06.42 omap5uevm arm-multi_v7_defconfig : FAILED 1:15.77 omap5uevm arm-multi_lpae_defconfig : FAILED 1:13.66 pandaes arm-multi_v7_defconfig : FAILED 2:13.70
Successful boards:
apc arm-vt8500_v6_v7_defconfig : passed 1:15.06 arndale arm-exynos_defconfig : passed 1:40.84 arndale arm-multi_v7_defconfig : passed 1:31.66 arndale arm-multi_lpae_defconfig : passed 1:27.74 bbb arm-omap2plus_defconfig : passed 1:38.58 beaver arm-tegra_defconfig : passed 1:03.19 beaver arm-multi_v7_defconfig : passed 0:54.13 capri arm-bcm_defconfig : passed 0:39.59 capri arm-multi_v7_defconfig : passed 0:40.82 colombus arm-sunxi_defconfig : passed 0:56.30 colombus arm-multi_v7_defconfig : passed 1:44.31 colombus arm-multi_lpae_defconfig : passed 1:02.62 cubie arm-sunxi_defconfig : passed 1:09.11 cubie arm-multi_v7_defconfig : passed 0:57.46 cubie2 arm-sunxi_defconfig : passed 1:06.91 cubie2 arm-multi_v7_defconfig : passed 1:09.43 cubie2 arm-multi_lpae_defconfig : passed 0:59.20 cubox arm-multi_v7_defconfig : passed 1:02.98 dalmore arm-tegra_defconfig : passed 2:28.49 dalmore arm-multi_v7_defconfig : passed 1:17.50 dalmore arm-multi_lpae_defconfig : passed 1:14.34 hummingboard arm-imx_v6_v7_defconfig : passed 1:25.95 hummingboard arm-multi_v7_defconfig : passed 1:13.37 jetsontk1 arm-tegra_defconfig : passed 1:00.62 jetsontk1 arm-multi_v7_defconfig : passed 0:56.33 odroidu3 arm-exynos_defconfig : passed 1:07.44 omap5uevm arm-omap2plus_defconfig : warnings 0:59.93 pandaes arm-omap2plus_defconfig : warnings 1:52.16 pi arm-exynos_defconfig : passed 0:59.47 pi arm-multi_v7_defconfig : passed 0:49.04 pi arm-multi_lpae_defconfig : passed 0:50.57 pit arm-exynos_defconfig : passed 0:59.85 pit arm-multi_v7_defconfig : passed 0:52.60 pit arm-multi_lpae_defconfig : passed 0:50.22 sama5 arm-sama5_defconfig : passed 1:53.41 seaboard arm-tegra_defconfig : passed 1:18.77 seaboard arm-multi_v7_defconfig : passed 1:14.36 snow arm-exynos_defconfig : passed 1:00.63 snow arm-multi_v7_defconfig : passed 0:59.43 snow arm-multi_lpae_defconfig : passed 1:51.64 snowball arm-u8500_defconfig : passed 2:16.86 snowball arm-multi_v7_defconfig : passed 4:13.66 trimslice arm-tegra_defconfig : passed 1:01.34 trimslice arm-multi_v7_defconfig : passed 1:03.74 wandboard arm-imx_v6_v7_defconfig : passed 1:10.43 wandboard arm-multi_v7_defconfig : passed 0:53.35
Offline boards:
jetsontk1 arm-multi_lpae_defconfig : OFFLINE 1:23.72
Board legend is available at http://arm-soc.lixom.net/boards.html
Last entries of failed logs below:
========================================================================
Board bbb-arm-multi_v7_defconfig failure log: -------------------------------------------------
################################################################# ################################################################# ################################################################# ################################################################# ############### 1.2 MiB/s done Bytes transferred = 4990240 (4c2520 hex) U-Boot# setenv serverip 172.16.1.3 setenv serverip 172.16.1.3 U-Boot# tftp 0x81f00000 arm-soc/v3.16-rc6-1009-g709032a/arm-multi_v7_defconfig/dtbs/am335x-boneblack.dtb tftp 0x81f00000 arm-soc/v3.16-rc6-1009-g709032a/arm-multi_v7_defconfig/dtbs/am335x-boneblack.dtb link up on port 0, speed 100, full duplex Using cpsw device TFTP from server 172.16.1.3; our IP address is 172.16.1.119 Filename 'arm-soc/v3.16-rc6-1009-g709032a/arm-multi_v7_defconfig/dtbs/am335x-boneblack.dtb'. Load address: 0x81f00000 Loading: *## 729.5 KiB/s done Bytes transferred = 29162 (71ea hex) U-Boot# bootz 0x80200000 - 0x81f00000 ; bootm 0x80200000 - 0x81f00000
[PYBOOT] [bbb 00:28]: u-boot: jumping to kernel image bootz 0x80200000 - 0x81f00000 ; bootm 0x80200000 - 0x81f00000 ## Flattened Device Tree blob at 81f00000 Booting using the fdt blob at 0x81f00000 Using Device Tree in place at 81f00000, end 81f0a1e9
Starting kernel ...
[PYBOOT] [bbb 00:28]: u-boot: started kernel.
[PYBOOT] [bbb 01:03]: Timed out waiting for "<type 'str'>":
[PYBOOT] [bbb 01:04]: got exception: timeout ~$off
[PYBOOT] [bbb 01:05]: Done.
========================================================================
Board omap5uevm-arm-multi_lpae_defconfig failure log: -------------------------------------------------
################################################################# ################################################################# ############### 713.9 KiB/s done Bytes transferred = 4990240 (4c2520 hex) U-Boot# setenv serverip 172.16.1.3 setenv serverip 172.16.1.3 U-Boot# tftp 0x82000000 arm-soc/v3.16-rc6-1009-g709032a/arm-multi_lpae_defconfig/dtbs/omap5-uevm.dtb tftp 0x82000000 arm-soc/v3.16-rc6-1009-g709032a/arm-multi_lpae_defconfig/dtbs/omap5-uevm.dtb Waiting for Ethernet connection... done. Using sms0 device TFTP from server 172.16.1.3; our IP address is 172.16.1.146 Filename 'arm-soc/v3.16-rc6-1009-g709032a/arm-multi_lpae_defconfig/dtbs/omap5-uevm.dtb'. Load address: 0x82000000 Loading: *EHCI timed out on TD - token=0x88008d80 T #### 8.8 KiB/s done Bytes transferred = 49643 (c1eb hex) U-Boot# bootz 0x81000000 - 0x82000000 ; bootm 0x81000000 - 0x82000000
[PYBOOT] [omap5uevm 00:35]: u-boot: jumping to kernel image bootz 0x81000000 - 0x82000000 ; bootm 0x81000000 - 0x82000000 Kernel image @ 0x81000000 [ 0x000000 - 0x4c2520 ] ## Flattened Device Tree blob at 82000000 Booting using the fdt blob at 0x82000000 Using Device Tree in place at 82000000, end 8200f1ea
Starting kernel ... [PYBOOT] [omap5uevm 00:35]: u-boot: started kernel.
[PYBOOT] [omap5uevm 01:10]: Timed out waiting for "<type 'str'>":
[PYBOOT] [omap5uevm 01:11]: got exception: timeout ~$off
[PYBOOT] [omap5uevm 01:13]: Done.
========================================================================
Board omap5uevm-arm-multi_v7_defconfig failure log: -------------------------------------------------
################################################################# ################################################################# ############### 646.5 KiB/s done Bytes transferred = 4990240 (4c2520 hex) U-Boot# setenv serverip 172.16.1.3 setenv serverip 172.16.1.3 U-Boot# tftp 0x82000000 arm-soc/v3.16-rc6-1009-g709032a/arm-multi_v7_defconfig/dtbs/omap5-uevm.dtb tftp 0x82000000 arm-soc/v3.16-rc6-1009-g709032a/arm-multi_v7_defconfig/dtbs/omap5-uevm.dtb Waiting for Ethernet connection... done. Using sms0 device TFTP from server 172.16.1.3; our IP address is 172.16.1.146 Filename 'arm-soc/v3.16-rc6-1009-g709032a/arm-multi_v7_defconfig/dtbs/omap5-uevm.dtb'. Load address: 0x82000000 Loading: *EHCI timed out on TD - token=0x88008d80 T #### 8.8 KiB/s done Bytes transferred = 49643 (c1eb hex) U-Boot# bootz 0x81000000 - 0x82000000 ; bootm 0x81000000 - 0x82000000
[PYBOOT] [omap5uevm 00:37]: u-boot: jumping to kernel image bootz 0x81000000 - 0x82000000 ; bootm 0x81000000 - 0x82000000 Kernel image @ 0x81000000 [ 0x000000 - 0x4c2520 ] ## Flattened Device Tree blob at 82000000 Booting using the fdt blob at 0x82000000 Using Device Tree in place at 82000000, end 8200f1ea
Starting kernel ...
[PYBOOT] [omap5uevm 00:37]: u-boot: started kernel.
[PYBOOT] [omap5uevm 01:12]: Timed out waiting for "<type 'str'>":
[PYBOOT] [omap5uevm 01:13]: got exception: timeout ~$off
[PYBOOT] [omap5uevm 01:15]: Done.
========================================================================
Board pandaes-arm-multi_v7_defconfig failure log: -------------------------------------------------
[ 2.189941] platform wl12xx_vmmc: Driver reg-fixed-voltage requests probe deferral [ 2.197906] Waiting for root device /dev/mmcblk0p2... [ 2.198120] omap_i2c 48070000.i2c: could not find pctldev for node /ocp/pinmux@4a100040/pinmux_i2c1_pins, deferring probe [ 2.198638] platform 48070000.i2c: Driver omap_i2c requests probe deferral [ 2.198638] omap_i2c 48072000.i2c: could not find pctldev for node /ocp/pinmux@4a100040/pinmux_i2c2_pins, deferring probe [ 2.198638] platform 48072000.i2c: Driver omap_i2c requests probe deferral [ 2.199462] omap_i2c 48060000.i2c: could not find pctldev for node /ocp/pinmux@4a100040/pinmux_i2c3_pins, deferring probe [ 2.199462] platform 48060000.i2c: Driver omap_i2c requests probe deferral [ 2.199462] omap_i2c 48350000.i2c: could not find pctldev for node /ocp/pinmux@4a100040/pinmux_i2c4_pins, deferring probe [ 2.200134] platform 48350000.i2c: Driver omap_i2c requests probe deferral [ 2.201141] omap_hsmmc 4809c000.mmc: unable to get vmmc regulator -517 [ 2.201141] platform 4809c000.mmc: Driver omap_hsmmc requests probe deferral [ 2.201141] omap_hsmmc 480d5000.mmc: could not find pctldev for node /ocp/pinmux@4a100040/pinmux_wl12xx_pins, deferring probe [ 2.201721] platform 480d5000.mmc: Driver omap_hsmmc requests probe deferral [ 2.413513] hw-breakpoint: Failed to enable monitor mode on CPU 0. [ 2.420532] hw-breakpoint: CPU 0 failed to disable vector catch [ 2.488433] usb 1-1.1: new high-speed USB device number 3 using ehci-omap [ 2.603210] smsc95xx v1.0.4 [ 2.659667] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-4a064c00.ehci-1.1, smsc95xx USB 2.0 Ethernet, 9e:8c:2e:67:34:bb [ 2.671783] reg-fixed-voltage wl12xx_vmmc: could not find pctldev for node /ocp/pinmux@4a100040/pinmux_wl12xx_gpio, deferring probe [ 2.684356] platform wl12xx_vmmc: Driver reg-fixed-voltage requests probe deferral [ 2.692749] omap_i2c 48070000.i2c: could not find pctldev for node /ocp/pinmux@4a100040/pinmux_i2c1_pins, deferring probe [ 2.704406] platform 48070000.i2c: Driver omap_i2c requests probe deferral [ 2.711608] omap_i2c 48072000.i2c: could not find pctldev for node /ocp/pinmux@4a100040/pinmux_i2c2_pins, deferring probe [ 2.723571] platform 48072000.i2c: Driver omap_i2c requests probe deferral [ 2.730773] omap_i2c 48060000.i2c: could not find pctldev for node /ocp/pinmux@4a100040/pinmux_i2c3_pins, deferring probe [ 2.742767] platform 48060000.i2c: Driver omap_i2c requests probe deferral [ 2.742767] omap_i2c 48350000.i2c: could not find pctldev for node /ocp/pinmux@4a100040/pinmux_i2c4_pins, deferring probe [ 2.761962] platform 48350000.i2c: Driver omap_i2c requests probe deferral [ 2.761962] omap_hsmmc 4809c000.mmc: unable to get vmmc regulator -517 [ 2.776947] platform 4809c000.mmc: Driver omap_hsmmc requests probe deferral [ 2.784912] omap_hsmmc 480d5000.mmc: could not find pctldev for node /ocp/pinmux@4a100040/pinmux_wl12xx_pins, deferring probe [ 2.796783] platform 480d5000.mmc: Driver omap_hsmmc requests probe deferral
[PYBOOT] [pandaes 02:11]: Timed out waiting for "<type 'str'>":
[PYBOOT] [pandaes 02:12]: got exception: timeout ~$off
[PYBOOT] [pandaes 02:13]: Done.
On Wed, Jul 30, 2014 at 11:39 PM, Olof's autobooter build@lixom.net wrote:
Full logs are available at http://arm-soc.lixom.net/bootlogs/arm-soc/v3.16-rc6-1009-g709032a/
Failed boards:
bbb arm-multi_v7_defconfig : FAILED 1:06.42 omap5uevm arm-multi_v7_defconfig : FAILED 1:15.77 omap5uevm arm-multi_lpae_defconfig : FAILED 1:13.66 pandaes arm-multi_v7_defconfig : FAILED 2:13.70
This happened because ARCH_HISI wasn't selected, and the hisilicon platforms were the ones who used to bring in PINCTRL_SINGLE through a select.
Either we should remove the select from HISI, or we should add it to OMAP and others that need it. It's sort of silly to try to boot without pinctrl on these platforms, so selecting does make some sense...
-Olof
On Thu, Jul 31, 2014 at 12:21 AM, Olof Johansson olof@lixom.net wrote:
On Wed, Jul 30, 2014 at 11:39 PM, Olof's autobooter build@lixom.net wrote:
Full logs are available at http://arm-soc.lixom.net/bootlogs/arm-soc/v3.16-rc6-1009-g709032a/
Failed boards:
bbb arm-multi_v7_defconfig : FAILED 1:06.42 omap5uevm arm-multi_v7_defconfig : FAILED 1:15.77 omap5uevm arm-multi_lpae_defconfig : FAILED 1:13.66 pandaes arm-multi_v7_defconfig : FAILED 2:13.70
This happened because ARCH_HISI wasn't selected, and the hisilicon platforms were the ones who used to bring in PINCTRL_SINGLE through a select.
Either we should remove the select from HISI, or we should add it to OMAP and others that need it. It's sort of silly to try to boot without pinctrl on these platforms, so selecting does make some sense...
Btw, I've made sure hisi is now selected, so the immediate need for this has been resolved. Still, the fragility remains.
-Olof
* Olof Johansson olof@lixom.net [140731 10:25]:
On Thu, Jul 31, 2014 at 12:21 AM, Olof Johansson olof@lixom.net wrote:
On Wed, Jul 30, 2014 at 11:39 PM, Olof's autobooter build@lixom.net wrote:
Full logs are available at http://arm-soc.lixom.net/bootlogs/arm-soc/v3.16-rc6-1009-g709032a/
Failed boards:
bbb arm-multi_v7_defconfig : FAILED 1:06.42 omap5uevm arm-multi_v7_defconfig : FAILED 1:15.77 omap5uevm arm-multi_lpae_defconfig : FAILED 1:13.66 pandaes arm-multi_v7_defconfig : FAILED 2:13.70
This happened because ARCH_HISI wasn't selected, and the hisilicon platforms were the ones who used to bring in PINCTRL_SINGLE through a select.
Either we should remove the select from HISI, or we should add it to OMAP and others that need it. It's sort of silly to try to boot without pinctrl on these platforms, so selecting does make some sense...
Btw, I've made sure hisi is now selected, so the immediate need for this has been resolved. Still, the fragility remains.
Please let's not select drivers in Kconfig. That eventually leads into chasing of dependencies by adding more selects and randconfig build failures. Best to just remove the select for hisi and add it to the defconfigs instead.
For the pinctrl, it is possible to configure all the pins in the bootloader and not touch them at all in the kernel. Of course this will rule out some PM use cases that require dynamic pin configuration. But still no need to enforce it, the pinctrl just won't do anything if not selected.
Regards,
Tony
On Thu, Jul 31, 2014 at 5:30 AM, Tony Lindgren tony@atomide.com wrote:
- Olof Johansson olof@lixom.net [140731 10:25]:
On Thu, Jul 31, 2014 at 12:21 AM, Olof Johansson olof@lixom.net wrote:
On Wed, Jul 30, 2014 at 11:39 PM, Olof's autobooter build@lixom.net wrote:
Full logs are available at http://arm-soc.lixom.net/bootlogs/arm-soc/v3.16-rc6-1009-g709032a/
Failed boards:
bbb arm-multi_v7_defconfig : FAILED 1:06.42 omap5uevm arm-multi_v7_defconfig : FAILED 1:15.77 omap5uevm arm-multi_lpae_defconfig : FAILED 1:13.66 pandaes arm-multi_v7_defconfig : FAILED 2:13.70
This happened because ARCH_HISI wasn't selected, and the hisilicon platforms were the ones who used to bring in PINCTRL_SINGLE through a select.
Either we should remove the select from HISI, or we should add it to OMAP and others that need it. It's sort of silly to try to boot without pinctrl on these platforms, so selecting does make some sense...
Btw, I've made sure hisi is now selected, so the immediate need for this has been resolved. Still, the fragility remains.
Please let's not select drivers in Kconfig. That eventually leads into chasing of dependencies by adding more selects and randconfig build failures. Best to just remove the select for hisi and add it to the defconfigs instead.
For the pinctrl, it is possible to configure all the pins in the bootloader and not touch them at all in the kernel. Of course this will rule out some PM use cases that require dynamic pin configuration. But still no need to enforce it, the pinctrl just won't do anything if not selected.
Common practice on pretty much every other platform disagrees.
In reality, is there really ever a case where you're not going to want pinctrl enabled on OMAP?
It's possible to set it up in the bootloader mostly the right way, but it isn't done so today, and we do have a policy to not rely on the bootloader always getting everything right. Obviously FW doesn't get it right given the breakage seen when it accidentally got turned off.
-Olof
* Olof Johansson olof@lixom.net [140731 20:09]:
On Thu, Jul 31, 2014 at 5:30 AM, Tony Lindgren tony@atomide.com wrote:
- Olof Johansson olof@lixom.net [140731 10:25]:
On Thu, Jul 31, 2014 at 12:21 AM, Olof Johansson olof@lixom.net wrote:
On Wed, Jul 30, 2014 at 11:39 PM, Olof's autobooter build@lixom.net wrote:
Full logs are available at http://arm-soc.lixom.net/bootlogs/arm-soc/v3.16-rc6-1009-g709032a/
Failed boards:
bbb arm-multi_v7_defconfig : FAILED 1:06.42 omap5uevm arm-multi_v7_defconfig : FAILED 1:15.77 omap5uevm arm-multi_lpae_defconfig : FAILED 1:13.66 pandaes arm-multi_v7_defconfig : FAILED 2:13.70
This happened because ARCH_HISI wasn't selected, and the hisilicon platforms were the ones who used to bring in PINCTRL_SINGLE through a select.
Either we should remove the select from HISI, or we should add it to OMAP and others that need it. It's sort of silly to try to boot without pinctrl on these platforms, so selecting does make some sense...
Btw, I've made sure hisi is now selected, so the immediate need for this has been resolved. Still, the fragility remains.
Please let's not select drivers in Kconfig. That eventually leads into chasing of dependencies by adding more selects and randconfig build failures. Best to just remove the select for hisi and add it to the defconfigs instead.
For the pinctrl, it is possible to configure all the pins in the bootloader and not touch them at all in the kernel. Of course this will rule out some PM use cases that require dynamic pin configuration. But still no need to enforce it, the pinctrl just won't do anything if not selected.
Common practice on pretty much every other platform disagrees.
It's a bad solution though because of the reasons above. If that's done, then the Kconfig options for pinctrl should be just bool and not selectable. And not having things working as loadable modules will almost certainly lead into spaghetti code as we've seen many times before.
In reality, is there really ever a case where you're not going to want pinctrl enabled on OMAP?
Yes anything that needs a super fast boot-up time most likely wants to have pinctrl disabled to save some milliseconds of string parsing time. Devices like cameras etc.
It's possible to set it up in the bootloader mostly the right way, but it isn't done so today, and we do have a policy to not rely on the bootloader always getting everything right. Obviously FW doesn't get it right given the breakage seen when it accidentally got turned off.
At least all the Nokia devices relied on pinctrl done correctly in the bootloader by the hardware engineers. Of course some dynamic muxing was needed for PM, but that was mostly because of SoC specific hardware workarounds needed :)
Regards,
Tony
kernel-build-reports@lists.linaro.org