Solution to Android vold and sdio conflicts

Source: Internet
Author: User

The Development Board has two MMC interfaces: one is mounted to the SD card and the other is mounted to the sdio interface. When Android is started at the same time, vold crashes and cannot be started.
The error code is as follows:
# Logcat

I/vold (1930): Android volume daemon version 2.0

E/(1941): Listen at 0.0.0.0: 22501

I/vold (1930): New MMC card 'sa02g' (Serial 2619342940) added @/devices/platform/mxsdhci.0/mmc_host/mmc0/mmc0: 1234

I/vold (1930): disk (blkdev 179: 0), 3854336 secs (1882 MB) 2 partitions

I/vold (1930): New blkdev 179.0 on media sa02g, media path/devices/platform/mxsdhci.0/mmc_host/mmc0/mmc0: 1234, dpp 2

I/vold (1930): partition (blkdev 179: 1), 2097153 secs (1024 MB) Type 0x83

I/vold (1930): New blkdev 179.1 on media sa02g, media path/devices/platform/mxsdhci.0/mmc_host/mmc0/mmc0: 1234, DPP 1

I/vold (1930): partition (blkdev 179: 2), 1717183 secs (838 MB) Type 0x83

I/vold (1930): New blkdev 179.2 on media sa02g, media path/devices/platform/mxsdhci.0/mmc_host/mmc0/mmc0: 1234, DPP 0

I/vold (1930): Evaluating Dev '/devices/platform/mxsdhci.0/mmc_host/mmc0/mmc0: 1234/block/mmcblk0' for mountable filesystems for'/sdcard'

I/vold (1930): Aborting start of/sdcard (bootstrap = 1)

I/vold (1930): volmgr not ready to handle device

I/debug (1931 ): **************************************** ********

I/debug (1931): Build fingerprint: 'freescale/imx51_bbg/imx51_bbg/: 2.1/erd79/eng. root.20100527.144938: Eng/test-keys'

I/debug (1931): PID: 1930, TID: 1930 >>>/ system/bin/vold <

I/debug (1931): Signal 11 (SIGSEGV), fault ADDR 00000000

I/debug (1931): R0 00000000 R1 00020000 R2 80808080 R3 00000000

I/debug (1931): R4 000121d4 R5 be97140c R6 be9713f8 R7 be971610

I/debug (1931): R8 00000000 R9 00000000 10 00000000 FP 00000000

I/debug (1931): IP 00012320 SP be9713d8 LR running a9a5 PC afe0e7c8 CPSR 40000010

I/debug (1931): #00 PC release e7c8/system/lib/libc. So

I/debug (1931): #01 PC restart a9a2/system/bin/vold

I/debug (1931): #02 PC release ab48/system/bin/vold

I/debug (1931): #03 PC release ac26/system/bin/vold

I/debug (1931): #04 PC 00009844/system/bin/vold

I/debug (1931): #05 PC unzip c2c6/system/lib/libc. So

I/debug (1931): #06 PC b00018aa/system/bin/linker

I/debug (1931 ):

I/debug (1931): code around PC:

I/debug (1931): afe0e7b8 e31c0003 1afffff6 e1a00002 e59f20d8

I/debug (1931): afe0e7c8 e490c004 e0433000 f5d0f040 e04c13a2

I/debug (1931): afe0e7d8 e0011002 e1d1100c 0490c004 1a000022

I/debug (1931 ):

I/debug (1931): code around LR:

I/debug (1931): 440a994 9905 edae f0009804 9003 fcad edd6f7fe

I/debug (1931): g0a9a4 21009b03 4b3a181a 70113a01 18e19a03

I/debug (1931): 415a9b4 f7fe1c28 9803ed9c edf8f7fe f7fe1c28

I/debug (1931 ):

I/debug (1931): Stack:

I/debug (1931): be971398 00000000

I/debug (1931): be97139c afe0bca5/system/lib/libc. So

I/debug (1931): be9713a0 00000000

I/debug (1931): be9713a4 afe0b39b/system/lib/libc. So

I/debug (1931): be9713a8 be97140c [Stack]

I/debug (1931): be9713ac 00000010

I/debug (1931): be9713b0 be971610 [Stack]

......

View the vold source code. vold reads/sys % S/type/sys % S/Name


System/CORE/vold/mmc. C may be empty and stack errors may occur.

Modify the patch as follows: Index: MMC. c ======================================================== =============================--- MMC. C (Revision 1) ++ MMC. C (Revision 280) @-, 6 + @ sprintf (filename, "/sys % S/type", devpath); P = read_file (filename, & sz ); + If (P = NULL) + {+ LogE ("unable to read % s/n", filename); + return-errno; ++} p [strlen (P) -1] = '/0'; sprintf (TMP, "mmc_type = % s", P); free (p); @-157,6 + 162,11 @ sprintf (filename, "/sys % S/Name", devpath); P = read_file (filename, & sz); + If (P = NULL) + {+ LogE ("unable to read % s/n", filename); + return-errno; +} p [strlen (P)-1] = '/0 '; sprintf (TMP, "mmc_name = % s", P); free (P );
Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.