3.2 kernels can't boot on external SD/MMC card
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
IglooCommunity |
Fix Released
|
Critical
|
Thomas Espersson | ||
Linaro Android |
Invalid
|
Medium
|
Unassigned | ||
Linaro Ubuntu |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Test environment:
- Hardware: Snowball v5 or higher with external SD/MMC card
- Software: use an Ubuntu nano image flashed with lmc onto SD/MMC card (part1: boot, part2: rootfs), replace the
kernel uImage on boot part by a 3.2 STE LT kernel (stable-
In the console, we get many errors "mmc1: error -84 whilst initialising SD card" and the rootfs (mmcblk1p2) partition is not mounted (see attached console log).
If we replace the kernel with 3.1 STE LT or 3.2 linux-stericsson (Linus Walleij STE next kernel) this works fine.
The issue doesn't seem to be a mmc only problem, perhaps a PM or clocking or timing cross case issue,
but after multiple investigations, I failed to find the root cause.
NB: We use PIO mode for SD/MMC driver (DMA disabled in board-mop500-sdi.c)
visibility: | private → public |
Changed in igloocommunity: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
Changed in igloocommunity: | |
assignee: | nobody → Patrik Klinger (patrik-klinger) |
Changed in igloocommunity: | |
assignee: | Patrik Klinger (patrik-klinger) → Thomas Espersson (espersson) |
milestone: | none → 2012.01 |
Changed in igloocommunity: | |
status: | Confirmed → Fix Committed |
Changed in linaro-ubuntu: | |
milestone: | none → 12.01 |
Changed in linaro-android: | |
milestone: | none → 12.02 |
Changed in linaro-ubuntu: | |
status: | New → Fix Released |
Changed in igloocommunity: | |
status: | Fix Committed → Fix Released |
Changed in linaro-android: | |
assignee: | nobody → Mathieu Poirier (mathieu.poirier) |
milestone: | 12.02 → none |
importance: | Undecided → Medium |
With 3.2 kernel released by the community, it is very important that we move the stable kernel release to 3.2 . Unfortunately, the move is *blocked* by our inability to resolve this issue. The issue has been escalated to Thomas E. and Patrik K. to try and secure internal ST-Ericsson resources to help resolve it.