Date: Thu, 14 Apr 2016 09:45:30 +0100
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Markus Reichl <m.reichl@fivetechno.de>
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
        Kukjin Kim <kgene@kernel.org>,
        linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
        "linux-samsung-soc@vger.kernel.org" 
	<linux-samsung-soc@vger.kernel.org>,
        linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
        Javier Martinez Canillas <javier@osg.samsung.com>,
        Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
        Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [next] Failing Odroid XU3 boot due to missing MMC device
Message-ID: <20160414084530.GS19428@n2100.arm.linux.org.uk>
References: <570F5380.7010103@samsung.com>
 <570F5550.5010708@fivetechno.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <570F5550.5010708@fivetechno.de>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 964
Lines: 28

On Thu, Apr 14, 2016 at 10:31:12AM +0200, Markus Reichl wrote:
> Hi Krzysztof,
> 
> yes, observed this with linux-next from yesterday 13.
> 
> I boot from eMMC.
> Device numbering of eMMC and SD are exchanged now.
> 
> I solved the boot problem by changing the rootdev in U-Boot env
> from /dev/mmcblk0p2 to /dev/mmcblk1p2.
> 
> Changed /etc/fdisk, too, to mount /dev/mmcblk1p1 to /boot.     

You really should mount by partition uuid - supplying something like:

	root=PARTUUID=f3ae567e-02

on the kernel command line.  This makes the mounting of rootfs
independent of which device carries the filesystem.

If you're not using an initramfs, the kernel prints the partuuid
values if it doesn't find the rootfs.  I don't know how to get the
partuuids without going through that process, sorry.

-- 
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.