[Q] Phone's partition table corrupted (?)

[Q] Phone's partition table corrupted (?) - Samsung Galaxy Nexus

After fiddling with every possible options available, I think my phones lagging has to be a problem caused by a corrupt partition table. I first ran this command :
[email protected]:/ # dmesg | grep mmc0
dmesg | grep mmc0
And when I ran :
1|[email protected]:/ # dmesg | grep mmc
dmesg | grep mmc , I got :::
<3>[ 102.344421] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.344482] mmcblk0: command error, retrying timeout
<3>[ 102.345764] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.345855] mmcblk0: command error, retrying timeout
<3>[ 102.346282] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.346405] mmcblk0: command error, retrying timeout
<3>[ 102.346893] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.347015] mmcblk0: command error, retrying timeout
<3>[ 102.347595] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.347747] mmcblk0: command error, retrying timeout and so on.
Full log available here : http://pastebin.com/9VRqRez8
I can access fastboot/Downloading mode without hassle. Making the adb working or getting past the first launch screen is a real pain.
I tried repartitioning using ODIN using I9250_partition-table-0915.pit and it was a success. Even I tried to flash stock ROM using ODIN v1.85. Even though it was a success, old ROM keeps loading up.
Is there anything I can do?
Is there anything that I can do?

Related

SD card problems under 2.2

I had this problem with my old class 2 4gb card and now i bought a brand new class 6 card. The kernel cannot read the sectors, at least that is what i found out from dmesg.
Code:
<3>[ 113.875640] end_request: I/O error, dev mmcblk0, sector 676358
<3>[ 113.875915] Buffer I/O error on device mmcblk0p1, logical block 674310
<4>[ 113.876373] lost page write due to I/O error on mmcblk0p1
<3>[ 113.877349] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 113.877807] mmcblk0: error -110 transferring data, sector 676358, nr 1, ca
rd status 0x400e00
<3>[ 113.878448] end_request: I/O error, dev mmcblk0, sector 676358
<3>[ 113.878936] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 113.879425] mmcblk0: error -110 transferring data, sector 676358, nr 1, ca
rd status 0x400e00
<3>[ 113.879882] end_request: I/O error, dev mmcblk0, sector 676358
<3>[ 113.880187] FAT: Directory bread(block 674310) failed
<3>[ 113.886108] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 113.886566] mmcblk0: error -110 transferring data, sector 676359, nr 1, ca
rd status 0x400e00
<3>[ 113.886871] end_request: I/O error, dev mmcblk0, sector 676359
<3>[ 113.887329] Buffer I/O error on device mmcblk0p1, logical block 674311
<4>[ 113.887573] lost page write due to I/O error on mmcblk0p1
the windows can access every sector on the phone, so the cards have to be good. This sometimes freezes the phone. I think this is the source of the occasional google maps freezes and lags and that causes problems for some games that runs from the card. Does anyone experienced anything similar?

I have stole the 4 gig card out of my gf-s phone it is a class 4 kingston, and with that card everything is perfect. The other cards are A-Data cards, the good card is Kingston. I will try to changethe card back to kingston in the shop.

With my girlfriends card, the io errors are gone and the black screen freezing too, but a couple softwares still horribly slow and unresponsive, like Dungeon Defenders and Sygic Aura and sometimes even google maps. I donwgraded to 2.51 and everything is nice and smooth. I used the sygic aura for a 300km travel, under 3.4.2 the software becomes unresponsive after a couple minutes. The google maps worked for longer under froyo, but it still became unresponsive after a couple hours. Similar goes for games too, so after a month of froyo i am back again using eclair...
Anyone experienced the same things with froyo or just my phone hates froyo Or the recent foyo realeases are still beta?

I am having the same thing with you again with my new 8G Kingston card. And the card just seems fine by chkdsk on windows. I suppose there are lots of problems with this kernel.
vick33 said:
I had this problem with my old class 2 4gb card and now i bought a brand new class 6 card. The kernel cannot read the sectors, at least that is what i found out from dmesg.
Code:
<3>[ 113.875640] end_request: I/O error, dev mmcblk0, sector 676358
<3>[ 113.875915] Buffer I/O error on device mmcblk0p1, logical block 674310
<4>[ 113.876373] lost page write due to I/O error on mmcblk0p1
<3>[ 113.877349] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 113.877807] mmcblk0: error -110 transferring data, sector 676358, nr 1, ca
rd status 0x400e00
<3>[ 113.878448] end_request: I/O error, dev mmcblk0, sector 676358
<3>[ 113.878936] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 113.879425] mmcblk0: error -110 transferring data, sector 676358, nr 1, ca
rd status 0x400e00
<3>[ 113.879882] end_request: I/O error, dev mmcblk0, sector 676358
<3>[ 113.880187] FAT: Directory bread(block 674310) failed
<3>[ 113.886108] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 113.886566] mmcblk0: error -110 transferring data, sector 676359, nr 1, ca
rd status 0x400e00
<3>[ 113.886871] end_request: I/O error, dev mmcblk0, sector 676359
<3>[ 113.887329] Buffer I/O error on device mmcblk0p1, logical block 674311
<4>[ 113.887573] lost page write due to I/O error on mmcblk0p1
the windows can access every sector on the phone, so the cards have to be good. This sometimes freezes the phone. I think this is the source of the occasional google maps freezes and lags and that causes problems for some games that runs from the card. Does anyone experienced anything similar?
Click to expand...
Click to collapse

Unfortunately I'm having exactly the same issues in my Milestone with a Transcend Class 10 card.
It seems that the problem is with the OMAP MMC default drivers, as this discussion in maemo.org shows:
http://maemo.org/community/maemo-users/n900_microsd_card_i-o_errors_and_corruption/
That means, if your card doesn't work good on the phone but works perfect on your PC, it is most likely incompatible with default OMAP MMC drivers, unless someone changes it (I'm not even sure if that is possible with our locked bootloaders, if those drivers are part of the kernel, I guess there is no way to do that), it won't ever properly work.
P.s.: I've tested the transcend card in a USB adapter, everything goes just fine, no errors with hw2test, so, it is really a case were bugorolla and TI supplied drivers are causing incompatibilities.

SD Card Problems

