Not booting on BeagleBoard xM 0x2

DISCUSSION Tomas Frydrych 8 participants 14 messages Apr 4, 2012 – Jun 13, 2012

Subsystems (2)

MMC, SD and SDIO OMAP hs MMC support

lore

Share & tools

lore

Tomas Frydrych

author

2012-04-04 10:14 UTC #0 lore raw

Hi,

I am trying to get Yocto image built from yesterday's master (Linux-3.0.23-yocto-standard) to boot on the NAND-less version of BeagleBoard xM, but the kernel panics with:

----------------- console log start ------------

Waiting for root device /dev/mmcblk0p2...
mmc0: new SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.67 GiB (ro)
mmcblk0: p1 p2

VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2) Please append a correct "root=" boot option; here are the available partitions:

b300 3858432 mmcblk0 driver: mmcblk
b301 120456 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1
b302 3445942 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2

VFS: Unable to mount root fs on unknown-block(179,2) User configuration error - no valid root filesystem found

Kernel panic - not syncing: Invalid configuration from end user prevents

continuing

-------------- console log end ------------------------------------

My guess would be the problem is the card being detected as 'ro' (line 3), but I do not know why that is (there is no lock switch on mmc cards).

The card itself is fine, it's the original card that came with the board, the original Angstrom demo boots fine from it, and yocto kernel 2.6.37 also used to boot.

Tomas

Andrea Galbusera

2012-04-04 12:04 UTC #1 lore raw

Hi Tomas,

Quoted 28 lines · Tomas Frydrych

Hi,
I am trying to get Yocto image built from yesterday's master (Linux-3.0.23-yocto-standard) to boot on the NAND-less version of BeagleBoard xM, but the kernel panics with:
----------------- console log start ------------
Waiting for root device /dev/mmcblk0p2...
mmc0: new SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.67 GiB (ro)
mmcblk0: p1 p2
VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2) Please append a correct "root=" boot option; here are the available partitions:
b300 3858432 mmcblk0 driver: mmcblk
b301 120456 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1 b302 3445942 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2
VFS: Unable to mount root fs on unknown-block(179,2) User configuration error - no valid root filesystem found
Kernel panic - not syncing: Invalid configuration from end user prevents
continuing
-------------- console log end ------------------------------------

Quoted 8 lines

My guess would be the problem is the card being detected as 'ro' (line 3), but I do not know why that is (there is no lock switch on mmc cards).
The card itself is fine, it's the original card that came with the board, the original Angstrom demo boots fine from it, and yocto kernel 2.6.37 also used to boot.
Tomas

Looks related to the comment I wrote here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892
I have a slightly different failure with yocto 1.2 beta snapshot (same kernel) but seems related. Needs more investigation.
Anyone else having problem booting on beagleboard xM? Seems something wrong happened after 1.1 release...

Andrea

Bruce Ashfield

2012-04-04 12:50 UTC #2 lore raw

Quoted 39 lines · Andrea Galbusera

Hi Tomas,
Quoted 35 lines · Tomas Frydrych
Hi,
I am trying to get Yocto image built from yesterday's master (Linux-3.0.23-yocto-standard) to boot on the NAND-less version of BeagleBoard xM, but the kernel panics with:
----------------- console log start ------------
Waiting for root device /dev/mmcblk0p2...
mmc0: new SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.67 GiB (ro)
mmcblk0: p1 p2
VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2) Please append a correct "root=" boot option; here are the available partitions:
b300 3858432 mmcblk0 driver: mmcblk
b301 120456 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1
b302 3445942 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2
VFS: Unable to mount root fs on unknown-block(179,2) User configuration error - no valid root filesystem found
Kernel panic - not syncing: Invalid configuration from end user prevents
continuing
-------------- console log end ------------------------------------
My guess would be the problem is the card being detected as 'ro' (line 3), but I do not know why that is (there is no lock switch on mmc cards).
The card itself is fine, it's the original card that came with the board, the original Angstrom demo boots fine from it, and yocto kernel 2.6.37 also used to boot.

Quoted 8 lines

