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.
Related
Hi,
a couple times a week my phone seems to freeze when I push the powerbutton. The hardware buttons light up, but the screen remains black. I always have to pull the battery, after that it works again.
I finally was near a pc when it happened and managed to make a dmesg log. This was taken while the phone wasn't responding. I just plugged it in and used adb to get a log. Here's the interesting part (at least I think it is):
Code:
<6>[ 5433.007232] bravo_ts_power: power 0
<7>[ 5433.007507] __capella_cm3602_power: Turn the capella_cm3602 power off
<6>[ 5433.008026] lcdc_suspend: suspending
<6>[ 5433.008331] [R] early_suspend: sync
<6>[ 5433.033782] active wake lock PowerManagerService
<6>[ 5433.033905] active wake lock SMD_DATA5, time left 21
<6>[ 5433.034149] active wake lock SMD_DS, time left 41
<6>[ 5433.034332] [R] early_suspend end
<3>[ 5438.615905] mmc1: Data CRC error
<3>[ 5438.616729] msmsdcc_data_err: opcode 0x00000019
<3>[ 5438.617156] msmsdcc_data_err: blksz 512, blocks 5
<3>[ 5438.618194] mmcblk0: error -84 transferring data, sector 1668966, nr 5, card status 0xf00
<3>[ 5438.620758] mmc1: Data timeout
<3>[ 5438.621612] end_request: I/O error, dev mmcblk0, sector 1668966
<3>[ 5438.622070] Buffer I/O error on device mmcblk0p1, logical block 1668965
<4>[ 5438.622833] lost page write due to I/O error on mmcblk0p1
<3>[ 5438.623291] end_request: I/O error, dev mmcblk0, sector 1668967
<3>[ 5438.624053] Buffer I/O error on device mmcblk0p1, logical block 1668966
<4>[ 5438.624511] lost page write due to I/O error on mmcblk0p1
<3>[ 5438.625305] end_request: I/O error, dev mmcblk0, sector 1668968
<3>[ 5438.625762] Buffer I/O error on device mmcblk0p1, logical block 1668967
<4>[ 5438.626525] lost page write due to I/O error on mmcblk0p1
<3>[ 5438.626983] end_request: I/O error, dev mmcblk0, sector 1668969
<3>[ 5438.627746] Buffer I/O error on device mmcblk0p1, logical block 1668968
<4>[ 5438.628173] lost page write due to I/O error on mmcblk0p1
<3>[ 5438.628967] end_request: I/O error, dev mmcblk0, sector 1668970
<3>[ 5438.629394] Buffer I/O error on device mmcblk0p1, logical block 1668969
<4>[ 5438.630187] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.042205] mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3>[ 5443.043090] mmc1: Data timeout
<3>[ 5443.043884] end_request: I/O error, dev mmcblk0, sector 1669055
<3>[ 5443.044311] Buffer I/O error on device mmcblk0p1, logical block 1669054
<4>[ 5443.045104] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.045562] end_request: I/O error, dev mmcblk0, sector 1669056
<3>[ 5443.046325] Buffer I/O error on device mmcblk0p1, logical block 1669055
<4>[ 5443.046752] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.047546] end_request: I/O error, dev mmcblk0, sector 1669057
<3>[ 5443.047973] Buffer I/O error on device mmcblk0p1, logical block 1669056
<4>[ 5443.048736] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.049194] end_request: I/O error, dev mmcblk0, sector 1669058
<3>[ 5443.049987] Buffer I/O error on device mmcblk0p1, logical block 1669057
<4>[ 5443.050415] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.051208] end_request: I/O error, dev mmcblk0, sector 1669059
<3>[ 5443.051635] end_request: I/O error, dev mmcblk0, sector 1669067
<3>[ 5443.052429] end_request: I/O error, dev mmcblk0, sector 1669075
<3>[ 5443.052856] end_request: I/O error, dev mmcblk0, sector 1669083
<3>[ 5443.053649] end_request: I/O error, dev mmcblk0, sector 1669091
<3>[ 5443.054077] end_request: I/O error, dev mmcblk0, sector 1669099
<3>[ 5443.054870] end_request: I/O error, dev mmcblk0, sector 1669107
<3>[ 5443.055664] end_request: I/O error, dev mmcblk0, sector 1669115
<3>[ 5443.056091] end_request: I/O error, dev mmcblk0, sector 1669123
<3>[ 5443.056884] end_request: I/O error, dev mmcblk0, sector 1669131
<3>[ 5443.057312] end_request: I/O error, dev mmcblk0, sector 1669139
<3>[ 5443.058105] end_request: I/O error, dev mmcblk0, sector 1669147
<3>[ 5443.058563] end_request: I/O error, dev mmcblk0, sector 1669155
<3>[ 5443.059326] end_request: I/O error, dev mmcblk0, sector 1669163
<3>[ 5443.059783] end_request: I/O error, dev mmcblk0, sector 1669171
<3>[ 5443.060546] end_request: I/O error, dev mmcblk0, sector 1669179
<3>[ 5443.066314] mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3>[ 5443.067199] mmc1: Data timeout
<3>[ 5443.067626] end_request: I/O error, dev mmcblk0, sector 2112723
<3>[ 5443.068420] Buffer I/O error on device mmcblk0p1, logical block 2112722
<4>[ 5443.068847] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.074676] mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3>[ 5443.075653] mmc1: Data timeout
<3>[ 5443.076110] end_request: I/O error, dev mmcblk0, sector 2
<3>[ 5443.081573] mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3>[ 5443.082427] mmc1: Data timeout
<3>[ 5443.082855] end_request: I/O error, dev mmcblk0, sector 833
<3>[ 5443.088745] mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3>[ 5443.089599] mmc1: Data timeout
<3>[ 5443.090026] end_request: I/O error, dev mmcblk0, sector 15594
<3>[ 5443.483581] mmc1: Data CRC error
<3>[ 5443.484374] msmsdcc_data_err: opcode 0x00000011
<3>[ 5443.484802] msmsdcc_data_err: blksz 512, blocks 1
<3>[ 5443.485748] mmcblk0: error -84 transferring data, sector 833, nr 1, card status 0xb00
<3>[ 5443.486389] end_request: I/O error, dev mmcblk0, sector 833
<3>[ 5443.487609] FAT: FAT read failed (blocknr 832)
<3>[ 5443.488616] mmc1: DMA channel flushed (0x80000004)
<3>[ 5443.489410] Flush data: 0000c003 3b18e000 00000000 00400040 00050004 00004003
<6>[ 5480.704193] batt: 95%, 4030 mV, -119 mA (-215 avg), 23.6 C, 1275 mAh
<6>[ 5530.876739] batt: 95%, 4030 mV, -69 mA (-82 avg), 23.6 C, 1273 mAh
<6>[ 5563.668518] gpio_keys_scan_keys: key 1-74, 0 (94) changed to 1
<6>[ 5563.673858] request_suspend_state: wakeup (3->0) at 5555550724239 (2010-12-28 12:24:48.362411743 UTC)
<6>[ 5563.674713] [R] late_resume start
<6>[ 5563.675201] lcdc_resume: resuming
<6>[ 5563.675628] samsung_oled_panel_init: +()
<6>[ 5563.676788] samsung_oled_panel_init: -()
<6>[ 5563.677368] msmfb: ready, waiting for full update
<7>[ 5563.678131] __capella_cm3602_power: Turn the capella_cm3602 power on
<6>[ 5563.678955] bravo_ts_power: power 1
<6>[ 5563.680053] lightsensor_ioctl set value = 1
<6>[ 5563.680816] lightsensor_enable
After that I reformatted my SDcard, wiped everything and did a fresh install of CM instead of Oxygen RC4 which I was using before.
Today I was downloading a few apps from the market, when suddenly the downloads disappeared from the notification bar. I used quick system info to look at the logs (again only a small part, i still have the rest if the full log contains more useful information):
Code:
<3> [23578.803039] : mmc1: Data CRC error
<3> [23578.803466] : msmsdcc_data_err: opcode 0x00000019
<3> [23578.804229] : msmsdcc_data_err: blksz 512, blocks 49
<3> [23578.804657] : mmc1: DMA channel flushed (0x80000004)
<3> [23578.805084] : Flush data: 0000c003 3b252030 00000000 00400040 00170015 00008003
<3> [23578.810241] : mmcblk0: error -84 transferring data, sector 2556870, nr 49, card status 0x900
<3> [23578.811096] : mmc1: Data timeout
<3> [23578.811889] : end_request: I/O error, dev mmcblk0, sector 2556870
<3> [23578.812652] : end_request: I/O error, dev mmcblk0, sector 2556878
<3> [23578.813079] : end_request: I/O error, dev mmcblk0, sector 2556886
<3> [23578.813812] : end_request: I/O error, dev mmcblk0, sector 2556894
<3> [23578.814209] : end_request: I/O error, dev mmcblk0, sector 2556902
<3> [23578.814972] : end_request: I/O error, dev mmcblk0, sector 2556910
<3> [23578.815368] : end_request: I/O error, dev mmcblk0, sector 2556918
<3> [23578.821869] : mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3> [23578.823883] : mmc1: Data timeout
<3> [23578.824524] : end_request: I/O error, dev mmcblk0, sector 2556934
<3> [23578.830535] : mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3> [23578.832946] : mmc1: Data timeout
<3> [23578.833801] : end_request: I/O error, dev mmcblk0, sector 2049
<3> [23578.834564] : Buffer I/O error on device mmcblk0p1, logical block 1
<4> [23578.834991] : lost page write due to I/O error on mmcblk0p1
<3> [23578.844360] : mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3> [23578.844635] : mmc1: Data timeout
<3> [23578.844757] : end_request: I/O error, dev mmcblk0, sector 4515
<3> [23578.844879] : Buffer I/O error on device mmcblk0p1, logical block 2467
<4> [23578.845092] : lost page write due to I/O error on mmcblk0p1
<3> [23579.089599] : mmc1: Data CRC error
<3> [23579.090057] : msmsdcc_data_err: opcode 0x00000011
<3> [23579.090454] : msmsdcc_data_err: blksz 512, blocks 1
<3> [23579.091919] : mmcblk0: error -84 transferring data, sector 4515, nr 1, card status 0xb00
<3> [23579.092315] : end_request: I/O error, dev mmcblk0, sector 4515
<3> [23579.093231] : FAT: FAT read failed (blocknr 2467)
<3> [23579.098968] : mmcblk0: error -110 sending read/write command, response 0xb00, card status 0x400b00
<3> [23579.105072] : end_request: I/O error, dev mmcblk0, sector 63598
<3> [23579.105529] : Buffer I/O error on device mmcblk0p1, logical block 61550
<4> [23579.105926] : lost page write due to I/O error on mmcblk0p1
<3> [23579.582916] : FAT: Filesystem error (dev mmcblk0p1)
<3> [23579.583038] : fat_get_cluster: invalid cluster chain (i_pos 984821)
<3> [23579.583465] : FAT: Filesystem has been set read-only
<6> [23585.658355] : wake lock SMD_DATA5, expired
<7> [23585.663910] : save exit: isCheckpointed 1
<6> [23585.666900] : suspend: enter suspend
<6> [23585.667297] : PM: Syncing filesystems ... done.
<4> [23585.670532] : Freezing user space processes ... (elapsed 0.02 seconds) done.
<4> [23585.699371] : Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
<6> [23585.749786] : PM: suspend of devices complete after 28.841 msecs
<6> [23585.750854] : power_suspend_late return 0
<6> [23585.751281] : PM: late suspend of devices complete after 1.036 msecs
<6> [23585.751281] : clocks on: uart_clk
<6> [23585.751281] : [R] suspend end
<6> [23585.751281] : [R] resume start
<6> [23585.751678] : PM: early resume of devices complete after 0.396 msecs
<6> [23585.757965] : wakeup wake lock: SMD_RPCCALL
<6> [23585.764862] : PM: resume of devices complete after 12.439 msecs
<4> [23585.766082] : Restarting tasks ... done.
<6> [23585.783905] : suspend: exit suspend, ret = 0 (2010-12-29 13:37:55.798841765 UTC)
<6> [23585.784912] : active wake lock ds2784-battery
<6> [23585.785339] : suspend: abort suspend
Could the freeze be the result of having apps installed on the SD when the error occurred?
The strange thing is that I got a new SD card for Christmas, and I have had (seemingly) the same freezes before. I never managed to get a log before, since i was never near a computer.
I already tried reformatting the card a few times, but that didn't seem to help.
Does anybody know a solution? Is it SD card related, or can it be caused by something else entirely?
Thanks
Does anyone have know if this is a problem with my SD card?
I find it odd that I also had the lockscreen freezing on my other SD card, I don't have it with me at the moment, so I can't compare the logs.
Is it also possible that the internal memory is corrupt? (Which would be a lot worse i guess )
Are you overclocking? If your min cpu speed is lower that 245mhz sometimes you get issues with the device waking.
Sent from my HTC Desire using Tapatalk
No, I'm not over/underclocking.
The second log was taken after several failed downloads of updates from the market. It showed the exact same error as the one were the lockscreen froze, but the phone functioned normally. Except for the downloads that failed of course.
I think the freezing is the result of an app or essential file on the SD card that can't be reached. Is that possible?
I have the same problem with the screen not waking. Did you find a solution?
Exact same problem..!!
Hey,
I have the exact same problem! I'm running a mildwild rom, with cm7r2 hboot, and 4ext recovery.. everything should be OK, but it's not..
I also think that it's the SD card that's dying.. gonna buy a new one tomorrow, and see if the problem goes away.. I'll post here, as soon as I find something out..!
- H
Is it a class 10 card? Also, maybe the I/O schedule may cause it.
What settings do u have set for it?
SaySayonara said:
Is it a class 10 card? Also, maybe the I/O schedule may cause it.
What settings do u have set for it?
Click to expand...
Click to collapse
Hey,
No I don't think it is.. but I don't think that should matter much, since I just got this phone, and had an old SD-card lying around.. so I rooted it, partitioned it, etc., but these malfunctions appeared almost immediately.. and I'm pretty sure the SD was OK when I put it in.. isn't class 10 usually only recommended for demanding a2sd setup-ups, that run over long periods of time..? I find it extremly suspicious that an SD card, even below class 6, would almost instantaneously die upon being put into use.. ?
However, now I've played around with it some more, and I'm almost certain now that it's the SD card that has gone broken.. because if I clear the data and cache of both google play and google framework services apks, and then boot into recovery and choose "tools" --> "check filesystem" --> sdcard --> repair sdcard (it doesn't work EVERY time, which also makes me suspect the Sd card...!!!!) , and then reboot, the SD card will work -- for a while... Like, I'll install 5-7 apps from google play, and then the same s**t all over again..
Gonna try it out with the same setup, but a brand new class 10 SD tomorrow, and report back..!
- H
I bought Sandisk Extreme 32GB
What partitioning tool did u use? I've seen many ppl saying that 4ext is the best. To be Frank I never had any issues with it.
SaySayonara said:
I bought Sandisk Extreme 32GB
What partitioning tool did u use? I've seen many ppl saying that 4ext is the best. To be Frank I never had any issues with it.
Click to expand...
Click to collapse
Yeah, I also used 4ext.. worked like a charm!
HAhaha, LOL - I was just looking at what card I'm gonna get tomorrow, and it looks like it's gonna be the same as yours..!!
- H
You're in for a treat my friend
I was very surprised by the difference.
All right!
The mystery is solved! Just tested it out with a new SanDisk class 10 16GB SD card.. everything works just fine.. partitioned it in 4ext, installed MildWild AOSP GB rom, installed a s**tload of apps, and everything works just fine.. the a2sd script is working as it should, both the rom install and apps install went smoothly. Besides changing the SD card, I changed nothing; same HBOOT, same 4ext, same everything.. So I guess it was the SD card that was fu***n things up..!
Cheers everybody!
- H
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.
Hey everyone,
I am having a strange problem with my sd-ext (ext4) partition for some time now.
The ROM I am using is ICS for Desire by Sandvold (Amarullz and a2sd), but I don't know whether this is strictly ROM related or not.
I have been getting some mass FCs over and over again, across different versions flashed after full wipes.
Today I found out that the problem is that the sd-ext partition is not properly mounted (read-only), but here is the weird part: it is properly mounted (read-write) using the recovery and is also properly mounted before I unlock the sim-card.
When I unlock the sim-card or otherwise change the connectivity (WLAN, mobile data, airplane mode) it remounts sd-ext as read-only.
I have already tried reformatting and repartioning the sd-card.
Any idea why the system is doing that or how I can prevent that from happening?
Thanks
\Update1:
Here is a part of dmesg, showing the error when I unlock the sim-card after a fresh reboot:
Code:
<6>[ 182.512451] active wake lock PowerManagerService
<6>[ 182.512481] active wake lock vbus_present
<6>[ 182.512481] active wake lock SMD_DS, time left 35
<6>[ 182.512481] [R] early_suspend end
<6>[ 190.756866] batt: 74%, 3884 mV, 290 mA (210 avg), 29.8 C, 1008 mAh
<3>[ 191.665740] mmc1: Data CRC error
<3>[ 191.665954] msmsdcc_data_err: opcode 0x00000019
<3>[ 191.666168] msmsdcc_data_err: blksz 512, blocks 16
<3>[ 191.666595] mmc1: DMA channel flushed (0x80000004)
<3>[ 191.666839] Flush data: 0000c003 3b2d8018 00000000 00400040 00370035 00008003
<6>[ 191.667266] mmc1: Controller has been re-initialiazed
<3>[ 191.672515] mmcblk0: error -84 transferring data, sector 6710376, nr 16, card status 0x900
<3>[ 191.672973] mmc1: Data timeout
<6>[ 191.673217] mmc1: Controller has been re-initialiazed
<3>[ 191.673797] end_request: I/O error, dev mmcblk0, sector 6710376
<3>[ 191.674041] end_request: I/O error, dev mmcblk0, sector 6710384
<3>[ 191.679138] Aborting journal on device mmcblk0p2-8.
<0>[ 191.687255] journal commit I/O error
<2>[ 191.726745] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:276: Detected aborted journal
<2>[ 191.727478] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
<3>[ 191.984802] binder: 1268: binder_alloc_buf, no vma
<6>[ 191.985046] binder: 206:339 transaction failed 29201, size 4-0
<6>[ 191.985412] binder: send failed reply for transaction 79996 to 1268:1268
The weird thing is that I have been running the phone without any problem in airplane mode + WLAN for a whole day, until I tried to reactivate mobile connection again and do some tests with it.
It seems that the system only has a problem with the journal when it uses the mobile connection.
\Update2:
Here the dmesg message before I unlock the sim-card. No error message for sd-ext:
Code:
<6>[ 13.084991] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
4EXT is also unable to find any errors with the sd-ext partition (I have used the recovery to format and partition the sd-card).
\Update3:
Ok I just reformatted and repartitioned the sdcard again using gparted and reflashed the ROM with a full wipe.
I am getting the same error again.
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!
I'm using the CyanoMod007 form michaelm_007. http://forum.xda-developers.com/showthread.php?t=2213033
At the Last Page the user newsoup said the max. sd-ext Patition Limit is 1.5 GB
I've seen it in other ROMs that limit. But honestly, I've never understood why this limitation exists. Also Ext2 could already manage 2 TB. So why does this limit?
I would like to respond directly to the post but I have not yet, unfortunately my 10 post.
If it's just a driver issue then I would also like to fixed it I have some experience with Linux kernel programming.
I would appreciate if someone would tell me this limit
regards
Werner2005
Theres no actual limit...its more of a recommendation. Technically you can make it as big as the file system allow you to, but the reason why most people dont recommend an ext partition >1.5gb is because it will cause issues such as slow downs, crashes, etc.
Chromium_ said:
Theres no actual limit...its more of a recommendation. Technically you can make it as big as the file system allow you to, but the reason why most people dont recommend an ext partition >1.5gb is because it will cause issues such as slow downs, crashes, etc.
Click to expand...
Click to collapse
So just as describe in the thread I have a similar layout. 32 GB SD card and 4 GB sd-ext. I just thought I'm so does not matter enough memory on the SD.
The only problem is I read here repeatedly that how you say it, crashed, etc. are.
I would just interested why these crashes happen.
For example, I observed, at a Such crashes:
Code:
<3>[50587.562805] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
<3>[50587.562835] mmcblk0: error -5 transferring data, sector 60169220, nr 69, card status 0x0
<3>[50587.562866] end_request: I/O error, dev mmcblk0, sector 60169220
<3>[50587.563323] mmc1: DMA channel flushed (0x80000004)
<3>[50587.563323] Flush data: 0000c003 3b35f000 00000000 00400040 00080008 00000003
<6>[50587.563385] mmc1: Controller has been re-initialiazed
<3>[50587.569061] mmcblk0: error -110 sending status command
<3>[50587.569091] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
<3>[50587.569122] mmcblk0: error -5 transferring data, sector 60169221, nr 68, card status 0x0
<3>[50587.569122] end_request: I/O error, dev mmcblk0, sector 60169221
<3>[50587.569580] mmc1: DMA channel flushed (0x80000004)
<3>[50587.569610] Flush data: 0000c003 3b35f000 00000000 00400040 00080008 00000003
<6>[50587.569671] mmc1: Controller has been re-initialiazed
<3>[50587.575286] mmcblk0: error -110 sending status command
<3>[50587.575286] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
<3>[50587.575317] mmcblk0: error -5 transferring data, sector 60169222, nr 67, card status 0x0
<3>[50587.575347] end_request: I/O error, dev mmcblk0, sector 60169222
The rest always looks the same...
It is easy intrsannt it seems as the kernel'd send data to the SD card Contoller. But the stop responding ...
Unfortunately, I've been writing the log to the late Cache was not enough to Figuring out what the first error.
use int2ext...
sohail.patel said:
use int2ext...
Click to expand...
Click to collapse
Take this as a piece of advice
I know you are trying to get 10 posts by being helpful here and there, but posting short answers in old threads doesn't really help anyone. Try referring to the newer threads. You could actually help someone that needs it