Hello,
i have CM7 and the SD Card has Problems. Sometime it wakes not from the Standby up. On Froyo also the selfe problem. But on Eclair is all good.
Dmesg says:
Code:
<3>[ 92.844055] end_request: I/O error, dev mmcblk0, sector 11576
<3>[ 92.844207] end_request: I/O error, dev mmcblk0, sector 11584
<3>[ 92.844329] end_request: I/O error, dev mmcblk0, sector 11592
<3>[ 92.844482] end_request: I/O error, dev mmcblk0, sector 11600
<3>[ 92.844573] end_request: I/O error, dev mmcblk0, sector 11608
<3>[ 92.844726] end_request: I/O error, dev mmcblk0, sector 11616
<3>[ 92.844818] end_request: I/O error, dev mmcblk0, sector 11624
<3>[ 92.845001] end_request: I/O error, dev mmcblk0, sector 11632
<3>[ 92.845092] end_request: I/O error, dev mmcblk0, sector 11640
<3>[ 92.845245] end_request: I/O error, dev mmcblk0, sector 11648
<3>[ 92.845336] end_request: I/O error, dev mmcblk0, sector 11656
<3>[ 92.845520] end_request: I/O error, dev mmcblk0, sector 11664
<3>[ 92.845611] end_request: I/O error, dev mmcblk0, sector 11672
<3>[ 92.845764] end_request: I/O error, dev mmcblk0, sector 11680
<3>[ 92.845855] end_request: I/O error, dev mmcblk0, sector 11688
<3>[ 92.846038] end_request: I/O error, dev mmcblk0, sector 11696
<3>[ 92.846130] end_request: I/O error, dev mmcblk0, sector 11704
<3>[ 92.846282] end_request: I/O error, dev mmcblk0, sector 11712
<3>[ 92.846374] end_request: I/O error, dev mmcblk0, sector 11720
<3>[ 92.846527] end_request: I/O error, dev mmcblk0, sector 11728
<3>[ 92.846618] end_request: I/O error, dev mmcblk0, sector 11736
<3>[ 92.846801] end_request: I/O error, dev mmcblk0, sector 11744
<3>[ 92.846893] end_request: I/O error, dev mmcblk0, sector 11752
<3>[ 92.847045] end_request: I/O error, dev mmcblk0, sector 11760
<3>[ 92.847137] end_request: I/O error, dev mmcblk0, sector 11768
<3>[ 92.847290] end_request: I/O error, dev mmcblk0, sector 11776
<3>[ 92.847412] end_request: I/O error, dev mmcblk0, sector 11784
<3>[ 92.847564] end_request: I/O error, dev mmcblk0, sector 11792
<3>[ 92.847656] end_request: I/O error, dev mmcblk0, sector 11800
<3>[ 92.847808] end_request: I/O error, dev mmcblk0, sector 11808
<3>[ 92.847900] end_request: I/O error, dev mmcblk0, sector 11816
<3>[ 92.848083] end_request: I/O error, dev mmcblk0, sector 11824
<3>[ 92.848175] end_request: I/O error, dev mmcblk0, sector 11832
<3>[ 92.848327] end_request: I/O error, dev mmcblk0, sector 11840
<3>[ 92.848419] end_request: I/O error, dev mmcblk0, sector 11848
<3>[ 92.848571] end_request: I/O error, dev mmcblk0, sector 11856
<3>[ 92.848663] end_request: I/O error, dev mmcblk0, sector 11864
<3>[ 92.848846] end_request: I/O error, dev mmcblk0, sector 11872
<3>[ 92.848937] end_request: I/O error, dev mmcblk0, sector 11880
<3>[ 92.849090] end_request: I/O error, dev mmcblk0, sector 11888
<3>[ 92.849182] end_request: I/O error, dev mmcblk0, sector 11896
<3>[ 92.849334] end_request: I/O error, dev mmcblk0, sector 11904
<3>[ 92.849426] end_request: I/O error, dev mmcblk0, sector 11912
<3>[ 92.849609] end_request: I/O error, dev mmcblk0, sector 11920
<3>[ 92.849761] end_request: I/O error, dev mmcblk0, sector 11928
<7>[ 97.077331] turning off regulator
<7>[ 119.222900] turning off regulator
<3>[ 122.393859] mmcblk0: error -110 transferring data, sector 263352, nr 1, ca
rd status 0xe00
<3>[ 122.394195] end_request: I/O error, dev mmcblk0, sector 263352
<4>[ 122.394958] mmcblk0: retrying using single block read
<3>[ 122.395324] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.395812] mmcblk0: error -110 transferring data, sector 1181976, nr 10,
card status 0x400e00
<3>[ 122.396331] end_request: I/O error, dev mmcblk0, sector 1181976
<3>[ 122.396606] end_request: I/O error, dev mmcblk0, sector 1181984
<4>[ 122.397399] mmcblk0: retrying using single block read
<3>[ 122.397766] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.398284] mmcblk0: error -110 transferring data, sector 1181976, nr 8, c
ard status 0x400e00
<3>[ 122.398773] end_request: I/O error, dev mmcblk0, sector 1181976
<3>[ 122.488830] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.489074] mmcblk0: error -110 transferring data, sector 583696, nr 1, ca
rd status 0x400e00
<3>[ 122.489562] end_request: I/O error, dev mmcblk0, sector 583696
<4>[ 122.489654] __ratelimit: 118 callbacks suppressed
<3>[ 122.489837] Buffer I/O error on device mmcblk0p1, logical block 581648
<4>[ 122.489929] lost page write due to I/O error on mmcblk0p1
<3>[ 122.492706] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.492889] mmcblk0: error -110 transferring data, sector 583696, nr 1, ca
rd status 0x400e00
<3>[ 122.493011] end_request: I/O error, dev mmcblk0, sector 583696
<3>[ 122.493316] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.493591] mmcblk0: error -110 transferring data, sector 583696, nr 1, ca
rd status 0x400e00
<3>[ 122.493682] end_request: I/O error, dev mmcblk0, sector 583696
<3>[ 122.493896] FAT: Directory bread(block 581648) failed
<3>[ 122.494079] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.494262] mmcblk0: error -110 transferring data, sector 583697, nr 1, ca
rd status 0x400e00
<3>[ 122.494445] end_request: I/O error, dev mmcblk0, sector 583697
<3>[ 122.494537] Buffer I/O error on device mmcblk0p1, logical block 581649
<4>[ 122.494720] lost page write due to I/O error on mmcblk0p1
<4>[ 122.521972] mmcblk0: retrying using single block read
<3>[ 122.522216] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.522369] mmcblk0: error -110 transferring data, sector 33352, nr 30, ca
rd status 0x400e00
<3>[ 122.522491] end_request: I/O error, dev mmcblk0, sector 33352
<3>[ 122.522644] end_request: I/O error, dev mmcblk0, sector 33360
<3>[ 122.522735] end_request: I/O error, dev mmcblk0, sector 33368
<3>[ 122.522888] end_request: I/O error, dev mmcblk0, sector 33376
<4>[ 122.523071] mmcblk0: retrying using single block read
<3>[ 122.523315] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.523498] mmcblk0: error -110 transferring data, sector 33352, nr 8, car
d status 0x400e00
<3>[ 122.523590] end_request: I/O error, dev mmcblk0, sector 33352
<4>[ 122.523834] mmcblk0: retrying using single block read
<3>[ 122.523986] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.524139] mmcblk0: error -110 transferring data, sector 33352, nr 8, car
d status 0x400e00
<3>[ 122.524322] end_request: I/O error, dev mmcblk0, sector 33352
<4>[ 122.524475] mmcblk0: retrying using single block read
<3>[ 122.524810] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.524993] mmcblk0: error -110 transferring data, sector 33352, nr 8, car
d status 0x400e00
<3>[ 122.525085] end_request: I/O error, dev mmcblk0, sector 33352
<4>[ 122.525329] mmcblk0: retrying using single block read
<3>[ 122.525451] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.525634] mmcblk0: error -110 transferring data, sector 33352, nr 8, car
d status 0x400e00
<3>[ 122.525787] end_request: I/O error, dev mmcblk0, sector 33352
<4>[ 122.525939] mmcblk0: retrying using single block read
<3>[ 122.526153] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.526245] mmcblk0: error -110 transferring data, sector 33352, nr 8, car
d status 0x400e00
<3>[ 122.526397] end_request: I/O error, dev mmcblk0, sector 33352
<4>[ 122.526641] mmcblk0: retrying using single block read
<3>[ 122.526794] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.526947] mmcblk0: error -110 transferring data, sector 33352, nr 8, car
d status 0x400e00
<3>[ 122.527099] end_request: I/O error, dev mmcblk0, sector 33352
<4>[ 122.527252] mmcblk0: retrying using single block read
<3>[ 122.527465] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.527557] mmcblk0: error -110 transferring data, sector 33352, nr 8, car
d status 0x400e00
<3>[ 122.527740] end_request: I/O error, dev mmcblk0, sector 33352
<4>[ 122.556274] mmcblk0: retrying using single block read
<3>[ 122.556427] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.556610] mmcblk0: error -110 transferring data, sector 33352, nr 8, car
d status 0x400e00
<3>[ 122.556762] end_request: I/O error, dev mmcblk0, sector 33352
<4>[ 122.556976] mmcblk0: retrying using single block read
<3>[ 122.557220] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.557312] mmcblk0: error -110 transferring data, sector 33352, nr 8, car
d status 0x400e00
<3>[ 122.557464] end_request: I/O error, dev mmcblk0, sector 33352
<4>[ 122.557708] mmcblk0: retrying using single block read
<3>[ 122.557830] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.558013] mmcblk0: error -110 transferring data, sector 33352, nr 8, car
d status 0x400e00
<3>[ 122.558166] end_request: I/O error, dev mmcblk0, sector 33352
<4>[ 122.558319] mmcblk0: retrying using single block read
<3>[ 122.558471] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.558624] mmcblk0: error -110 transferring data, sector 33352, nr 8, car
d status 0x400e00
<3>[ 122.558807] end_request: I/O error, dev mmcblk0, sector 33352
<4>[ 122.559020] mmcblk0: retrying using single block read
<3>[ 122.559143] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.559326] mmcblk0: error -110 transferring data, sector 33352, nr 8, car
d status 0x400e00
<3>[ 122.559417] end_request: I/O error, dev mmcblk0, sector 33352
<4>[ 122.559631] mmcblk0: retrying using single block read
<3>[ 122.559753] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.559936] mmcblk0: error -110 transferring data, sector 33352, nr 8, car
d status 0x400e00
<3>[ 122.560089] end_request: I/O error, dev mmcblk0, sector 33352
<4>[ 122.560241] mmcblk0: retrying using single block read
<3>[ 122.560455] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.560607] mmcblk0: error -110 transferring data, sector 33352, nr 8, car
d status 0x400e00
<3>[ 122.560699] end_request: I/O error, dev mmcblk0, sector 33352
<4>[ 122.578002] mmcblk0: retrying using single block read
<3>[ 122.578155] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.578308] mmcblk0: error -110 transferring data, sector 1181992, nr 32,
card status 0x400e00
<3>[ 122.578491] end_request: I/O error, dev mmcblk0, sector 1181992
<3>[ 122.578582] end_request: I/O error, dev mmcblk0, sector 1182000
<3>[ 122.578735] end_request: I/O error, dev mmcblk0, sector 1182008
<3>[ 122.578826] end_request: I/O error, dev mmcblk0, sector 1182016
<4>[ 122.579071] mmcblk0: retrying using single block read
<3>[ 122.579223] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.579376] mmcblk0: error -110 transferring data, sector 1181992, nr 8, c
ard status 0x400e00
<3>[ 122.579620] end_request: I/O error, dev mmcblk0, sector 1181992
<4>[ 122.579833] mmcblk0: retrying using single block read
<3>[ 122.580017] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.580200] mmcblk0: error -110 transferring data, sector 1181992, nr 8, c
ard status 0x400e00
<3>[ 122.580291] end_request: I/O error, dev mmcblk0, sector 1181992
<4>[ 122.580535] mmcblk0: retrying using single block read
<3>[ 122.580657] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.580810] mmcblk0: error -110 transferring data, sector 1181992, nr 8, c
ard status 0x400e00
<3>[ 122.580993] end_request: I/O error, dev mmcblk0, sector 1181992
<4>[ 122.581146] mmcblk0: retrying using single block read
<3>[ 122.581329] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.581512] mmcblk0: error -110 transferring data, sector 1181992, nr 8, c
ard status 0x400e00
<3>[ 122.581604] end_request: I/O error, dev mmcblk0, sector 1181992
<4>[ 122.581817] mmcblk0: retrying using single block read
<3>[ 122.581939] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.582122] mmcblk0: error -110 transferring data, sector 1181992, nr 8, c
ard status 0x400e00
<3>[ 122.582275] end_request: I/O error, dev mmcblk0, sector 1181992
<4>[ 122.582427] mmcblk0: retrying using single block read
<3>[ 122.582641] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.582794] mmcblk0: error -110 transferring data, sector 1181992, nr 8, c
ard status 0x400e00
<3>[ 122.582885] end_request: I/O error, dev mmcblk0, sector 1181992
<4>[ 122.583129] mmcblk0: retrying using single block read
<3>[ 122.583251] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.583404] mmcblk0: error -110 transferring data, sector 1181992, nr 8, c
ard status 0x400e00
<3>[ 122.583587] end_request: I/O error, dev mmcblk0, sector 1181992
<4>[ 122.586578] mmcblk0: retrying using single block read
<3>[ 122.586791] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.586975] mmcblk0: error -110 transferring data, sector 583696, nr 2, ca
rd status 0x400e00
<3>[ 122.587066] end_request: I/O error, dev mmcblk0, sector 583696
<3>[ 122.587249] end_request: I/O error, dev mmcblk0, sector 583697
<3>[ 122.589416] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.589569] mmcblk0: error -110 transferring data, sector 583696, nr 1, ca
rd status 0x400e00
<3>[ 122.589752] end_request: I/O error, dev mmcblk0, sector 583696
<3>[ 122.589874] FAT: Directory bread(block 581648) failed
<3>[ 122.590118] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.590270] mmcblk0: error -110 transferring data, sector 583697, nr 1, ca
rd status 0x400e00
<3>[ 122.590362] end_request: I/O error, dev mmcblk0, sector 583697
<3>[ 122.590545] FAT: Directory bread(block 581649) failed
<4>[ 122.590759] mmcblk0: retrying using single block read
<3>[ 122.590972] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.591125] mmcblk0: error -110 transferring data, sector 583696, nr 2, ca
rd status 0x400e00
<3>[ 122.591217] end_request: I/O error, dev mmcblk0, sector 583696
<3>[ 122.591400] end_request: I/O error, dev mmcblk0, sector 583697
<3>[ 122.591552] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.591705] mmcblk0: error -110 transferring data, sector 583696, nr 1, ca
rd status 0x400e00
<3>[ 122.591888] end_request: I/O error, dev mmcblk0, sector 583696
<3>[ 122.591979] FAT: Directory bread(block 581648) failed
<3>[ 122.592193] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.592376] mmcblk0: error -110 transferring data, sector 583697, nr 1, ca
rd status 0x400e00
<3>[ 122.592468] end_request: I/O error, dev mmcblk0, sector 583697
<3>[ 122.592620] FAT: Directory bread(block 581649) failed
<4>[ 122.592803] mmcblk0: retrying using single block read
<3>[ 122.592987] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.593170] mmcblk0: error -110 transferring data, sector 583696, nr 2, ca
rd status 0x400e00
<3>[ 122.593261] end_request: I/O error, dev mmcblk0, sector 583696
<3>[ 122.593414] end_request: I/O error, dev mmcblk0, sector 583697
<3>[ 122.593566] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.593719] mmcblk0: error -110 transferring data, sector 583696, nr 1, ca
rd status 0x400e00
<3>[ 122.593902] end_request: I/O error, dev mmcblk0, sector 583696
<3>[ 122.593994] FAT: Directory bread(block 581648) failed
<3>[ 122.594238] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.594390] mmcblk0: error -110 transferring data, sector 583697, nr 1, ca
rd status 0x400e00
<3>[ 122.594482] end_request: I/O error, dev mmcblk0, sector 583697
<3>[ 122.594665] FAT: Directory bread(block 581649) failed
<3>[ 122.594818] mmcblk0: error -110 sending read/write command, response 0x0,
card status 0x400e00
<3>[ 122.594970] mmcblk0: error -110 transferring data, sector 583698, nr 1, ca
rd status 0x400e00
<3>[ 122.602447] end_request: I/O error, dev mmcblk0, sector 583698
<3>[ 122.602569] Buffer I/O error on device mmcblk0p1, logical block 581650
<4>[ 122.602722] lost page write due to I/O error on mmcblk0p1
<3>[ 138.695495] evdev: event3-1109: buffer overflow
<3>[ 144.127746] evdev: event3-1109: buffer overflow
#
It is a 4GB Class 4 Card. On PC is all good. chkdsk says nothing.
Sorry for my bad Englisch .
Karsten

