Greg,
I've found two patches for stable so that we can do more thorough boot-testing of the v3.10 kernel. Please see below:
On Fri, Apr 04, 2014 at 10:55:03AM -0700, Kevin Hilman wrote:
On 04/04/2014 07:51 AM, Jason Cooper wrote:
On Fri, Apr 04, 2014 at 01:55:31AM -0700, Kevin's boot bot wrote:
Automated DT boot report for various ARM defconfigs.
Tree/Branch: queue Git describe: v3.10.36 Failed boot tests (console logs at the end) =========================================== armada-xp-openblocks-ax3-4: FAIL: multi_v7_defconfig armada-370-mirabox: FAIL: multi_v7_defconfig
...
multi_v7_defconfig
armada-xp-openblocks-ax3-4: FAIL: last 80 lines of boot log:
pps_core: LinuxPPS API ver. 1 registered pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti giometti@linux.it PTP clock support registered EDAC MC: Ver: 3.0.0 Switching to clocksource armada_370_xp_clocksource bounce pool size: 64 pages Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) armada-xp-pinctrl d0018000.pinctrl: registered pinctrl driver ipmi message handler version 39.2 IPMI System Interface driver. ipmi_si: Adding default-specified kcs state machine ipmi_si: Trying default-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0 ipmi_si: Could not set up I/O space Trying to free nonexistent resource <0000000000000ca2-0000000000000ca2> Trying to free nonexistent resource <0000000000000ca3-0000000000000ca3> ipmi_si: Adding default-specified smic state machine ipmi_si: Trying default-specified smic state machine at i/o address 0xca9, slave address 0x0, irq 0 ipmi_si: Could not set up I/O space Trying to free nonexistent resource <0000000000000ca9-0000000000000ca9> Trying to free nonexistent resource <0000000000000caa-0000000000000caa> Trying to free nonexistent resource <0000000000000cab-0000000000000cab> ipmi_si: Adding default-specified bt state machine ipmi_si: Trying default-specified bt state machine at i/o address 0xe4, slave address 0x0, irq 0 ipmi_si: Could not set up I/O space Trying to free nonexistent resource <00000000000000e4-00000000000000e4> Trying to free nonexistent resource <00000000000000e5-00000000000000e5> Trying to free nonexistent resource <00000000000000e6-00000000000000e6> ipmi_si: Unable to find any System Interface(s) Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled d0012000.serial: ttyS0 at MMIO 0xd0012000 (irq = 17) is a 16550A console [ttyS0] enabled d0012100.serial: ttyS1 at MMIO 0xd0012100 (irq = 18) is a 16550A sata_mv d00a0000.sata: slots 32 ports 2 scsi0 : sata_mv scsi1 : sata_mv ata1: SATA max UDMA/133 irq 24 ata2: SATA max UDMA/133 irq 24 usbcore: registered new interface driver usb-storage mousedev: PS/2 mouse device common for all mice sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman sdhci-pltfm: SDHCI platform and OF driver helper usbcore: registered new interface driver usbhid usbhid: USB HID core driver VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6 Registering SWP/SWPB emulation handler /home/build/work/batch/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) ata1: SATA link down (SStatus 0 SControl F300) ata2: SATA link down (SStatus 0 SControl F300) List of all partitions: No filesystem could mount root, tried:
What rootfs are you using?
I'm using a ramdisk, but in v3.10, multi_v7_defconfig doesn't have the right kconfig for u-boot to pass a ramdisk. I've had these boards black-listed from v3.10, but my blacklist got mixed up so it didn't get run.
FWIW, if you wan't to send patch to v3.10 stable for this, I beleive this is what's needed in the defconfig to boot a ramdisk:
CONFIG_ARM_ATAG_DTB_COMPAT=y
c12d82b843537 "arm: multi_v7_defconfig: Enable initrd/initramfs support"
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y
This isn't in mainline multi_v7_defconfig.
CONFIG_BLK_DEV_INITRD=y
a0396b9bd5a4a "ARM: multi_v7_defconfig: enable ARM_ATAG_DTB_COMPAT"
Kevin, if you could try the above two patches without CMDLINE_..., we should be able to resume testing v3.10 once they land in stable.
thx,
Jason.