Quoted 1 line
Tomas
Looks related to the comment I wrote here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892
I have a slightly different failure with yocto 1.2 beta snapshot (same kernel) but seems related. Needs more investigation.
Anyone else having problem booting on beagleboard xM? Seems something wrong happened after 1.1 release...

We are working on several bugs on our reference beagleboard. The problem is that my beagleboard died (a horrible painful death) and the other boards that are directly available to are RevC and they are booting. So things are slowed down a bit .. but we are trying to get to the bottom of it, as fast as possible.

Cheers,

Bruce

Quoted 6 lines

Andrea
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Gary Thomas

2012-04-04 14:10 UTC #3 lore raw

Quoted 49 lines · Bruce Ashfield

Quoted 39 lines · Andrea Galbusera
Hi Tomas,
Quoted 35 lines · Tomas Frydrych
Hi,
I am trying to get Yocto image built from yesterday's master (Linux-3.0.23-yocto-standard) to boot on the NAND-less version of BeagleBoard xM, but the kernel panics with:
----------------- console log start ------------
Waiting for root device /dev/mmcblk0p2...
mmc0: new SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.67 GiB (ro)
mmcblk0: p1 p2
VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2) Please append a correct "root=" boot option; here are the available partitions:
b300 3858432 mmcblk0 driver: mmcblk
b301 120456 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1 b302 3445942 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2
VFS: Unable to mount root fs on unknown-block(179,2) User configuration error - no valid root filesystem found
Kernel panic - not syncing: Invalid configuration from end user prevents
continuing
-------------- console log end ------------------------------------
My guess would be the problem is the card being detected as 'ro' (line 3), but I do not know why that is (there is no lock switch on mmc cards).
The card itself is fine, it's the original card that came with the board, the original Angstrom demo boots fine from it, and yocto kernel 2.6.37 also used to boot.
Quoted 8 lines
Quoted 1 line
Tomas
Looks related to the comment I wrote here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892
I have a slightly different failure with yocto 1.2 beta snapshot (same kernel) but seems related. Needs more investigation.
Anyone else having problem booting on beagleboard xM? Seems something wrong happened after 1.1 release...

Quoted 5 lines

We are working on several bugs on our reference beagleboard. The problem is that my beagleboard died (a horrible painful death) and the other boards that are directly available to are RevC and they are booting. So things are slowed down a bit .. but we are trying to get to the bottom of it, as fast as possible.

Just FYI, it also doesn't boot on my rev-C3 (not xM), albeit with a different error pattern. It hangs at this point:
Waiting for root device /dev/mmcblk0p2...
mmc0: error -110 whilst initialising SD card

Looks like you might need the attached patch?

Signature · 4 lines

------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

From 47be8c9046c22715ce646091dd9e98fa87fc86e1 Mon Sep 17 00:00:00 2001
From: Steve Sakoman <[email protected]>
Date: Mon, 18 Jul 2011 23:13:41 -0500
Subject: [PATCH 07/10] omap_hsmmc: Set dto to max value of 14 to avoid SD Card timeouts

This fixes MMC errors due to timeouts on certain SD Cards following suggestions to set dto to 14 by Jason Kridner and Steven Kipisz

Details of the issue:
http://talk.maemo.org/showthread.php?p=1000707#post1000707

This fix was originally proposed by Sukumar Ghoral of TI.

---
 drivers/mmc/host/omap_hsmmc.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

drivers/mmc/host/omap_hsmmc.c +3 -0

index dedf3da..a8a60d4 100644
@@ -1441,6 +1441,9 @@ static void set_data_timeout(struct omap_hsmmc_host *host,
 			dto = 14;
 	}
 
+	/* Set dto to max value of 14 to avoid SD Card timeouts */
+	dto = 14;
+
 	reg &= ~DTO_MASK;
 	reg |= dto << DTO_SHIFT;
 	OMAP_HSMMC_WRITE(host->base, SYSCTL, reg);

Signature · 1 line

1.7.2.5

Andrea Galbusera

2012-04-04 14:58 UTC #4 lore raw

Hi Gary,

Quoted 64 lines · Gary Thomas

