[Galaxy S III Q&A, Help & Troubleshooting] tehjack:
Hey guys,

I just need your opinion or some ideas.

I was wondering why my galaxy s3 was locking up, so I took a look into the kernel output.

So the malfunction is: Phone locks up, no reaction to any key pressing and so on, but I can reboot it by holding the power button.

By having a ssh connection to my phone I can see that when the phone "locks" up the kernel is still living. So there is no kernel panic or what so ever.

After that I got curious, will the lock up go away? And yes, it did. After 30 minutes or so. And after that the phone was working without problems again. Here is the relevant log output of the kernel (/proc/kmesg):

<3>[26695.166202] c0 mmc0: Timeout waiting for hardware interrupt.
<7>[26695.166317] c0 mshci: ============== REGISTER DUMP ==============
<7>[26695.166440] c0 mshci: MSHCI_CTRL: 0x00000010
<7>[26695.166534] c0 mshci: MSHCI_PWREN: 0x00000001
<7>[26695.166628] c0 mshci: MSHCI_CLKDIV: 0x00000001
<7>[26695.166723] c0 mshci: MSHCI_CLKSRC: 0x00000000
<7>[26695.166814] c0 mshci: MSHCI_CLKENA: 0x00000000
<7>[26695.166907] c0 mshci: MSHCI_TMOUT: 0xffffffff
<7>[26695.167004] c0 mshci: MSHCI_CTYPE: 0x00010000
<7>[26695.167100] c0 mshci: MSHCI_BLKSIZ: 0x00000200
<7>[26695.167192] c0 mshci: MSHCI_BYTCNT: 0x0000f000
<7>[26695.167288] c0 mshci: MSHCI_INTMSK: 0x0000bfce
<7>[26695.167380] c0 mshci: MSHCI_CMDARG: 0x00010000
<7>[26695.167472] c0 mshci: MSHCI_CMD: 0x80202000
<7>[26695.167574] c0 mshci: MSHCI_MINTSTS: 0x00000000
<7>[26695.167666] c0 mshci: MSHCI_RINTSTS: 0x00000030
<7>[26695.167757] c0 mshci: MSHCI_STATUS: 0x01fe6b01
<7>[26695.167860] c0 mshci: MSHCI_FIFOTH: 0x503f0040
<7>[26695.167954] c0 mshci: MSHCI_CDETECT: 0x00000001
<7>[26695.168045] c0 mshci: MSHCI_WRTPRT: 0x00000001
<7>[26695.168145] c0 mshci: MSHCI_GPIO: 0x00000000
<7>[26695.168238] c0 mshci: MSHCI_TCBCNT: 0x00007800
<7>[26695.168331] c0 mshci: MSHCI_TBBCNT: 0x0000f0d8
<7>[26695.168432] c0 mshci: MSHCI_DEBNCE: 0x000fffff
<7>[26695.168523] c0 mshci: MSHCI_USRID: 0xffffffff
<7>[26695.168615] c0 mshci: MSHCI_VERID: 0x5342240a
<7>[26695.168717] c0 mshci: MSHCI_HCON: 0x00e424c1
<7>[26695.168811] c0 mshci: MSHCI_UHS_REG: 0x00010000
<7>[26695.168904] c0 mshci: MSHCI_BMOD: 0x00000582
<7>[26695.169000] c0 mshci: MSHCI_PLDMND: 0x00000000
<7>[26695.169090] c0 mshci: MSHCI_DBADDR: 0x6bee0000
<7>[26695.169182] c0 mshci: MSHCI_IDSTS: 0x00000000
<7>[26695.169282] c0 mshci: MSHCI_IDINTEN: 0x00000000
<7>[26695.169374] c0 mshci: MSHCI_DSCADDR: 0x6bee00e0
<7>[26695.169465] c0 mshci: MSHCI_BUFADDR: 0x00000000
<7>[26695.169564] c0 mshci: MSHCI_WAKEUPCON: 0x00000000
<7>[26695.169658] c0 mshci: MSHCI_CLOCKCON: 0x00000000
<7>[26695.169751] c0 mshci: MSHCI_FIFODAT: 0x00000000
<7>[26695.169845] c0 mshci: ===========================================
<3>[26695.170166] c0 mmcblk0: error -110 sending status command, aborting
<3>[26695.170367] c0 end_request: I/O error, dev mmcblk0, sector 22589728
<3>[26695.170540] c0 Buffer I/O error on device mmcblk0p12, logical block 2000420
<4>[26695.170747] c0 EXT4-fs warning (device mmcblk0p12): ext4_end_bio:258: I/O error writing to inode 65490 (offset 12288 size 4096 starting block 2823717)
<3>[26695.171109] c0 CMD aborting case in MMC's block layer ret 0.
<3>[26695.171271] c0 mmcblk0: CMD25, ARG=0x158b120.
<3>[26695.171370] c0 packed CMD type = 0.
<3>[26695.171461] c0 mmc0, request returns 4.

And here is the part I am concerned about: My internal memory is faulty! mmcblk0p12 belongs to /data and truely speaking this is not good!

/dev/block/mmcblk0p12 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0

Normaly the system shouldn't notice any defect sectors (because the hardware has some spare sectors and remaps the request to them) so I think I have serious trouble here.

What do you think? Do you agree on that assumption?