Please help me

I/O error suggests the card is failing; try chkdsk /R just to be certain there's not an issue with it. My new 16GB Class 10 lasted 24hrs before I saw an I/O error like this, and it's completely unusable now. Verify that you can not only read from the card, but write data to it too (writes failing were the first indication of an issue for me).

Thanks for your Answer .
This is the Result but it is German. Can i set it in English?
Code:
C:\Users\Karsten>chkdsk H: /r
Der Typ des Dateisystems ist FAT32.
Volumeseriennummer : 32BF-6A7A
Dateien und Ordner werden überprüft...
Die Datei- und Ordnerüberprüfung ist abgeschlossen.
Freier Speicherplatz wird verifiziert...
Verifizierung freien Speicherplatzes ist beendet.
Das Dateisystem wurde überprüft. Es wurden keine Probleme festgestellt.
4.114.931.712 Bytes Speicherplatz auf dem Datenträger insgesamt
4.096 Bytes in 1 versteckten Datei(en)
405.504 Bytes in 80 Ordner(n)
1.212.456.960 Bytes in 538 Datei(en)
2.902.061.056 Bytes auf dem Datenträger verfügbar
4.096 Bytes in jeder Zuordnungseinheit
1.004.622 Zuordnungseinheiten auf dem Datenträger insgesamt
708.511 Zuordnungseinheiten auf dem Datenträger verfügbar
C:\Users\Karsten>
Seeming were no problems noticed.
Karsten