Quoted 55 lines · Bruce Ashfield
Quoted 45 lines · Andrea Galbusera
Hi Tomas,
Quoted 33 lines · Tomas Frydrych
Hi,
I am trying to get Yocto image built from yesterday's master (Linux-3.0.23-yocto-standard) to boot on the NAND-less version of BeagleBoard xM, but the kernel panics with:
----------------- console log start ------------
Waiting for root device /dev/mmcblk0p2...
mmc0: new SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.67 GiB (ro)
mmcblk0: p1 p2
VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2) Please append a correct "root=" boot option; here are the available partitions:
b300 3858432 mmcblk0 driver: mmcblk
b301 120456 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1 b302 3445942 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2
VFS: Unable to mount root fs on unknown-block(179,2) User configuration error - no valid root filesystem found
Kernel panic - not syncing: Invalid configuration from end user prevents
continuing
-------------- console log end ------------------------------------
My guess would be the problem is the card being detected as 'ro' (line 3), but I do not know why that is (there is no lock switch on mmc cards).
Quoted 5 lines
The card itself is fine, it's the original card that came with the board, the original Angstrom demo boots fine from it, and yocto kernel 2.6.37 also used to boot.
Tomas
Quoted 6 lines
Looks related to the comment I wrote here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892
I have a slightly different failure with yocto 1.2 beta snapshot (same kernel) but seems related. Needs more investigation.
Anyone else having problem booting on beagleboard xM? Seems something wrong happened after 1.1 release...
Quoted 6 lines
We are working on several bugs on our reference beagleboard. The problem is that my beagleboard died (a horrible painful death) and the other boards
that are directly available to are RevC and they are booting. So things are slowed down a bit .. but we are trying to get to the bottom of it, as fast as possible.

Quoted 6 lines

Just FYI, it also doesn't boot on my rev-C3 (not xM), albeit with a different
error pattern. It hangs at this point:
Waiting for root device /dev/mmcblk0p2...
mmc0: error -110 whilst initialising SD card

That's exactly the same error I see! Happy to know am not alone...

Quoted 1 line

Looks like you might need the attached patch?

I'm going to give it a try as soon as I can. Did you already submit it somewhere?

Andrea

Gary Thomas

2012-04-04 15:07 UTC #5 lore raw

Quoted 74 lines · Andrea Galbusera

Hi Gary,
Quoted 64 lines · Gary Thomas
Quoted 55 lines · Bruce Ashfield
Quoted 45 lines · Andrea Galbusera
Hi Tomas,
Quoted 33 lines · Tomas Frydrych
Hi,
I am trying to get Yocto image built from yesterday's master (Linux-3.0.23-yocto-standard) to boot on the NAND-less version of BeagleBoard xM, but the kernel panics with:
----------------- console log start ------------
Waiting for root device /dev/mmcblk0p2...
mmc0: new SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.67 GiB (ro)
mmcblk0: p1 p2
VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2) Please append a correct "root=" boot option; here are the available partitions:
b300 3858432 mmcblk0 driver: mmcblk
b301 120456 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1 b302 3445942 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2
VFS: Unable to mount root fs on unknown-block(179,2) User configuration error - no valid root filesystem found
Kernel panic - not syncing: Invalid configuration from end user prevents
continuing
-------------- console log end ------------------------------------
My guess would be the problem is the card being detected as 'ro' (line 3), but I do not know why that is (there is no lock switch on mmc cards).
Quoted 5 lines
The card itself is fine, it's the original card that came with the board, the original Angstrom demo boots fine from it, and yocto kernel 2.6.37 also used to boot.
Tomas
Quoted 6 lines
Looks related to the comment I wrote here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892
I have a slightly different failure with yocto 1.2 beta snapshot (same kernel) but seems related. Needs more investigation.
Anyone else having problem booting on beagleboard xM? Seems something wrong happened after 1.1 release...
Quoted 6 lines
We are working on several bugs on our reference beagleboard. The problem is that my beagleboard died (a horrible painful death) and the other boards
that are directly available to are RevC and they are booting. So things are slowed down a bit .. but we are trying to get to the bottom of it, as fast as possible.
Quoted 6 lines
Just FYI, it also doesn't boot on my rev-C3 (not xM), albeit with a different
error pattern. It hangs at this point:
Waiting for root device /dev/mmcblk0p2...
mmc0: error -110 whilst initialising SD card

