On Thursday 23 February 2017 07:02 PM, Adam Ford wrote: > I narrowed down the patch to this merge. > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e79ab194d15e1baa25540cb9efaf2a459cf4bc32 > > > Using the same boot parameters, I can boot the 4.9.y branch, so I > don't think it's my SD card or my boot parameters. Hmm, I just tried booting my DA850 EVM with root filesystem on SD card, and it booted fine. http://pastebin.ubuntu.com/24077092/ > I need to go checkout this branch and bisect it to identify what > causes a failure to boot over SD card. If anyone has already started > this, can you let me know, I don't want to double efforts. > > Here is the log: > > [stuff deleted] Are you using DT boot or non-DT ? Also, what is the config you are using to build the kernel - davinci_all_defconfig? > VDCDC1: incomplete constraints, leaving on > mmc0: new high speed SDHC card at address b368 > mmcblk0: mmc0:b368 00000 3.75 GiB (ro) > mmcblk0: p1 p2 > VDCDC3: incomplete constraints, leaving on > LDO1: incomplete constraints, leaving on > LDO2: incomplete constraints, leaving on > VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2): error -30 -30 is "Read only filesystem". Could it be that you have "rw" in you bootargs and have the read-only switch of SD card set to locked? Thanks, Sekhar PS: DA850/OMAP-L138 EVM is not supported on linux-omap mailing list. linux-omap community hacks on boards supported through arch/arm /mach-omap2 and arch/arm/mach-omap1. I know "OMAP" in the part number creates this confusion. For bug reports on DA850 EVM, please copy the folks and lists listed in MAINTAINERS entry: TI DAVINCI MACHINE SUPPORT M: Sekhar Nori <nsekhar@xxxxxx> M: Kevin Hilman <khilman@xxxxxxxxxx> L: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx (moderated for non-subscribers) T: git git://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci.git S: Supported F: arch/arm/mach-davinci/ F: drivers/i2c/busses/i2c-davinci.c -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html