Karsten95 said:
Thanks for your Answer .
This is the Result but it is German. Can i set it in English?
Code:
C:\Users\Karsten>chkdsk H: /r
Der Typ des Dateisystems ist FAT32.
Volumeseriennummer : 32BF-6A7A
Dateien und Ordner werden überprüft...
Die Datei- und Ordnerüberprüfung ist abgeschlossen.
Freier Speicherplatz wird verifiziert...
Verifizierung freien Speicherplatzes ist beendet.
Das Dateisystem wurde überprüft. Es wurden keine Probleme festgestellt.
4.114.931.712 Bytes Speicherplatz auf dem Datenträger insgesamt
4.096 Bytes in 1 versteckten Datei(en)
405.504 Bytes in 80 Ordner(n)
1.212.456.960 Bytes in 538 Datei(en)
2.902.061.056 Bytes auf dem Datenträger verfügbar
4.096 Bytes in jeder Zuordnungseinheit
1.004.622 Zuordnungseinheiten auf dem Datenträger insgesamt
708.511 Zuordnungseinheiten auf dem Datenträger verfügbar
C:\Users\Karsten>
Seeming were no problems noticed.
Karsten
Click to expand...
Click to collapse
I formatted the SDCARD as FAT32 with 64k Clusters in windows 7 have no problems, 16GB Trancend Class 6 Resd speed 31.6 MB/s Write speed 11.4MB/s Have used SDspeed Increase at 2048 read ahead.

[Q] R800X UHS high speed sdcard compatibility problems?

Hey guys. This site has been a huge help to me lately, but I just can't figure out this problem...
To start from the beginning, my R800X is second hand but was never used or activated, so its in perfect condition. It came with 2.3.2 installed on it, and I have not activated it on any service yet (I plan on moving to page plus at some point). I rooted it originally with SuperOneClick and added a 32Gb Sandisk Ultra Mobile UHS-1 Class 10 microSD (which has high read speeds and is made for smartphones and tablets) and Link2SD. Not long after that I decided to have Alejandrissimo unlock my bootloader, which went very smoothly.
The next thing I did was install CWM, and I settled on GBTweaked07 as my first ROM to try out. It seemed nice but was freezing and lagging a lot with Doomkernel, so I tried other CM7 kernels and had the same issues, some times on the first boot. I had thought at one point that it was my SD card so I removed it, formatted it with EasyUS partition master (FAT32, with a second small partition for Link2SD) and the phone just said it was damaged after that... so I formatted it AGAIN in Windows and it worked fine... or so I thought.
I was still having some random lag\freezing and other problems, so I moved on to ICS and installed FXP-142 (with the included kernel) which seemed to work the best, but out of nowhere started giving me the same issues. First I get lag and freezing, then I often times get errors loading apps (not responding or force close errors) and some app icons revery to the android logo and will not load. Rebooting and clearing cache in CWM some times fixes it, but it comes back again later... its really irritating, to say the least. Some times it causes the phone to reboot itself (not completely, CM9.1 just reloads without going back to the FXP screen), other times it makes the phone completely unresponsive with the back-light seemingly stuck off, and I have to pop the battery out to get things working again. Other times, I can play SuperGSNES for hours with no problems at all.
I have used OSMonitor to dig up some error messages, and I've found that these seem to pop up when the phone is going through one of its glitching spells:
Code:
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180500, nr 2, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180500
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180501, nr 1, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180501
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [WARNING] mmcblk0: retrying using single block read
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180494, nr 8, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180494
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180495, nr 7, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180495
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180496, nr 6, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180496
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180497, nr 5, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180497
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180498, nr 4, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180498
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180499, nr 3, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180499
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180500, nr 2, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180500
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180501, nr 1, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180501
10/18/2012 13:58:50 [WARNING] mmc1: Starting deferred resume
10/18/2012 13:58:50 [WARNING] mmc1: Deferred resume completed
I filtered the log to show only mmc errors (related to the memory card from what I can gather) because I get other messages related to "msm_snddev_poweramp" constantly that clutter up the log.
Now, I thought the card was just bad, but I've tested it extensively on my computer and it has no bad clusters or defects of any kind, according to chkdsk or Minitool's diagnostics. I can copy to and read from it over and over with no problems. I've tried formatting it many times, in different programs (Secure Digital SDFormatter, Windows 7, EasyUS PM, Minitool Partition Wizard...) using FAT32 (the phone couldn't read it as EXT4 and I use Windows so that isn't ideal anyway), with and without the second Link2SD partition, and even if it works for a while, the phone will eventually start screwing up and spewing those mmc errors into dmesg.
I never had any of these problems with the stock ROM\kernel and the included 8gb class 2 microSD, and the problems don't seem to occur on the current setup with my spare G.Skill 4Gb Class 4 card.
Is it possible that the phone itself just plain does not work with certain memory cards, specifically UHS-1 class cards? Is it possible that a different Kernel or ROM may fix the problem?
I'm at a loss, and I'm hoping someone can help interpret those mmc messages or point me in a direction to narrow down the cause of this madness.
Thank you!

Well, I've been playing around with a different kernel\ROM setup using my old 4Gb class 4 card, and I'm not having any sdcard errors at all. I'll keep messing with it, but it seems to be stable this way. If it works like this for a while I'll try putting the other card back in to see if it brings on the errors. If so, I'll just have to give up trying to use this card on this phone.
Ice Cream Pureness + LuPuS is fantastic... but I don't seem to have any signal and the baseband is "unknown". It doesn't really matter right now because I have no service, but this is a bit worrying...

ozzuneoj said:
Hey guys. This site has been a huge help to me lately, but I just can't figure out this problem...
To start from the beginning, my R800X is second hand but was never used or activated, so its in perfect condition. It came with 2.3.2 installed on it, and I have not activated it on any service yet (I plan on moving to page plus at some point). I rooted it originally with SuperOneClick and added a 32Gb Sandisk Ultra Mobile UHS-1 Class 10 microSD (which has high read speeds and is made for smartphones and tablets) and Link2SD. Not long after that I decided to have Alejandrissimo unlock my bootloader, which went very smoothly.
The next thing I did was install CWM, and I settled on GBTweaked07 as my first ROM to try out. It seemed nice but was freezing and lagging a lot with Doomkernel, so I tried other CM7 kernels and had the same issues, some times on the first boot. I had thought at one point that it was my SD card so I removed it, formatted it with EasyUS partition master (FAT32, with a second small partition for Link2SD) and the phone just said it was damaged after that... so I formatted it AGAIN in Windows and it worked fine... or so I thought.
I was still having some random lag\freezing and other problems, so I moved on to ICS and installed FXP-142 (with the included kernel) which seemed to work the best, but out of nowhere started giving me the same issues. First I get lag and freezing, then I often times get errors loading apps (not responding or force close errors) and some app icons revery to the android logo and will not load. Rebooting and clearing cache in CWM some times fixes it, but it comes back again later... its really irritating, to say the least. Some times it causes the phone to reboot itself (not completely, CM9.1 just reloads without going back to the FXP screen), other times it makes the phone completely unresponsive with the back-light seemingly stuck off, and I have to pop the battery out to get things working again. Other times, I can play SuperGSNES for hours with no problems at all.
I have used OSMonitor to dig up some error messages, and I've found that these seem to pop up when the phone is going through one of its glitching spells:
Code:
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180500, nr 2, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180500
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180501, nr 1, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180501
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [WARNING] mmcblk0: retrying using single block read
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180494, nr 8, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180494
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180495, nr 7, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180495
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180496, nr 6, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180496
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180497, nr 5, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180497
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180498, nr 4, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180498
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180499, nr 3, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180499
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180500, nr 2, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180500
10/18/2012 13:58:50 [ERROR] mmc1: DMA channel flushed (0x80000004)
10/18/2012 13:58:50 [INFORMATION] mmc1: Controller has been reset
10/18/2012 13:58:50 [INFORMATION] mmc1: Worked around bug 1535304
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending status comand
10/18/2012 13:58:50 [ERROR] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
10/18/2012 13:58:50 [ERROR] mmcblk0: error -5 transferring data, sector 180501, nr 1, card status 0x0
10/18/2012 13:58:50 [ERROR] end_request: I/O error, dev mmcblk0, sector 180501
10/18/2012 13:58:50 [WARNING] mmc1: Starting deferred resume
10/18/2012 13:58:50 [WARNING] mmc1: Deferred resume completed
I filtered the log to show only mmc errors (related to the memory card from what I can gather) because I get other messages related to "msm_snddev_poweramp" constantly that clutter up the log.
Now, I thought the card was just bad, but I've tested it extensively on my computer and it has no bad clusters or defects of any kind, according to chkdsk or Minitool's diagnostics. I can copy to and read from it over and over with no problems. I've tried formatting it many times, in different programs (Secure Digital SDFormatter, Windows 7, EasyUS PM, Minitool Partition Wizard...) using FAT32 (the phone couldn't read it as EXT4 and I use Windows so that isn't ideal anyway), with and without the second Link2SD partition, and even if it works for a while, the phone will eventually start screwing up and spewing those mmc errors into dmesg.
I never had any of these problems with the stock ROM\kernel and the included 8gb class 2 microSD, and the problems don't seem to occur on the current setup with my spare G.Skill 4Gb Class 4 card.
Is it possible that the phone itself just plain does not work with certain memory cards, specifically UHS-1 class cards? Is it possible that a different Kernel or ROM may fix the problem?
I'm at a loss, and I'm hoping someone can help interpret those mmc messages or point me in a direction to narrow down the cause of this madness.
Thank you!
Click to expand...
Click to collapse
We had confirmed reports class 10 doesnt work on the xperia play. No changing the kernel doesnt make the difference. You need to know the difference between the read and write speeds of the sdcard because class 10 serves a different purpose (digital cameras/video recorder). Otherwise you've been gyped. You need class 6 and below sd cards.

