Failing Odroid XU3 boot due to missing MMC device

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
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Hi,

Quoted 16 lines · Krzysztof Kozlowski

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

Quoted 1 line

I didn't start bisecting yet... maybe this is known?

Refer to the below thread.

https://patchwork.kernel.org/patch/8769361/

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
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

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.

Quoted 11 lines

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.

Quoted 11 lines · Markus Reichl

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.