Failed boards:
panda multi_v7_defconfig : FAILED 1:35.52
Successful boards:
apc vt8500_v6_v7_defconfig : passed 1:20.97 arndale exynos_defconfig : passed 1:07.94 bbb omap2plus_defconfig : passed 1:37.10 bbb multi_v7_defconfig : passed 1:20.91 beaver tegra_defconfig : passed 0:58.53 beaver multi_v7_defconfig : passed 0:54.51 capri bcm_defconfig : passed 0:45.31 capri multi_v7_defconfig : passed 0:44.11 cubie sunxi_defconfig : passed 0:50.66 cubie multi_v7_defconfig : passed 0:51.32 cubie2 sunxi_defconfig : passed 0:49.86 cubie2 multi_v7_defconfig : passed 0:58.34 cubie2 multi_lpae_defconfig : passed 0:49.68 cubox dove_defconfig : passed 1:07.38 dalmore tegra_defconfig : passed 1:19.16 dalmore multi_v7_defconfig : passed 1:18.95 dalmore multi_lpae_defconfig : passed 1:18.22 hummingboard imx_v6_v7_defconfig : warnings 1:19.49 hummingboard multi_v7_defconfig : passed 0:59.19 panda omap2plus_defconfig : passed 1:14.72 sama5 sama5_defconfig : passed 1:52.11 seaboard tegra_defconfig : passed 1:04.97 seaboard multi_v7_defconfig : passed 1:06.73 snow exynos_defconfig : passed 1:23.19 snowball u8500_defconfig : passed 1:27.56 snowball multi_v7_defconfig : passed 2:06.30 trimslice tegra_defconfig : passed 0:55.41 trimslice multi_v7_defconfig : passed 1:06.36 wandboard imx_v6_v7_defconfig : warnings 0:57.57 wandboard multi_v7_defconfig : passed 1:01.92
Board legend is available at http://arm-soc.lixom.net/boards.html
Last entries of failed logs below:
========================================================================
Board panda-multi_v7_defconfig failure log: -------------------------------------------------
[ 1.441864] usbcore: registered new interface driver usb-storage [ 1.449615] mousedev: PS/2 mouse device common for all mice [ 1.457244] i2c /dev entries driver [ 1.462341] sdhci: Secure Digital Host Controller Interface driver [ 1.468841] sdhci: Copyright(c) Pierre Ossman [ 1.474060] omap_hsmmc 4809c000.mmc: vmmc regulator missing [ 1.479949] platform 4809c000.mmc: Driver omap_hsmmc requests probe deferral [ 1.487609] omap_hsmmc 480d5000.mmc: vmmc regulator missing [ 1.493530] platform 480d5000.mmc: Driver omap_hsmmc requests probe deferral [ 1.501190] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.508422] usbcore: registered new interface driver usbhid [ 1.514282] usbhid: USB HID core driver [ 1.521606] TCP: cubic registered [ 1.525115] NET: Registered protocol family 17 [ 1.529968] Key type dns_resolver registered [ 1.534912] Power Management for TI OMAP4+ devices. [ 1.540039] Power Management for TI OMAP4. [ 1.544372] OMAP4 PM: u-boot >= v2012.07 is required for full PM support [ 1.551757] Registering SWP/SWPB emulation handler [ 1.557830] vwl1271: 1800 mV [ 1.562652] Skipping twl internal clock init and using bootloader value (unknown osc rate) [ 1.571807] twl 0-0048: PIH (irq 39) nested IRQs [ 1.577392] twl_rtc rtc.11: Power up reset detected. [ 1.583282] twl_rtc rtc.11: Enabling TWL-RTC [ 1.589965] twl_rtc rtc.11: rtc core: registered rtc.11 as rtc0 [ 1.596923] VAUX1_6030: 1000 <--> 3000 mV at 2800 mV [ 1.602935] VAUX2_6030: 1200 <--> 2800 mV at 1800 mV [ 1.608917] VAUX3_6030: 1000 <--> 3000 mV at 1200 mV [ 1.614898] VMMC: 1200 <--> 3000 mV at 3000 mV [ 1.620330] VPP: 1800 <--> 2500 mV at 1900 mV [ 1.625671] VUSIM: 1200 <--> 2900 mV at 1800 mV [ 1.630676] VDAC: 1800 mV [ 1.634246] VANA: 2100 mV [ 1.637756] VCXIO: 1800 mV [ 1.637756] VUSB: 3300 mV [ 1.644531] V1V8: 1800 mV [ 1.648040] V2V1: 2100 mV [ 1.653533] omap_i2c 48070000.i2c: bus 0 rev0.11 at 400 kHz ~$off # PYBOOT: Exception: timeout
Hi Olof,
On Tue, Jan 28, 2014 at 2:17 AM, Olof's autobooter build@lixom.net wrote:
hummingboard imx_v6_v7_defconfig : warnings 1:19.49
Are these warnings available for us to look at?
Regards,
Fabio Estevam
On Tue, Jan 28, 2014 at 1:24 PM, Fabio Estevam festevam@gmail.com wrote:
Hi Olof,
On Tue, Jan 28, 2014 at 2:17 AM, Olof's autobooter build@lixom.net wrote:
hummingboard imx_v6_v7_defconfig : warnings 1:19.49
Are these warnings available for us to look at?
I haven't automated upload/reporting of them, but I'm happy to supply on request. In this case it was during early boot. All KERN_WARN-level output form a boot of that kernel is:
[WARN] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 [WARN] Memory: 505016K/524288K available (6291K kernel code, 386K rwdata, 2064K rodata, 312K init, 5506K bss, 19272K reserved, 0K highmem) [WARN] ------------[ cut here ]------------ [WARN] WARNING: CPU: 0 PID: 0 at /home/build/work/batch/mm/slub.c:1511 __kmem_cache_create+0x24c/0x340() [WARN] Modules linked in: [WARN] CPU: 0 PID: 0 Comm: swapper Not tainted 3.13.0-next-20140128 #1 [WARN] Backtrace: [WARN] [<8001217c>] (dump_backtrace) from [<80012460>] (show_stack+0x18/0x1c) [WARN] r6:800dc208 r5:00000000 r4:808a4cd0 r3:00000000 [WARN] [<80012448>] (show_stack) from [<806224d0>] (dump_stack+0x84/0x9c) [WARN] [<8062244c>] (dump_stack) from [<80027bbc>] (warn_slowpath_common+0x70/0x94) [WARN] r5:00000009 r4:00000000 [WARN] [<80027b4c>] (warn_slowpath_common) from [<80027c84>] (warn_slowpath_null+0x24/0x2c) [WARN] r8:80e13a18 r7:00002000 r6:80872454 r5:9ffe1000 r4:9f400000 [WARN] [<80027c60>] (warn_slowpath_null) from [<800dc208>] (__kmem_cache_create+0x24c/0x340) [WARN] [<800dbfbc>] (__kmem_cache_create) from [<80851e94>] (create_boot_cache+0x50/0x78) [WARN] r10:00000000 r9:9fffcbc0 r8:80888880 r7:808724c8 r6:80784fcc r5:80872454 [WARN] r4:0000002c [WARN] [<80851e44>] (create_boot_cache) from [<808536ec>] (kmem_cache_init+0x3c/0xe0) [WARN] r6:80e13a14 r5:80872454 r4:80e190a4 r3:00002000 [WARN] [<808536b0>] (kmem_cache_init) from [<808319c8>] (start_kernel+0x198/0x388) [WARN] r8:80888880 r7:8086fc80 r6:ffffffff r5:808e0840 r4:00000001 [WARN] [<80831830>] (start_kernel) from [<10008074>] (0x10008074) [WARN] r9:412fc09a r8:10004059 r7:8088d52c r6:8086fc7c r5:80888928 r4:10c53c7d [WARN] ---[ end trace 3406ff24bd97382e ]--- [WARN] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar [WARN] ... MAX_LOCKDEP_SUBCLASSES: 8 [WARN] ... MAX_LOCK_DEPTH: 48 [WARN] ... MAX_LOCKDEP_KEYS: 8191 [WARN] ... CLASSHASH_SIZE: 4096 [WARN] ... MAX_LOCKDEP_ENTRIES: 16384 [WARN] ... MAX_LOCKDEP_CHAINS: 32768 [WARN] ... CHAINHASH_SIZE: 16384 [WARN] memory used by lock dependency info: 3695 kB [WARN] per task-struct memory footprint: 1152 bytes [WARN] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [WARN] imx-sdma 20ec000.sdma: Direct firmware load failed with error -2 [WARN] imx-sdma 20ec000.sdma: Falling back to user helper [WARN] 2188000.ethernet supply phy not found, using dummy regulator [WARN] sdhci-esdhc-imx 2194000.usdhc: could not get ultra high speed state, work on normal mode [WARN] mmc0: host does not support reading read-only switch. assuming write-enable. [WARN] isa bounce pool size: 16 pages
On Tue, Jan 28, 2014 at 7:29 PM, Olof Johansson olof@lixom.net wrote:
[WARN] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 [WARN] Memory: 505016K/524288K available (6291K kernel code, 386K rwdata, 2064K rodata, 312K init, 5506K bss, 19272K reserved, 0K highmem) [WARN] ------------[ cut here ]------------ [WARN] WARNING: CPU: 0 PID: 0 at /home/build/work/batch/mm/slub.c:1511 __kmem_cache_create+0x24c/0x340()
Ok, thanks.
It seems we have a fix for this one, but it has not been applied yet: https://lkml.org/lkml/2014/1/24/194
Regards,
Fabio Estevam
On Tue, Jan 28, 2014 at 07:24:02PM -0200, Fabio Estevam wrote:
Hi Olof,
On Tue, Jan 28, 2014 at 2:17 AM, Olof's autobooter build@lixom.net wrote:
hummingboard imx_v6_v7_defconfig : warnings 1:19.49
Are these warnings available for us to look at?
I've given up with talking to Olof about Hummingboard stuff - Olof's been totally unresponsive for a week now to patches to try etc...
On Tue, Jan 28, 2014 at 1:30 PM, Russell King - ARM Linux linux@arm.linux.org.uk wrote:
On Tue, Jan 28, 2014 at 07:24:02PM -0200, Fabio Estevam wrote:
Hi Olof,
On Tue, Jan 28, 2014 at 2:17 AM, Olof's autobooter build@lixom.net wrote:
hummingboard imx_v6_v7_defconfig : warnings 1:19.49
Are these warnings available for us to look at?
I've given up with talking to Olof about Hummingboard stuff - Olof's been totally unresponsive for a week now to patches to try etc...
A week? What did I miss a week ago?
By the time I had a chance to try the patch for MMC from Friday (I.e. on Monday morning), it had already been through a pass of building your tree and booting successfully, so it didn't seem needed.
-Olof
On Tue, Jan 28, 2014 at 01:36:54PM -0800, Olof Johansson wrote:
On Tue, Jan 28, 2014 at 1:30 PM, Russell King - ARM Linux linux@arm.linux.org.uk wrote:
On Tue, Jan 28, 2014 at 07:24:02PM -0200, Fabio Estevam wrote:
Hi Olof,
On Tue, Jan 28, 2014 at 2:17 AM, Olof's autobooter build@lixom.net wrote:
hummingboard imx_v6_v7_defconfig : warnings 1:19.49
Are these warnings available for us to look at?
I've given up with talking to Olof about Hummingboard stuff - Olof's been totally unresponsive for a week now to patches to try etc...
A week? What did I miss a week ago?
By the time I had a chance to try the patch for MMC from Friday (I.e. on Monday morning), it had already been through a pass of building your tree and booting successfully, so it didn't seem needed.
I'm still interested to know: (a) whether you're using a UHS card, and (b) whether the change to use gpio card detection resolved the errors you were seeing.
since it's an important datapoint for the future when I add support for UHS. And yes, time ticks by slowly when waiting for responses. :p
On Tue, Jan 28, 2014 at 4:56 PM, Russell King - ARM Linux linux@arm.linux.org.uk wrote:
On Tue, Jan 28, 2014 at 01:36:54PM -0800, Olof Johansson wrote:
On Tue, Jan 28, 2014 at 1:30 PM, Russell King - ARM Linux linux@arm.linux.org.uk wrote:
On Tue, Jan 28, 2014 at 07:24:02PM -0200, Fabio Estevam wrote:
Hi Olof,
On Tue, Jan 28, 2014 at 2:17 AM, Olof's autobooter build@lixom.net wrote:
hummingboard imx_v6_v7_defconfig : warnings 1:19.49
Are these warnings available for us to look at?
I've given up with talking to Olof about Hummingboard stuff - Olof's been totally unresponsive for a week now to patches to try etc...
A week? What did I miss a week ago?
By the time I had a chance to try the patch for MMC from Friday (I.e. on Monday morning), it had already been through a pass of building your tree and booting successfully, so it didn't seem needed.
I'm still interested to know: (a) whether you're using a UHS card, and (b) whether the change to use gpio card detection resolved the errors you were seeing.
since it's an important datapoint for the future when I add support for UHS. And yes, time ticks by slowly when waiting for responses. :p
Ok, I'll take a look when I get home tonight. The problem was resolved so (b) is affirmative.
-Olof
On Tue, Jan 28, 2014 at 5:04 PM, Olof Johansson olof@lixom.net wrote:
On Tue, Jan 28, 2014 at 4:56 PM, Russell King - ARM Linux linux@arm.linux.org.uk wrote:
On Tue, Jan 28, 2014 at 01:36:54PM -0800, Olof Johansson wrote:
On Tue, Jan 28, 2014 at 1:30 PM, Russell King - ARM Linux linux@arm.linux.org.uk wrote:
On Tue, Jan 28, 2014 at 07:24:02PM -0200, Fabio Estevam wrote:
Hi Olof,
On Tue, Jan 28, 2014 at 2:17 AM, Olof's autobooter build@lixom.net wrote:
hummingboard imx_v6_v7_defconfig : warnings 1:19.49
Are these warnings available for us to look at?
I've given up with talking to Olof about Hummingboard stuff - Olof's been totally unresponsive for a week now to patches to try etc...
A week? What did I miss a week ago?
By the time I had a chance to try the patch for MMC from Friday (I.e. on Monday morning), it had already been through a pass of building your tree and booting successfully, so it didn't seem needed.
I'm still interested to know: (a) whether you're using a UHS card, and (b) whether the change to use gpio card detection resolved the errors you were seeing.
since it's an important datapoint for the future when I add support for UHS. And yes, time ticks by slowly when waiting for responses. :p
Ok, I'll take a look when I get home tonight. The problem was resolved so (b) is affirmative.
The board has a Samsung 8GB SD card, Class 10 (MB-MP8GA/US). So, not UHS.
-Olog
kernel-build-reports@lists.linaro.org