chery2k said:
We had confirmed reports class 10 doesnt work on the xperia play. No changing the kernel doesnt make the difference. You need to know the difference between the read and write speeds of the sdcard because class 10 serves a different purpose (digital cameras/video recorder). Otherwise you've been gyped. You need class 6 and below sd cards.
Click to expand...
Click to collapse
UHS-1 is different than just standard Class 10. It is a new rating for high speed writing AND reading. Speed really should not be an issue with this card. I just ran CrystalDiskMark on the 32Gb Sandisk Ultra and the 4Gb GSkill Class 4 card and these are the results:
Sandisk Ultra 32Gb Class 10 UHS-1
-----------------------------------------------------------------------
CrystalDiskMark 3.0.1 (C) 2007-2010 hiyohiyo
Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]
Sequential Read : 20.047 MB/s
Sequential Write : 13.083 MB/s
Random Read 512KB : 20.483 MB/s
Random Write 512KB : 3.992 MB/s
Random Read 4KB (QD=1) : 3.176 MB/s [ 775.4 IOPS]
Random Write 4KB (QD=1) : 1.392 MB/s [ 339.8 IOPS]
Random Read 4KB (QD=32) : 3.463 MB/s [ 845.4 IOPS]
Random Write 4KB (QD=32) : 1.437 MB/s [ 350.8 IOPS]
Test : 100 MB [K: 1.3% (0.4/28.4 GB)] (x5)
Date : 2012/10/20 13:14:41
OS : Windows 7 SP1 [6.1 Build 7601] (x64)
G.SKill 4Gb Class 4
-----------------------------------------------------------------------
CrystalDiskMark 3.0.1 (C) 2007-2010 hiyohiyo
Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]
Sequential Read : 21.166 MB/s
Sequential Write : 7.057 MB/s
Random Read 512KB : 20.377 MB/s
Random Write 512KB : 0.901 MB/s
Random Read 4KB (QD=1) : 3.770 MB/s [ 920.4 IOPS]
Random Write 4KB (QD=1) : 0.231 MB/s [ 56.3 IOPS]
Random Read 4KB (QD=32) : 3.381 MB/s [ 825.4 IOPS]
Random Write 4KB (QD=32) : 0.220 MB/s [ 53.7 IOPS]
Test : 100 MB [K: 8.5% (321.8/3778.0 MB)] (x5)
Date : 2012/10/20 13:03:34
OS : Windows 7 SP1 [6.1 Build 7601] (x64)
Speed wise the cards are very similar, except that the Class 10 has significantly higher sequential AND random write speeds (random writes are very important for running apps from the card). The Class 4 is a bit faster with the 4kb reads (in MB\s and IOPS) with a queue depth of 1, but I would hope that a 25% difference in read speed in one situation wouldn't completely disable the Android OS and cause data corruption. Its still faster than the random read speed you'll find on many cards.
So, if it isn't a lack of random read\write speed, what is it? The Class 10 designation alone doesn't somehow make a card incompatible... its just a symbol on the package.
Is there any electrical difference between a faster card and a slower one that would make the faster one incompatible with this phone? Maybe its TOO fast, even though the UHS-1 cards are advertised as being made for tablets and smart phones?

Well, after seeing that the LuPuS+Ice Cream Pureness combo was stable with my 4Gb card, I put the 32Gb in and after a while I did get the mmc errors again while copying files. I really feel that I've tried everything at this point, aside from formatting the card with an EXT file system and making it unreadable on my computer.
I still don't understand why a card would be incompatible like this if the read and write speeds are good enough and the card has no physical problems.

Okay, I've made a discovery on another forum:
http://maemo.org/community/maemo-users/n900_microsd_card_i-o_errors_and_corruption/
This is exactly the problem I'm having, and they fixed it on an n900 by editing the DTO (data time-out I think) settings in one of the driver files for the sdcard controller. Basically, some drivers try to tell the memory controller to change this setting dynamically to determine the "optimal" setting for each SD card... where as, any card will apparently work with a standard setting anyway (maybe there is some performance or power benefit to adjusting this). The problem is, changing this setting dynamically is apparently problematic with many high speed cards, resulting in a timing problem and data corruption.
I guess its a fairly common problem with various handheld devices...
http://talk.maemo.org/archive/index.php/t-72789.html
My question is, does anyone have the means and the knowledge to see if the Xperia has a similar setting like this in its drivers? I only have a basic knowledge of programming and zero experience with linux kernel programming... so, if anyone finds a possible solution and attempts to make a fix for it, I'd be willing to test it. In the mean time, if I can find some kernel source files (doomkernel's CDMA source link is broken) I'll try digging around a bit myself. I have no idea how to compile though, even if I do find a similar setting.
Also, it'd be really nice to be able to post this topic in the development forum, but I'm still working my way up to 10 posts...

I can't believe it... I actually found the exact file mentioned in the first thread I linked above:
https://github.com/DooMLoRD/Xperia-...b/master/kernel/drivers/mmc/host/omap_hsmmc.c
The Xperia Play apparently uses the same driver (most likely a different version)... And it has the same exact section above that needs to be edited to remove the problematic DTO checks:
Original:
Code:
static void set_data_timeout(struct omap_hsmmc_host *host,
unsigned int timeout_ns,
unsigned int timeout_clks)
{
unsigned int timeout, cycle_ns;
uint32_t reg, clkd, dto = 0;
reg = OMAP_HSMMC_READ(host->base, SYSCTL);
clkd = (reg & CLKD_MASK) >> CLKD_SHIFT;
if (clkd == 0)
clkd = 1;
cycle_ns = 1000000000 / (clk_get_rate(host->fclk) / clkd);
timeout = timeout_ns / cycle_ns;
timeout += timeout_clks;
if (timeout) {
while ((timeout & 0x80000000) == 0) {
dto += 1;
timeout <<= 1;
}
dto = 31 - dto;
timeout <<= 1;
if (timeout && dto)
dto += 1;
if (dto >= 13)
dto -= 13;
else
dto = 0;
if (dto > 14)
dto = 14;
}
reg &= ~DTO_MASK;
reg |= dto << DTO_SHIFT;
OMAP_HSMMC_WRITE(host->base, SYSCTL, reg);
}
More info here:
http://talk.maemo.org/showthread.php?p=1000707#post1000707
Is it possible to make a module to patch an existing kernel for the xperia play? Specifically the r800x, since I'm willing to make mine a guinea pig. It seems like a very quick edit job... I've done it myself, I just don't have the means or knowledge to compile it into a useful file.
If anyone can do this I'd be very appreciative!

I just wanted to point out that Ive never experienced any lag or problems with my samsung class10 sd card, im using one of these in my r800x and my r800a ... not a single problem ... ever
http://www.samsung.com/ie/consumer/...ards/micro-sd/MB-MSBGA/EU?subsubtype=micro-sd

216Monster said:
I just wanted to point out that Ive never experienced any lag or problems with my samsung class10 sd card, im using one of these in my r800x and my r800a ... not a single problem ... ever
http://www.samsung.com/ie/consumer/...ards/micro-sd/MB-MSBGA/EU?subsubtype=micro-sd
Click to expand...
Click to collapse
Some people have suggested that the problem could arise from problematic metadata on a SD card, since this omap driver is actually trying to query the card to figure out what would be the best setting for it.
You're correct, it doesn't effect all class 10 cards, but it seems to be much more common with class 10 cards vs slower ones... for whatever reason.

mmcblk0 I/O error – possible hardware problem?

