* [next] Failing Odroid XU3 boot due to missing MMC device @ 2016-04-14 8:23 ` Krzysztof Kozlowski 0 siblings, 0 replies; 14+ messages in thread From: Krzysztof Kozlowski @ 2016-04-14 8:23 UTC (permalink / raw) To: Kukjin Kim, linux-arm-kernel, linux-samsung-soc@vger.kernel.org, linux-kernel, linux-mmc, 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 ^ permalink raw reply [flat|nested] 14+ messages in thread
* [next] Failing Odroid XU3 boot due to missing MMC device @ 2016-04-14 8:23 ` Krzysztof Kozlowski 0 siblings, 0 replies; 14+ messages in thread From: Krzysztof Kozlowski @ 2016-04-14 8:23 UTC (permalink / raw) To: linux-arm-kernel 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 ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [next] Failing Odroid XU3 boot due to missing MMC device 2016-04-14 8:23 ` Krzysztof Kozlowski @ 2016-04-14 8:28 ` Jaehoon Chung -1 siblings, 0 replies; 14+ messages in thread From: Jaehoon Chung @ 2016-04-14 8:28 UTC (permalink / raw) To: Krzysztof Kozlowski, Kukjin Kim, linux-arm-kernel, linux-samsung-soc@vger.kernel.org, linux-kernel, linux-mmc, Javier Martinez Canillas, Bartlomiej Zolnierkiewicz, Marek Szyprowski 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 > > ^ permalink raw reply [flat|nested] 14+ messages in thread
* [next] Failing Odroid XU3 boot due to missing MMC device @ 2016-04-14 8:28 ` Jaehoon Chung 0 siblings, 0 replies; 14+ messages in thread From: Jaehoon Chung @ 2016-04-14 8:28 UTC (permalink / raw) To: linux-arm-kernel 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 at vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > > ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [next] Failing Odroid XU3 boot due to missing MMC device 2016-04-14 8:28 ` Jaehoon Chung @ 2016-04-14 9:05 ` Krzysztof Kozlowski -1 siblings, 0 replies; 14+ messages in thread From: Krzysztof Kozlowski @ 2016-04-14 9:05 UTC (permalink / raw) To: Jaehoon Chung, Kukjin Kim, linux-arm-kernel, linux-samsung-soc@vger.kernel.org, linux-kernel, linux-mmc, Javier Martinez Canillas, Bartlomiej Zolnierkiewicz, Marek Szyprowski 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 ^ permalink raw reply [flat|nested] 14+ messages in thread
* [next] Failing Odroid XU3 boot due to missing MMC device @ 2016-04-14 9:05 ` Krzysztof Kozlowski 0 siblings, 0 replies; 14+ messages in thread From: Krzysztof Kozlowski @ 2016-04-14 9:05 UTC (permalink / raw) To: linux-arm-kernel 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 ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [next] Failing Odroid XU3 boot due to missing MMC device 2016-04-14 8:23 ` Krzysztof Kozlowski @ 2016-04-14 8:31 ` Markus Reichl -1 siblings, 0 replies; 14+ messages in thread From: Markus Reichl @ 2016-04-14 8:31 UTC (permalink / raw) To: Krzysztof Kozlowski, Kukjin Kim, linux-arm-kernel, linux-samsung-soc@vger.kernel.org, linux-kernel, linux-mmc, Javier Martinez Canillas, Bartlomiej Zolnierkiewicz, Marek Szyprowski 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 > ^ permalink raw reply [flat|nested] 14+ messages in thread
* [next] Failing Odroid XU3 boot due to missing MMC device @ 2016-04-14 8:31 ` Markus Reichl 0 siblings, 0 replies; 14+ messages in thread From: Markus Reichl @ 2016-04-14 8:31 UTC (permalink / raw) To: linux-arm-kernel 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 at vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [next] Failing Odroid XU3 boot due to missing MMC device 2016-04-14 8:31 ` Markus Reichl @ 2016-04-14 8:45 ` Russell King - ARM Linux -1 siblings, 0 replies; 14+ messages in thread From: Russell King - ARM Linux @ 2016-04-14 8:45 UTC (permalink / raw) To: Markus Reichl Cc: Krzysztof Kozlowski, Kukjin Kim, linux-arm-kernel, linux-samsung-soc@vger.kernel.org, linux-kernel, linux-mmc, Javier Martinez Canillas, Bartlomiej Zolnierkiewicz, Marek Szyprowski 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. ^ permalink raw reply [flat|nested] 14+ messages in thread
* [next] Failing Odroid XU3 boot due to missing MMC device @ 2016-04-14 8:45 ` Russell King - ARM Linux 0 siblings, 0 replies; 14+ messages in thread From: Russell King - ARM Linux @ 2016-04-14 8:45 UTC (permalink / raw) To: linux-arm-kernel 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. ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [next] Failing Odroid XU3 boot due to missing MMC device 2016-04-14 8:45 ` Russell King - ARM Linux @ 2016-04-14 8:54 ` Markus Reichl -1 siblings, 0 replies; 14+ messages in thread From: Markus Reichl @ 2016-04-14 8:54 UTC (permalink / raw) To: Russell King - ARM Linux Cc: Krzysztof Kozlowski, Kukjin Kim, linux-arm-kernel, linux-samsung-soc@vger.kernel.org, linux-kernel, linux-mmc, Javier Martinez Canillas, Bartlomiej Zolnierkiewicz, Marek Szyprowski 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 > ^ permalink raw reply [flat|nested] 14+ messages in thread
* [next] Failing Odroid XU3 boot due to missing MMC device @ 2016-04-14 8:54 ` Markus Reichl 0 siblings, 0 replies; 14+ messages in thread From: Markus Reichl @ 2016-04-14 8:54 UTC (permalink / raw) To: linux-arm-kernel 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 > ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [next] Failing Odroid XU3 boot due to missing MMC device 2016-04-14 8:45 ` Russell King - ARM Linux @ 2016-04-14 9:07 ` Krzysztof Kozlowski -1 siblings, 0 replies; 14+ messages in thread From: Krzysztof Kozlowski @ 2016-04-14 9:07 UTC (permalink / raw) To: Russell King - ARM Linux, Markus Reichl Cc: Kukjin Kim, linux-arm-kernel, linux-samsung-soc@vger.kernel.org, linux-kernel, linux-mmc, Javier Martinez Canillas, Bartlomiej Zolnierkiewicz, Marek Szyprowski 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 ^ permalink raw reply [flat|nested] 14+ messages in thread
* [next] Failing Odroid XU3 boot due to missing MMC device @ 2016-04-14 9:07 ` Krzysztof Kozlowski 0 siblings, 0 replies; 14+ messages in thread From: Krzysztof Kozlowski @ 2016-04-14 9:07 UTC (permalink / raw) To: linux-arm-kernel 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 ^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2016-04-14 9:07 UTC | newest] Thread overview: 14+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 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
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.