From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Jaehoon Chung <jh80.chung@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
Date: Thu, 14 Apr 2016 11:05:03 +0200 [thread overview]
Message-ID: <570F5D3F.1060900@samsung.com> (raw)
In-Reply-To: <570F54B2.2070704@samsung.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [next] Failing Odroid XU3 boot due to missing MMC device
Date: Thu, 14 Apr 2016 11:05:03 +0200 [thread overview]
Message-ID: <570F5D3F.1060900@samsung.com> (raw)
In-Reply-To: <570F54B2.2070704@samsung.com>
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
next prev parent reply other threads:[~2016-04-14 9:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 8:23 [next] Failing Odroid XU3 boot due to missing MMC device Krzysztof Kozlowski
2016-04-14 8:23 ` Krzysztof Kozlowski
2016-04-14 8:28 ` Jaehoon Chung
2016-04-14 8:28 ` Jaehoon Chung
2016-04-14 9:05 ` Krzysztof Kozlowski [this message]
2016-04-14 9:05 ` Krzysztof Kozlowski
2016-04-14 8:31 ` Markus Reichl
2016-04-14 8:31 ` Markus Reichl
2016-04-14 8:45 ` Russell King - ARM Linux
2016-04-14 8:45 ` Russell King - ARM Linux
2016-04-14 8:54 ` Markus Reichl
2016-04-14 8:54 ` Markus Reichl
2016-04-14 9:07 ` Krzysztof Kozlowski
2016-04-14 9:07 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=570F5D3F.1060900@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=javier@osg.samsung.com \
--cc=jh80.chung@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.