Hello, guys!
This morning I found my phone with black screen and not responding to power button. I pulled the battery out and tried to boot. The phone only showed the "Google" text on the black screen for several minutes (five, may be ten minutes) and did not respond to any buttons. At this point I pulled the battery for the second time and tried the recovery mode. The stock recovery booted after about a minute of "Google" screen. In stock recovery the only option I tried first time was "Wipe cache". It showed a static image of "work-in-progress" with static progress bar for several seconds and then returned to main recovery screen. I tried the "reboot" and received the black screen with no buttons working.
Pulled the battery and tried normal boot, which stuck on black "Google" stage.
Ok, I connected the phone to my laptop, and booted TWRP via fastboot, it took a little longer to boot, but at least I managed to "adb-shell" it and grab dmesg output. This is the relevant part (containing "mmc" word):
Code:
<6>[ 2.828399] mmc0: new high speed MMC card at address 0001
...
<6>[ 2.829101] mmcblk0: mmc0:0001 VYL00M 14.6 GiB
<6>[ 2.829345] mmcblk0boot0: mmc0:0001 VYL00M partition 1 512 KiB
<6>[ 2.829681] mmcblk0boot1: mmc0:0001 VYL00M partition 2 512 KiB
<6>[ 2.835021] Reprogramming LPDDR2 timings to 400000000 Hz
<3>[ 2.836090] Power Management for TI OMAP4.
<6>[ 2.836334] OMAP4 PM: Static dependency added between MPUSS and DUCATI <-> L4_PER/CFG and L3_1.
<6>[ 2.836517] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13
<4>[ 2.837432] sr_init: No PMIC hook to init smartreflex
<6>[ 2.837799] smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
<6>[ 2.838073] smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
<6>[ 2.838317] smartreflex smartreflex.2: omap_sr_probe: SmartReflex driver initialized
<6>[ 2.838592] sr_class1p5_driver_init: OMAP4460: add 10mV margin for class 1.5
<6>[ 2.838928] SmartReflex class 1.5 driver: initialized (86400000ms)
<6>[ 2.839569] mmcblk0boot1: unknown partition table
<6>[ 2.840728] [MODEM_IF] PA EVENT : reset =0, pa=1
<6>[ 2.840972] mmcblk0boot0: unknown partition table
...
<4>[ 3.851135] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
<4>[ 3.899353] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
<6>[ 3.915679] mmc1: new high speed SDIO card at address 0001
<4>[ 3.917633] F1 signature read @0x18000000=0x16844330
<4>[ 3.927154] DHD: dongle ram size is set to 294912(orig 294912)
...
<3>[ 7.677093] mmcblk0: timed out sending r/w cmd command, card status 0xe00
<3>[ 7.677276] mmcblk0: not retrying timeout
<3>[ 7.677581] end_request: I/O error, dev mmcblk0, sector 1495040
<3>[ 7.677764] Buffer I/O error on device mmcblk0p11, logical block 0
<4>[ 7.678100] lost page write due to I/O error on mmcblk0p11
<6>[ 7.678802] EXT4-fs (mmcblk0p11): recovery complete
<6>[ 7.679138] EXT4-fs (mmcblk0p11): mounted filesystem with ordered data mode. Opts: (null)
<3>[ 8.737213] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
<3>[ 8.737304] mmcblk0: command error, retrying timeout
<3>[ 8.737426] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
<3>[ 8.737548] mmcblk0: command error, retrying timeout
<3>[ 8.737701] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
<3>[ 8.737762] mmcblk0: command error, retrying timeout
<3>[ 8.737915] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
...
and a lot of I/O errors with mmcblk0 block device
Reading from /dev/block/mmcblk0 constantly fails, even the first sectors (dd if=/dev/block/mmcblk0 of=/dev/null).
I pulled the battery out, left the phone and rushed to the work.
With my little knowledge it looks like broken sdcard itself or sdcard controller. Does it make any sense? Is it possible to repair it easily? I realize I cannot simply replace sdcard, as it most likely soldered in the board, but how hard is it to replace if I have the equipment and spare parts?
Another question: as I can boot TWRP recovery via fastboot, is it theoretically possible to find and boot a custom kernel, which does not require internal storage at all, like some stripped kernel which works only in RAM, but still provides the basic functions like phone calling, wifi browsing and something like this?
Any help would be greatly appreciated!

Try restoring your phone to stock using ODIN
http://forum.xda-developers.com/showthread.php?t=1827685
I think the PIT file should repair your partition table if it's just a software problem

Thanks for the tip. I guess I will try odin methods only as as a last resort since it may void my warranty. I am still positive about sending my unit to the service center in January.
At the moment fastboot methods do not work if they try to actually write something. fastboot boot works pretty good.

Looks like a bad partition, ODIN back to factory wont void your warranty. All it does is reset your phone to the stock image, that's probably what they'll do when you send it in for warranty repair. Save yourself the time and trouble.

Bad blocks is something software won't fix. This is a hardware problem with the flash memory and it needs replaced.

I had something like this happen when I was formatting my /data partition in TWRP. I did a factory reset and it was like "wiping /data without wiping /data/media" and just to be on the safe side I wiped /data and it froze and when I got control back it said that it couldn't format it or anything so I ended up restoring the factory image and that fixed everything.

varet tviengt
Once again, just to be on the safe side, I will not try ODIN factory reset just yet. As it may be the hardware problem and I may end up with phone-triangle-computer state, in which case my warranty might be rejected like I messed something up myself blah-blah-blah.
The problem with the warranty is that I should go to my home, and I am now several thousands kilometers away from it on a vacation. So I will just wait for it.

I'm having the exact same problems for the last few weeks. Did you fix it? If so, how?

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

I have a GNexus 4.2.2 stock and I have reboot problem from the last week.
in the last_kmsg(attached) I read many references to mmc problems, for example
Code:
[ 5213.429595] mmcblk0: timed out sending r/w cmd command, card status 0x900
[ 5213.429779] mmcblk0: not retrying timeout
[ 5213.429901] end_request: I/O error, dev mmcblk0, sector 2450976
[ 5213.430084] end_request: I/O error, dev mmcblk0, sector 2450984
[ 5213.430175] end_request: I/O error, dev mmcblk0, sector 2450992
[ 5213.430328] end_request: I/O error, dev mmcblk0, sector 2451000
[ 5213.430450] end_request: I/O error, dev mmcblk0, sector 2451008
[ 5213.430603] end_request: I/O error, dev mmcblk0, sector 2451016
[ 5213.430694] end_request: I/O error, dev mmcblk0, sector 2451024
[ 5213.430847] end_request: I/O error, dev mmcblk0, sector 2451032
[ 5213.431091] Aborting journal on device mmcblk0p12-8.
I have already restore the Factory Images from Google developer, but I don't solve.
Is damage the memory or is a software problem?

up

Any news here? Since a few days I'm experiencing the same problem .

I have sane issue ! Any info for us ?
Inviato dal mio Galaxy Nexus usando Tapatalk 4

I am experiencing this problem too. Often apps crash when SQLite tries to write something to disk: Disk I/O error (code 1034).
I'm also getting random reboots and corrupted files.
This happens both with CM11-M2 and stock 4.3 ROM, so I don't think it's a software problem.
Do you think the internal storage is dying? Is there something I can do? Thanks!

Galaxy Nexus Super Slow. Can't Erase/Flash or ODIN.

Hey folks,
My GNex is super slow. Annoyingly slow that it'd take at least 2 mins for a touch event to get respond. The problem started after flashing a SlimKat Beta ROM.
I tried wiping, factory-reset, ODIN flash and many others. ODIN showed pass and still loads the old ROM. Lately, I found others having this same problem and everyone suggested installing lagfix(fstrim) app. The problem is I can't even get past by first screen. Getting the ADB to work is dreadful. For just one time, I could open my storage and I deleted every other file. After rebooting all the deleted-files-which-i-though-were-deleted reappeared.
Recovery/fastboot seems to work.
What can I do?

Try fastboot. But your emmc is fried probably.
Sent from my Nexus 10 using xda app-developers app

mrgnex said:
Try fastboot. But your emmc is fried probably.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Oh. Here In India, the Samsung Service Centers wont take GNex as this was not launched here.
I'm doomed. :crying:
Can I get my EMMC replaced from US?

wantsree said:
Oh. Here In India, the Samsung Service Centers wont take GNex as this was not launched here.
I'm doomed. :crying:
Can I get my EMMC replaced from US?
Click to expand...
Click to collapse
First try fastboot. I dont know 100% sure your emmc is fried.
Sent from my Nexus 10 using xda app-developers app

