Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1378590 > unrolled thread

[next] Failing Odroid XU3 boot due to missing MMC device

Started byKrzysztof Kozlowski <k.kozlowski@samsung.com>
First post2016-04-14 10:30 +0200
Last post2016-04-14 11:10 +0200
Articles 7 — 4 participants

Back to article view | Back to linux.kernel

Contents

  [next] Failing Odroid XU3 boot due to missing MMC device Krzysztof Kozlowski <k.kozlowski@samsung.com> - 2016-04-14 10:30 +0200
    Re: [next] Failing Odroid XU3 boot due to missing MMC device Jaehoon Chung <jh80.chung@samsung.com> - 2016-04-14 10:30 +0200
      Re: [next] Failing Odroid XU3 boot due to missing MMC device Krzysztof Kozlowski <k.kozlowski@samsung.com> - 2016-04-14 11:10 +0200
    Re: [next] Failing Odroid XU3 boot due to missing MMC device Markus Reichl <m.reichl@fivetechno.de> - 2016-04-14 10:40 +0200
      Re: [next] Failing Odroid XU3 boot due to missing MMC device Russell King - ARM Linux <linux@arm.linux.org.uk> - 2016-04-14 10:50 +0200
        Re: [next] Failing Odroid XU3 boot due to missing MMC device Markus Reichl <m.reichl@fivetechno.de> - 2016-04-14 11:00 +0200
        Re: [next] Failing Odroid XU3 boot due to missing MMC device Krzysztof Kozlowski <k.kozlowski@samsung.com> - 2016-04-14 11:10 +0200

#1378590 — [next] Failing Odroid XU3 boot due to missing MMC device

FromKrzysztof Kozlowski <k.kozlowski@samsung.com>
Date2016-04-14 10:30 +0200
Subject[next] Failing Odroid XU3 boot due to missing MMC device
Message-ID<rnKP0-7eq-9@gated-at.bofh.it>
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

[toc] | [next] | [standalone]

#1378592

FromJaehoon Chung <jh80.chung@samsung.com>
Date2016-04-14 10:30 +0200
Message-ID<rnKP0-7eq-15@gated-at.bofh.it>
In reply to#1378590
Hi,

On 04/14/2016 05:23 PM, Krzysztof Kozlowski wrote:
> 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?

Refer to the below thread.

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

Best Regards,
Jaehoon Chung

> 
> 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@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
>

[toc] | [prev] | [next] | [standalone]

#1378629

FromKrzysztof Kozlowski <k.kozlowski@samsung.com>
Date2016-04-14 11:10 +0200
Message-ID<rnLrK-7Nv-43@gated-at.bofh.it>
In reply to#1378592
On 04/14/2016 10:28 AM, Jaehoon Chung wrote:
> Hi,
> 
> On 04/14/2016 05:23 PM, Krzysztof Kozlowski wrote:
>> 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?
> 
> Refer to the below thread.
> 
> https://patchwork.kernel.org/patch/8769361/

Thanks! That explains it.

BR,
Krzysztof

[toc] | [prev] | [next] | [standalone]

#1378597

FromMarkus Reichl <m.reichl@fivetechno.de>
Date2016-04-14 10:40 +0200
Message-ID<rnKYF-7jf-5@gated-at.bofh.it>
In reply to#1378590
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.     

Regards,
--
Markus Reichl

Am 14.04.2016 um 10:23 schrieb 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
> 
> 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@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

[toc] | [prev] | [next] | [standalone]

#1378607

FromRussell King - ARM Linux <linux@arm.linux.org.uk>
Date2016-04-14 10:50 +0200
Message-ID<rnL8m-7nM-17@gated-at.bofh.it>
In reply to#1378597
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.

[toc] | [prev] | [next] | [standalone]

#1378622

FromMarkus Reichl <m.reichl@fivetechno.de>
Date2016-04-14 11:00 +0200
Message-ID<rnLi4-7rI-33@gated-at.bofh.it>
In reply to#1378607
Am 14.04.2016 um 10:45 schrieb Russell King - ARM Linux:
> 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.

lsblk --output PARTUUID

>

[toc] | [prev] | [next] | [standalone]

#1378624

FromKrzysztof Kozlowski <k.kozlowski@samsung.com>
Date2016-04-14 11:10 +0200
Message-ID<rnLrH-7Nv-9@gated-at.bofh.it>
In reply to#1378607
On 04/14/2016 10:45 AM, Russell King - ARM Linux wrote:
> 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.

Markus, Russell,

Thanks, I'll switch to UUID.

Best regards,
Krzysztof

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web