Quoted 6 lines

That's exactly the same error I see! Happy to know am not alone...
Quoted 1 line
Looks like you might need the attached patch?
I'm going to give it a try as soon as I can. Did you already submit it somewhere?

I haven't had a chance to try it yet. I got it from the meta-ti layer.

Signature · 4 lines

------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Robert Berger

2012-04-04 18:49 UTC #6 lore raw

In reply to Gary Thomas

Garry/Andrea,

I am currently giving a training based on the Beagle-XM an this error happened at the same time on 5 boards with a 3.1 kernel.

Quoted 4 lines

error pattern. It hangs at this point:
Waiting for root device /dev/mmcblk0p2...
mmc0: error -110 whilst initialising SD card

The fix was to change the SD cards and use cards from a different manufacturer, so yes, it seems to be related to some funny SD card timings.

I did not try to patch yet.

Regards,

Robert

..."To assert that the earth revolves around the sun is as erroneous as to claim that Jesus was not born of a virgin." - Cardinal Bellarmine 1615, during the trial of Galileo

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1

Chris Tapp

2012-04-04 19:11 UTC #7 lore raw

Quoted 6 lines · Robert Berger

Garry/Andrea,
I am currently giving a training based on the Beagle-XM an this error happened at the same time on 5 boards with a 3.1 kernel.

Quoted 7 lines

Quoted 4 lines
error pattern. It hangs at this point:
Waiting for root device /dev/mmcblk0p2...
mmc0: error -110 whilst initialising SD card
The fix was to change the SD cards and use cards from a different manufacturer, so yes, it seems to be related to some funny SD card timings.

Not sure if it help, but the Raspberry Pi team have been having problems with SD cards as well. Some work, some don't - even when they have the same part numbers. Seems as if some silicon / firmware revision along the way has changed something somewhere...

Chris

Tomas Frydrych

author

2012-04-05 05:31 UTC #8 lore raw

In reply to Gary Thomas

Quoted 59 lines · Gary Thomas

Quoted 51 lines · Bruce Ashfield
Quoted 41 lines · Andrea Galbusera
Hi Tomas,
Quoted 37 lines · Tomas Frydrych
Hi,
I am trying to get Yocto image built from yesterday's master (Linux-3.0.23-yocto-standard) to boot on the NAND-less version of BeagleBoard xM, but the kernel panics with:
----------------- console log start ------------
Waiting for root device /dev/mmcblk0p2...
mmc0: new SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.67 GiB (ro)
mmcblk0: p1 p2
VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2) Please append a correct "root=" boot option; here are the available partitions:
b300 3858432 mmcblk0 driver: mmcblk
b301 120456 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1 b302 3445942 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2
VFS: Unable to mount root fs on unknown-block(179,2) User configuration error - no valid root filesystem found
Kernel panic - not syncing: Invalid configuration from end user
prevents
continuing
-------------- console log end ------------------------------------
My guess would be the problem is the card being detected as 'ro' (line 3), but I do not know why that is (there is no lock switch on mmc cards).
The card itself is fine, it's the original card that came with the board, the original Angstrom demo boots fine from it, and yocto kernel 2.6.37 also used to boot.
Quoted 8 lines
Quoted 1 line
Tomas
Looks related to the comment I wrote here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892
I have a slightly different failure with yocto 1.2 beta snapshot (same kernel) but seems related. Needs more investigation.
Anyone else having problem booting on beagleboard xM? Seems something wrong happened after 1.1 release...
Quoted 6 lines
We are working on several bugs on our reference beagleboard. The problem is that my beagleboard died (a horrible painful death) and the other boards
that are directly available to are RevC and they are booting. So things are slowed down a bit .. but we are trying to get to the bottom of it, as fast as possible.

Quoted 7 lines