I could run this following commands. What do you make of this?
127|[email protected]:/ $ su
[email protected]:/ # dmesg | grep mmc0
dmesg | grep mmc0
1|[email protected]:/ # dmesg | grep mmc
dmesg | grep mmc
<3>[ 102.344421] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.344482] mmcblk0: command error, retrying timeout
<3>[ 102.345764] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.345855] mmcblk0: command error, retrying timeout
<3>[ 102.346282] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.346405] mmcblk0: command error, retrying timeout
<3>[ 102.346893] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.347015] mmcblk0: command error, retrying timeout
<3>[ 102.347595] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.347747] mmcblk0: command error, retrying timeout
<3>[ 102.348175] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.348297] mmcblk0: command error, retrying timeout
<3>[ 102.348785] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.348937] mmcblk0: command error, retrying timeout
<3>[ 102.349700] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.349761] mmcblk0: command error, retrying timeout
<3>[ 102.350250] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.350341] mmcblk0: command error, retrying timeout
<3>[ 102.350860] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.350921] mmcblk0: command error, retrying timeout
<3>[ 102.351470] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.351593] mmcblk0: command error, retrying timeout
<3>[ 102.352203] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.352325] mmcblk0: command error, retrying timeout
<3>[ 102.352844] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.352966] mmcblk0: command error, retrying timeout
<3>[ 102.353546] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.353668] mmcblk0: command error, retrying timeout
<3>[ 102.354095] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.354217] mmcblk0: command error, retrying timeout
<3>[ 102.354766] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.354858] mmcblk0: command error, retrying timeout
<3>[ 102.355438] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 102.355529] mmcblk0: command error, retrying timeout
<3>[ 105.539093] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.539154] mmcblk0: command error, retrying timeout
<3>[ 105.539916] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.540039] mmcblk0: command error, retrying timeout
<3>[ 105.540740] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.540893] mmcblk0: command error, retrying timeout
<3>[ 105.541442] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.541564] mmcblk0: command error, retrying timeout
<3>[ 105.542755] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.542907] mmcblk0: command error, retrying timeout
<3>[ 105.543792] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.543914] mmcblk0: command error, retrying timeout
<3>[ 105.545104] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.545196] mmcblk0: command error, retrying timeout
<3>[ 105.545715] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.545776] mmcblk0: command error, retrying timeout
<3>[ 105.546417] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.546478] mmcblk0: command error, retrying timeout
<3>[ 105.546905] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.547058] mmcblk0: command error, retrying timeout
<3>[ 105.547546] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.547668] mmcblk0: command error, retrying timeout
<3>[ 105.548187] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.548309] mmcblk0: command error, retrying timeout
<3>[ 105.548767] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.548889] mmcblk0: command error, retrying timeout
<3>[ 105.549377] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.549499] mmcblk0: command error, retrying timeout
<3>[ 105.550140] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.550201] mmcblk0: command error, retrying timeout
<3>[ 105.550720] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.550781] mmcblk0: command error, retrying timeout
<3>[ 105.551910] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.552001] mmcblk0: command error, retrying timeout
<3>[ 105.552947] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.553070] mmcblk0: command error, retrying timeout
<3>[ 105.553558] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.553680] mmcblk0: command error, retrying timeout
<3>[ 105.554138] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.554290] mmcblk0: command error, retrying timeout
<3>[ 105.554840] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.554992] mmcblk0: command error, retrying timeout
<3>[ 105.555389] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.555511] mmcblk0: command error, retrying timeout
<3>[ 105.556030] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.556121] mmcblk0: command error, retrying timeout
<3>[ 105.556671] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.556762] mmcblk0: command error, retrying timeout
<3>[ 105.557220] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.557281] mmcblk0: command error, retrying timeout
<3>[ 105.557769] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.557922] mmcblk0: command error, retrying timeout
<3>[ 105.558471] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.558624] mmcblk0: command error, retrying timeout
<3>[ 105.559051] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.559173] mmcblk0: command error, retrying timeout
<3>[ 105.559631] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.559783] mmcblk0: command error, retrying timeout
<3>[ 105.560302] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.560424] mmcblk0: command error, retrying timeout
<3>[ 105.560913] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.560974] mmcblk0: command error, retrying timeout
<3>[ 105.561523] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.561584] mmcblk0: command error, retrying timeout
<3>[ 105.562164] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.562255] mmcblk0: command error, retrying timeout
<3>[ 105.562652] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.562774] mmcblk0: command error, retrying timeout
<3>[ 105.563262] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.563385] mmcblk0: command error, retrying timeout
<3>[ 105.563934] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.564056] mmcblk0: command error, retrying timeout
<3>[ 105.564483] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.564605] mmcblk0: command error, retrying timeout
<3>[ 105.565093] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.565216] mmcblk0: command error, retrying timeout
<3>[ 105.566589] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.566650] mmcblk0: command error, retrying timeout
<3>[ 105.572906] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.572998] mmcblk0: command error, retrying timeout
<3>[ 105.573669] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.573730] mmcblk0: command error, retrying timeout
<3>[ 105.574218] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.574340] mmcblk0: command error, retrying timeout
<3>[ 105.575042] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.575164] mmcblk0: command error, retrying timeout
<3>[ 105.575958] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.576080] mmcblk0: command error, retrying timeout
<3>[ 105.576507] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.576660] mmcblk0: command error, retrying timeout
<3>[ 105.577117] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.577239] mmcblk0: command error, retrying timeout
<3>[ 105.578125] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.578186] mmcblk0: command error, retrying timeout
<3>[ 105.578704] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.578765] mmcblk0: command error, retrying timeout
<3>[ 105.579284] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.579376] mmcblk0: command error, retrying timeout
<3>[ 105.580139] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.580261] mmcblk0: command error, retrying timeout
<3>[ 105.580718] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.580841] mmcblk0: command error, retrying timeout
<3>[ 105.581298] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.581420] mmcblk0: command error, retrying timeout
<3>[ 105.582336] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.582458] mmcblk0: command error, retrying timeout
<3>[ 105.582885] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.583007] mmcblk0: command error, retrying timeout
<3>[ 105.583557] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.583648] mmcblk0: command error, retrying timeout
<3>[ 105.584533] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.584594] mmcblk0: command error, retrying timeout
<3>[ 105.585083] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.585144] mmcblk0: command error, retrying timeout
<3>[ 105.585632] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.585754] mmcblk0: command error, retrying timeout
<3>[ 105.587127] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.587249] mmcblk0: command error, retrying timeout
<3>[ 105.587707] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.587829] mmcblk0: command error, retrying timeout
<3>[ 105.588287] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.588409] mmcblk0: command error, retrying timeout
<3>[ 105.589263] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.589385] mmcblk0: command error, retrying timeout
<3>[ 105.589874] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.589965] mmcblk0: command error, retrying timeout
<3>[ 105.590484] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.590545] mmcblk0: command error, retrying timeout
<3>[ 105.591400] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.591491] mmcblk0: command error, retrying timeout
<3>[ 105.591918] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.592041] mmcblk0: command error, retrying timeout
<3>[ 105.592529] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.592651] mmcblk0: command error, retrying timeout
<3>[ 105.593536] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.593658] mmcblk0: command error, retrying timeout
<3>[ 105.594085] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.594207] mmcblk0: command error, retrying timeout
<3>[ 105.594696] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.594818] mmcblk0: command error, retrying timeout
<3>[ 105.596313] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.596405] mmcblk0: command error, retrying timeout
<3>[ 105.596893] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.596954] mmcblk0: command error, retrying timeout
<3>[ 105.597503] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.597564] mmcblk0: command error, retrying timeout
<3>[ 105.598510] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.598632] mmcblk0: command error, retrying timeout
<3>[ 105.599060] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.599182] mmcblk0: command error, retrying timeout
<3>[ 105.599670] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.599792] mmcblk0: command error, retrying timeout
<3>[ 105.600677] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.600830] mmcblk0: command error, retrying timeout
<3>[ 105.601257] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.601379] mmcblk0: command error, retrying timeout
<3>[ 105.601928] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.601989] mmcblk0: command error, retrying timeout
<3>[ 105.602996] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.603088] mmcblk0: command error, retrying timeout
<3>[ 105.603790] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.603881] mmcblk0: command error, retrying timeout
<3>[ 105.604400] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.604522] mmcblk0: command error, retrying timeout
<3>[ 105.605499] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.605651] mmcblk0: command error, retrying timeout
<3>[ 105.606079] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.606201] mmcblk0: command error, retrying timeout
<3>[ 105.606658] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.606811] mmcblk0: command error, retrying timeout
<3>[ 105.607666] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.607788] mmcblk0: command error, retrying timeout
<3>[ 105.608245] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.608337] mmcblk0: command error, retrying timeout
<3>[ 105.608886] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.608947] mmcblk0: command error, retrying timeout
<3>[ 105.609985] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 105.610076] mmcblk0: command error, retrying timeout
<3>[ 108.796203] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 108.796325] mmcblk0: command error, retrying timeout
<3>[ 108.796997] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 108.797119] mmcblk0: command error, retrying timeout
<3>[ 108.798675] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 108.798767] mmcblk0: command error, retrying timeout
<3>[ 108.799285] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 108.799346] mmcblk0: command error, retrying timeout
<3>[ 108.799896] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 108.799957] mmcblk0: command error, retrying timeout
<3>[ 108.802185] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 108.802307] mmcblk0: command error, retrying timeout
<3>[ 108.803771] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 108.803894] mmcblk0: command error, retrying timeout
<3>[ 108.804382] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 108.804504] mmcblk0: command error, retrying timeout
<3>[ 108.806274] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 108.806396] mmcblk0: command error, retrying timeout
<3>[ 108.963897] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 108.964019] mmcblk0: command error, retrying timeout
<3>[ 108.966644] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 108.966796] mmcblk0: command error, retrying timeout
<3>[ 108.968078] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 108.968170] mmcblk0: command error, retrying timeout
<3>[ 110.665710] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 110.665832] mmcblk0: command error, retrying timeout
<3>[ 110.666900] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 110.666992] mmcblk0: command error, retrying timeout
<3>[ 110.678405] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 110.678527] mmcblk0: command error, retrying timeout
<3>[ 117.779418] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 117.779571] mmcblk0: command error, retrying timeout
<3>[ 121.335144] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 121.335235] mmcblk0: command error, retrying timeout
<3>[ 121.336364] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 121.336425] mmcblk0: command error, retrying timeout
<3>[ 121.686676] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 121.686737] mmcblk0: command error, retrying timeout
<3>[ 121.718505] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 121.718597] mmcblk0: command error, retrying timeout
<3>[ 121.720275] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 121.720397] mmcblk0: command error, retrying timeout
<3>[ 121.727844] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 121.727966] mmcblk0: command error, retrying timeout
<3>[ 122.383178] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 122.383300] mmcblk0: command error, retrying timeout
<3>[ 122.384033] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 122.384185] mmcblk0: command error, retrying timeout
<3>[ 125.931274] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 125.931365] mmcblk0: command error, retrying timeout
<3>[ 125.931793] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 125.931884] mmcblk0: command error, retrying timeout
<3>[ 125.965270] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 125.965332] mmcblk0: command error, retrying timeout
<3>[ 125.966888] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 125.967041] mmcblk0: command error, retrying timeout
<3>[ 125.971252] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 125.971405] mmcblk0: command error, retrying timeout
<3>[ 125.971984] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 125.972106] mmcblk0: command error, retrying timeout
<3>[ 129.545532] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 129.545654] mmcblk0: command error, retrying timeout
<3>[ 133.096038] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 133.096130] mmcblk0: command error, retrying timeout
<3>[ 136.643981] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 136.644134] mmcblk0: command error, retrying timeout
<3>[ 140.194000] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 140.194122] mmcblk0: command error, retrying timeout
<3>[ 140.194763] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 140.194946] mmcblk0: command error, retrying timeout
<3>[ 140.196258] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 140.196411] mmcblk0: command error, retrying timeout
<3>[ 140.197540] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 140.197692] mmcblk0: command error, retrying timeout
<3>[ 140.202514] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 140.202636] mmcblk0: command error, retrying timeout
<3>[ 143.745666] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 143.745727] mmcblk0: command error, retrying timeout
<3>[ 143.746551] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 143.746612] mmcblk0: command error, retrying timeout
<3>[ 143.752288] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 143.752441] mmcblk0: command error, retrying timeout
<3>[ 147.293365] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.293487] mmcblk0: command error, retrying timeout
<3>[ 147.294006] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.294097] mmcblk0: command error, retrying timeout
<3>[ 147.297424] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.297546] mmcblk0: command error, retrying timeout
<3>[ 147.299133] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.299255] mmcblk0: command error, retrying timeout
<3>[ 147.300079] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.300201] mmcblk0: command error, retrying timeout
<3>[ 147.385742] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.385803] mmcblk0: command error, retrying timeout
<3>[ 147.395599] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.395660] mmcblk0: command error, retrying timeout
<3>[ 147.396514] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.396667] mmcblk0: command error, retrying timeout
<3>[ 147.425567] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.425659] mmcblk0: command error, retrying timeout
<3>[ 147.425994] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.426116] mmcblk0: command error, retrying timeout
<3>[ 147.427062] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.427154] mmcblk0: command error, retrying timeout
<3>[ 147.433166] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.433288] mmcblk0: command error, retrying timeout
<3>[ 147.457763] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.457885] mmcblk0: command error, retrying timeout
<3>[ 147.458770] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.458831] mmcblk0: command error, retrying timeout
<3>[ 147.459533] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.459594] mmcblk0: command error, retrying timeout
<3>[ 147.486785] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.486907] mmcblk0: command error, retrying timeout
<3>[ 147.487945] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.488067] mmcblk0: command error, retrying timeout
<3>[ 147.514129] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.514251] mmcblk0: command error, retrying timeout
<3>[ 147.514801] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.514892] mmcblk0: command error, retrying timeout
<3>[ 147.515777] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.515869] mmcblk0: command error, retrying timeout
<3>[ 147.516906] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.517028] mmcblk0: command error, retrying timeout
<3>[ 147.743957] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.744018] mmcblk0: command error, retrying timeout
<3>[ 147.758270] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 147.758361] mmcblk0: command error, retrying timeout
<3>[ 148.025939] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 148.026062] mmcblk0: command error, retrying timeout
<3>[ 148.027709] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 148.027832] mmcblk0: command error, retrying timeout
<3>[ 148.028594] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 148.028747] mmcblk0: command error, retrying timeout
<3>[ 151.594024] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 151.594177] mmcblk0: command error, retrying timeout
<3>[ 151.595672] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 151.595794] mmcblk0: command error, retrying timeout
<3>[ 151.597137] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 151.597259] mmcblk0: command error, retrying timeout
<5>[ 151.860961] type=1400 audit(1398533598.879:4): avc: denied { getattr } for pid=903 comm="twitter.android" path="/data/app" dev=mmcblk0p12 ino=773681 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:apk_data_file:s0 tclass=dir
<3>[ 151.952209] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 151.952301] mmcblk0: command error, retrying timeout
<3>[ 151.958343] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 151.958435] mmcblk0: command error, retrying timeout
<3>[ 151.959808] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 151.959930] mmcblk0: command error, retrying timeout
<3>[ 152.703399] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 152.703521] mmcblk0: command error, retrying timeout
<3>[ 152.705718] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 152.705871] mmcblk0: command error, retrying timeout
<3>[ 152.707275] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 152.707397] mmcblk0: command error, retrying timeout
<3>[ 156.512603] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 156.512725] mmcblk0: command error, retrying timeout
<3>[ 156.513214] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 156.513336] mmcblk0: command error, retrying timeout
<3>[ 156.514556] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 156.514617] mmcblk0: command error, retrying timeout
<3>[ 156.515411] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 156.515502] mmcblk0: command error, retrying timeout
<3>[ 160.255981] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 160.256103] mmcblk0: command error, retrying timeout
<3>[ 163.801513] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 163.801605] mmcblk0: command error, retrying timeout
<3>[ 163.804534] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 163.804595] mmcblk0: command error, retrying timeout
<3>[ 163.812561] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 163.812683] mmcblk0: command error, retrying timeout
<3>[ 163.821899] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 163.822021] mmcblk0: command error, retrying timeout
<3>[ 163.824401] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 163.824523] mmcblk0: command error, retrying timeout
<3>[ 163.847442] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 163.847564] mmcblk0: command error, retrying timeout
<3>[ 163.855285] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
.....
Full LOG here :
http://pastebin.com/9VRqRez8

mrgnex said:
First try fastboot. I dont know 100% sure your emmc is fried.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I tried erasing userdata, cache, system, recovery using fastboot. Nothing seems to work . Also tried flashing a new ROM. Is there anything else I can do with fastboot?

wantsree said:
I tried erasing userdata, cache, system, recovery using fastboot. Nothing seems to work . Also tried flashing a new ROM. Is there anything else I can do with fastboot?
Click to expand...
Click to collapse
get into fastboot lock the bootloader and then unlock it which pretty much clears everything then flash a factory android 4.3 image...
startover and see if it works...btw i know the pain to get gnex repaired in india

Develop Bugs

welcome