Hi,
On 12/04/2012 05:51 PM, Andy Green wrote:
On 05/12/12 08:51, the mail apparently from Juri Lelli included:
Hi all,
in the process of testing scheduler patches on a Pandaboard ES, I
found a possible regression regarding OMAP mmc. The system is a
Pandaboard ES (OMAP4460 ES1.1) running Linaro 12.10 (GNU/Linux
3.4.0-2-linaro-lt-omap armv7l).
The problem is that the system remains stuck at boot time trying
to mount the root device.
This is what I got via git bisect from Linux 3.5 and Linux 3.7-rc7:
26b88520b80695a6fa5fd95b5d97c03f4daf87e0 is the first bad commit
commit 26b88520b80695a6fa5fd95b5d97c03f4daf87e0
Author: Russell King <rmk+ker...@arm.linux.org.uk>
Date: Fri Apr 13 12:27:37 2012 +0100
mmc: omap_hsmmc: remove private DMA API implementation
Remove the private DMA API implementation from omap_hsmmc, making it
use entirely the DMA engine API.
Tested-by: Tony Lindgren <t...@atomide.com>
Tested-by: Venkatraman S <svenk...@ti.com>
Signed-off-by: Russell King <rmk+ker...@arm.linux.org.uk>
:040000 040000 03cff4d68cc92ea652ef8e0c6ac74af804bc9f00
a9763c6b364bfc66b5fcd4cada7315befcbd62e8 M drivers
Here instead the two boot traces, before (all OK) and after the bad
commit.
Hi -
I'd suggest some caution pointing the finger on that one. We
experienced a similar problem earlier in the year bringing up OMAP5
chips, there is a race somewhere that gives these symptoms we were
unable to pin down despite spending a lot of time on it.
Yes, I wasn't blaming anyone, just telling that something changed
for me at that point in the way my board boots (or not :).
Changing the configuration according to what Robert Nelson suggested
solves the problem.
BTW, do you think writing down this experience somewhere (Linaro
wiki?) would help other people?
Thank you both for your help.
Best Regards,
- Juri
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