Just FYI, it also doesn't boot on my rev-C3 (not xM), albeit with a different
error pattern. It hangs at this point:
Waiting for root device /dev/mmcblk0p2...
mmc0: error -110 whilst initialising SD card
Looks like you might need the attached patch?

This is a different issue. I get this too with one particular MMC card, but with 2.6.37 kernel, if I unplug this card and plug it back in the boot resumes and completes successfully. If I do this with the 3.0.2 kernel, the bug I described with the associated kernel panic then kicks in.

Tomas

Quoted 7 lines

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Ryan Julian

2012-06-12 23:05 UTC #9 lore raw

Quoted 5 lines · Tomas Frydrych

This is a different issue. I get this too with one particular MMC card, but with 2.6.37 kernel, if I unplug this card and plug it back in the boot resumes and completes successfully. If I do this with the 3.0.2 kernel, the bug I described with the associated kernel panic then kicks in.

Quoted 11 lines

Tomas
Quoted 7 lines
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto

Bruce and Tomas,
Did you ever find a solution to this issue?

I'm encountering the same issue on the BB-xM Rev C. I've tested on two different boards from different production runs, both with an error identical to Tomas'. I'd be happy to run tests/provide logs if given instructions.

Thanks!

-Ryan

Bruce Ashfield

2012-06-12 23:10 UTC #10 lore raw

Quoted 18 lines · Ryan Julian

Quoted 5 lines · Tomas Frydrych
This is a different issue. I get this too with one particular MMC card, but with 2.6.37 kernel, if I unplug this card and plug it back in the boot resumes and completes successfully. If I do this with the 3.0.2 kernel, the bug I described with the associated kernel panic then kicks in.
Quoted 11 lines
Tomas
Quoted 7 lines
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto

Quoted 6 lines

Bruce and Tomas,
Did you ever find a solution to this issue?
I'm encountering the same issue on the BB-xM Rev C. I've tested on two different boards from different production runs, both with an error identical to Tomas'. I'd be happy to run tests/provide logs if given instructions.

We did. Denys provided us a fix, the only one that was available at the time:

commit a49b0ec1356bb15a6a8c76b76c464ab3f1f61840

Author: Bruce Ashfield <[email protected]>
Date:   Tue Apr 17 13:45:47 2012 -0400

meta/beagleboard: disable CONFIG_PREEMPT

The boot hangs with the message:
mmc0: error -110 whilst initialising SD card

The MMC driver has issues initializing when PREEMPT is enabled
(either forced
or voluntary). Unplugging and then plugging the card back will reset the driver and continue booting. Alternatively, disable preemption.

Signed-off-by Denys Dmytriyenko <[email protected]>

Signed-off-by Bruce Ashfield <[email protected]>

:000000 100644 0000000... 0cbeb5a... A bsp/beagleboard/no-preempt.cfg :000000 100644 0000000... 1e75e15... A bsp/beagleboard/no-preempt.scc

Cheers,

Bruce

Quoted 11 lines

Thanks!
-Ryan
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Signature · 2 lines

"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Ryan Julian

2012-06-12 23:39 UTC #11 lore raw

Hi Bruce,

The build I'm using already includes Denys' patch.

I was referring to Tomas' original problem, in which the MMC card successfully initialized, but the kernel still panics while trying to mount mmcblk0p2. These two seem unrelated, unless I'm mistaken.

Quoted 75 lines · Bruce Ashfield

