Waiting for root device /dev/mmcblk0p2... mmc0: error -110 whilst initialising SD card

[GoogleCodeExporter]

What steps will reproduce the problem?
1.I used procedure mentioned in rowboat site for beagleboard C3. Downloaded 
2.6.37 kernel gingerbread as per the details mentioned in site 

2.copied root and system folders to android_rootfs and created rootfs.bz2
3.

What is the expected output? What do you see instead?
 It should mount rootfs and give login prompt but the error is

 Waiting for root device /dev/mmcblk0p2...
 mmc0: error -110 whilst initialising SD card

What version of the product are you using? On what operating system?
I downloaded 2.6.37 kernel gingerbread

Please provide any additional information below.
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Linux-2.6.37-g3b51b95
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2796888 Bytes = 2.7 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37-g3b51b95 (root@dhcppc10) (gcc version 4.4.0 (GCC) ) #2 Tue 
Dec 27 16:49:35 IST 2011
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Beagle Board
Reserving 12582912 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP3430/3530 ES3.0 (l2cache iva sgx neon isp )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x10000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 61952
Kernel command line: console=ttyO2,115200n8 mpurate=600 vram=12M 
omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw 
rootfstype=ext3 rootwait init=/init rw
.....
...
ALSA device list:
  #0: omap3beagle
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
NET: Registered protocol family 15
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
ThumbEE CPU extension supported.
Power Management for TI OMAP3.
smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
SmartReflex Class3 initialized
clock: disabling unused clocks to save power
platform mpu.0: omap_voltage_scale: Already at the requestedrate 600000000
fbcvt: 1024x768@60: CVT Name - .786M3-R
regulator_init_complete: incomplete constraints, leaving VDAC on
twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 15
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 16
Waiting for root device /dev/mmcblk0p2...
mmc0: error -110 whilst initialising SD card

Original issue reported on code.google.com by swara...@gmail.com on 30 Dec 2011 at 6:06

Attachments:

• beagle_error_log.txt

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

can anybody send me android rootfs directory stucture, as kernel is looking for 
init files. What are the init files that android would be looking for?

Original comment by swara...@gmail.com on 30 Dec 2011 at 6:20

[GoogleCodeExporter]

"Waiting for root device /dev/mmcblk0p2...
mmc0: error -110 whilst initialising SD card
"

There seems to be some problem in initializing the sd card after the kernel 
booted. So you are not able to boot.
Can you check if the card is inserted properly and that the sdcard gets power 
after kernel has booted.

Original comment by vishvesh...@aim.com on 30 Dec 2011 at 10:05

[GoogleCodeExporter]

Thanks for the reply Vishvesh
I resolved that issue, I enabled CONFIG_EMBEDDED_SDIO and MMC_DEBUG in kernel 
configs that solved mmc issue and i'm able to get the prompt. 

Now i'm facing problem with "init untracked pid xxx exit " error and its 
restarting the board. If try to print logcat  it says no /dev/(something)/main 
unavailable.

Can you help me in resolving this issue.

I attached complete log.
FYI... these are the last lines of the log:

mice: PS/2 mouse device common for all mice
input: gpio-keys as /devices/platform/gpio-keys/input/input0
input: twl4030_pwrbutton as 
/devices/platform/omap/omap_i2c.1/i2c-1/1-0049/twl4030_pwrbutton/input/input1
using rtc device, twl_rtc, for alarms
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
twl_rtc twl_rtc: Power up reset detected.
twl_rtc twl_rtc: Enabling TWL-RTC.
i2c /dev entries driver
Linux media interface: v0.10
Linux video capture interface: v2.00
omap3isp supply VDD_CSIPHY1 not found, using dummy regulator
omap3isp supply VDD_CSIPHY2 not found, using dummy regulator
omap3isp omap3isp: Revision 2.0 found
omap-iommu omap-iommu.0: isp: version 1.1
omap_i2c omap_i2c.2: controller timed out
mt9v113 2-003c: chip id mismatch read 0x0, expecting 0x2280
isp_register_subdev_group: Unable to register subdev mt9v113
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
twl4030_wdt twl4030_wdt: Failed to register misc device
twl4030_wdt: probe of twl4030_wdt failed with error -16
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: dm-devel@redhat.com
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mmc_rescan: trying to init card at 400000 Hz
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
OMAP3 Beagle/Devkit8000 SoC init
asoc: twl4030-hifi <-> omap-mcbsp-dai.1 mapping ok
ALSA device list:
  #0: omap3beagle
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
NET: Registered protocol family 15
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
ThumbEE CPU extension supported.
Power Management for TI OMAP3.
smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
SmartReflex Class3 initialized
clock: disabling unused clocks to save power
platform iva.0: omap_voltage_scale: Already at the requestedrate 360000000
platform mpu.0: omap_voltage_scale: Already at the requestedrate 500000000
regulator_init_complete: incomplete constraints, leaving VDAC on
twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 15
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 16
Waiting for root device /dev/mmcblk0p2...
mmc0: new high speed SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.68 GiB 
 mmcblk0: p1 p2
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 212K
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj 
instead.
init: cannot find '/system/bin/sgx/rc.pvr', disabling 'pvr'
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
sh: can't accessinit: untracked pid 996 exited
 tty; job control turned off
init: untracked pid 997 exited
# init: untracked pid 1001 exited
init: untracked pid 1041 exited
init: untracked pid 1045 exited
init: untracked pid 1042 exited
init: untracked pid 1046 exited
init: critical process 'servicemanager' exited 4 times in 4 minutes; rebooting 
into recovery mode
Restarting system with command 'recovery'.
###40#W######�C�H�U�́Instruments X-Loader 1.51 (Dec 23 2011 - 13:51:31)
Beagle Rev C4
Starting X-loader on MMC 
Reading boot sector

213432 Bytes Read from MMC 
Starting OS Bootloader from MMC...
Starting OS Bootloader...

Original comment by swara...@gmail.com on 30 Dec 2011 at 11:20

Attachments:

• minicom_beagle.cap