From mboxrd@z Thu Jan 1 00:00:00 1970 From: Krzysztof Kozlowski Subject: [next] Failing Odroid XU3 boot due to missing MMC device Date: Thu, 14 Apr 2016 10:23:28 +0200 Message-ID: <570F5380.7010103@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: Received: from mailout2.w1.samsung.com ([210.118.77.12]:65128 "EHLO mailout2.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750861AbcDNIXd (ORCPT ); Thu, 14 Apr 2016 04:23:33 -0400 Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Kukjin Kim , linux-arm-kernel , "linux-samsung-soc@vger.kernel.org" , linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org, Javier Martinez Canillas , Bartlomiej Zolnierkiewicz , Marek Szyprowski Hi, Anyone also observed recent failures of linux-next (20160413, 20160414) on booting from SD card? On my Odroid XU3 exynos and multi_v7 configs fail with: Apr 14 07:52:53 starting version 229 Apr 14 07:52:53 :: running hook [udev] Apr 14 07:52:53 :: Triggering uevents... Apr 14 07:52:54 Waiting 10 seconds for device /dev/mmcblk0p1 ... Apr 14 07:53:05 ERROR: device '/dev/mmcblk0p1' not found. Skipping fsck. Apr 14 07:53:05 ERROR: Unable to find root device '/dev/mmcblk0p1'. Apr 14 07:53:05 You are being dropped to a recovery shell Apr 14 07:53:05 Type 'exit' to try and continue booting Apr 14 07:53:05 sh: can't access tty; job control turned off I didn't start bisecting yet... maybe this is known? Full logs: http://www.krzk.eu/builders/boot-odroid-xu3-exynos/builds/673/steps/Boot%20odroid/logs/serial Best regards, Krzysztof