Quoted 5 lines · Ryan Julian
Quoted 4 lines · Tomas Frydrych
This is a different issue. I get this too with one particular MMC card, but with 2.6.37 kernel, if I unplug this card and plug it back in the boot resumes and completes successfully. If I do this with the 3.0.2 kernel, the bug I described with the associated kernel panic then kicks
in.
Quoted 13 lines
Quoted 12 lines
Tomas
Quoted 7 lines
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
Quoted 4 lines
Bruce and Tomas,
Did you ever find a solution to this issue?
I'm encountering the same issue on the BB-xM Rev C. I've tested on two
different
Quoted 1 line
boards from different production runs, both with an error identical to
Tomas'.
Quoted 1 line
I'd be happy to run tests/provide logs if given instructions.
We did. Denys provided us a fix, the only one that was available at the time:
commit a49b0ec1356bb15a6a8c76b76c464ab3f1f61840
Author: Bruce Ashfield <[email protected]>
Date:   Tue Apr 17 13:45:47 2012 -0400
meta/beagleboard: disable CONFIG_PREEMPT
The boot hangs with the message:
mmc0: error -110 whilst initialising SD card
The MMC driver has issues initializing when PREEMPT is enabled
(either forced
or voluntary). Unplugging and then plugging the card back will reset the driver and continue booting. Alternatively, disable preemption.
Signed-off-by Denys Dmytriyenko <[email protected]>
Signed-off-by Bruce Ashfield <[email protected]>
:000000 100644 0000000... 0cbeb5a... A bsp/beagleboard/no-preempt.cfg :000000 100644 0000000... 1e75e15... A bsp/beagleboard/no-preempt.scc
Cheers,
Bruce
Quoted 11 lines
Thanks!
-Ryan
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

Bruce Ashfield

2012-06-13 02:34 UTC #12 lore raw

Quoted 7 lines · Ryan Julian

Hi Bruce,
The build I'm using already includes Denys' patch.
I was referring to Tomas' original problem, in which the MMC card successfully initialized, but the kernel still panics while trying to mount mmcblk0p2. These two seem unrelated, unless I'm mistaken.

The two issues that we worked with ended up both being resolved by the preempt disable patch. Both stemmed from the MMC card not being recognized, and that was due to in kernel preemption.

So we may be seeing something different yet again here ..

Cheers,

Bruce

Quoted 81 lines

Quoted 76 lines · Bruce Ashfield
Quoted 19 lines · Ryan Julian
Quoted 6 lines · Tomas Frydrych
This is a different issue. I get this too with one particular MMC card, but with 2.6.37 kernel, if I unplug this card and plug it back in the boot resumes and completes successfully. If I do this with the 3.0.2 kernel, the bug I described with the associated kernel panic then kicks in.
Quoted 11 lines
Tomas
Quoted 7 lines
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
Quoted 8 lines
Bruce and Tomas,
Did you ever find a solution to this issue?
I'm encountering the same issue on the BB-xM Rev C. I've tested on two different
boards from different production runs, both with an error identical to Tomas'.
I'd be happy to run tests/provide logs if given instructions.
We did. Denys provided us a fix, the only one that was available at the time:
commit a49b0ec1356bb15a6a8c76b76c464ab3f1f61840
Author: Bruce Ashfield <[email protected]>
Date: Tue Apr 17 13:45:47 2012 -0400
meta/beagleboard: disable CONFIG_PREEMPT
The boot hangs with the message:
mmc0: error -110 whilst initialising SD card
The MMC driver has issues initializing when PREEMPT is enabled (either forced
or voluntary). Unplugging and then plugging the card back will reset the
driver and continue booting. Alternatively, disable preemption.
Signed-off-by Denys Dmytriyenko <[email protected]>
Signed-off-by Bruce Ashfield <[email protected]>
:000000 100644 0000000... 0cbeb5a... A bsp/beagleboard/no-preempt.cfg :000000 100644 0000000... 1e75e15... A bsp/beagleboard/no-preempt.scc
Cheers,
Bruce
Quoted 11 lines
Thanks!
-Ryan
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

Signature · 2 lines

"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Tomas Frydrych

author

2012-06-13 06:46 UTC #13 lore raw

Quoted 5 lines · Bruce Ashfield

Quoted 4 lines · Ryan Julian
Hi Bruce,
The build I'm using already includes Denys' patch.

Quoted 7 lines

Quoted 3 lines
I was referring to Tomas' original problem, in which the MMC card successfully initialized, but the kernel still panics while trying to mount mmcblk0p2. These two seem unrelated, unless I'm mistaken.
The two issues that we worked with ended up both being resolved by the preempt disable patch. Both stemmed from the MMC card not being recognized, and that was due to in kernel preemption.

IIRC, both of these went away with a kernel update, but I am now using a kernel from meta-ti, so I can't verify that.

Tomas