Thomas Petazzoni thomas.petazzoni@free-electrons.com writes:
Dear Jason Cooper,
On Wed, 7 May 2014 08:11:30 -0400, Jason Cooper wrote:
iirc, these boot into an initrd. If so, are the errors below an artifact of the boot farm?
Gregory, Thomas, Ezequiel,
If these are legitimate errors, can you please take a look and tell me if anything needs backported?
Weird. I don't think anything has changed in terms of initrd handling recently, at least nothing specific to mvebu platforms. I remember discussing some U-Boot configuration tips at ELC with Kevin. Maybe he has changed his boot scripts/configurations a bit and it breaks on these platforms now? I'd like to hear from Kevin about this.
These are long standing boot failures that I had blacklisted from boot testing on stable, but in shuffling some things around, my blacklist got removed.
The problem here on the mvebu platforms is that the multi_v7_defconfig in v3.10.y is missing some kconfig options for using a bootloader-loaded initramfs. Specifically:
CONFIG_BLK_DEV_INITRD=y CONFIG_ARM_ATAG_DTB_COMPAT=y
Also for the buildroot initramfs I use, I need:
CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y
These have been in multi_v7_defconfig s since v3.12 I think, but missing from v3.10, which was the early days of multi_v7_defconfig anyways.
Someone needs to submit a patch to stable for this to get this working, or maybe I should just stop booting multi_v7_defconfig on v3.10.
Kevin