Random reboots van Samsung Galaxy Tab 2 10.1

[Tuxinator]

Sinds een paar dagen is mijn Samsung Galaxy Tab 2 10.1 random aan het rebooten. Op de Tab draait CyanogenMod 10.1.3. Om naar de oorzaak te zoeken heb ik met Titanium Backup third party apps bevroren om die uit te sluiten, en in de recovery de cache partitie gewist, maar dat bracht geen oplossing. Vervolgens eens met Odin de stock firmware geflashed en dat leek goed te gaan. Nu ben ik weer terug naar CyanogenMod en de reboots beginnen weer opnieuw.

Als ik na die reboot kijk naar /proc/last_kmsg dan kom ik de nodige I/O errors tegen, ik heb de log even op Pastebin gegooid aangezien die een beetje groot is: http://pastebin.com/GN8Du34C

Hier een klein gedeelte uit die log:

code:

[   16.266265] C1 [           init] android_usb: already disabled
[   16.266601] C1 [           init] android_usb: already disabled
[   17.524566] C1 [           init] init: cannot find '/sbin/cbd', disabling 'cpboot-daemon'
[   18.065307] C0 [ SurfaceFlinger] Invalid Device Structure
[   83.363311] C0 [       Binder_4] accel_open_calibration: Can't open calibration file
[   86.872558] C1 [       Binder_2] accel_open_calibration: Can't open calibration file
[  117.836242] C0 [       Binder_5] accel_open_calibration: Can't open calibration file
[  121.312530] C1 [       Binder_3] accel_open_calibration: Can't open calibration file
[  126.463806] C1 [  system_server] accel_open_calibration: Can't open calibration file
[  129.958343] C0 [       Binder_5] accel_open_calibration: Can't open calibration file
[  240.795715] C0 [        mmcqd/0] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[  240.795959] C0 [        mmcqd/0] mmcblk0: error -110 transferring data, sector 26404336, nr 8, cmd response 0x900, card status 0x0
[  240.796203] C0 [        mmcqd/0] Buffer I/O error on device mmcblk0p10, logical block 2744510
[  338.316589] C1 [           init] init: untracked pid 3068 exited
[ 1346.119262] C1 [    kworker/u:3] failed to stop pwm timer. ret=-22
[ 1346.682281] C1 [    kworker/u:3] Invalid Device Structure
[ 1437.307495] C0 [    kworker/u:3] Freezing of user space  aborted
[ 1441.690246] C0 [    kworker/u:3] Successfully put all powerdomains to target state
[ 1442.191131] C1 [          khubd] hub 1-0:1.0: activate --> -22
[ 1445.314849] C0 [    kworker/u:3] Successfully put all powerdomains to target state
[ 1445.778015] C1 [          khubd] hub 1-0:1.0: activate --> -22
[ 1448.796722] C0 [    kworker/u:3] Successfully put all powerdomains to target state
[ 1449.293670] C1 [          khubd] hub 1-0:1.0: activate --> -22
[ 1478.214355] C0 [    kworker/u:1] binder: release proc 6173, transaction 990934, not freed
[ 1486.452850] C0 [        mmcqd/0] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400e00
[ 1486.503173] C0 [        mmcqd/0] mmcblk0: error -110 transferring data, sector 26403880, nr 8, cmd response 0x900, card status 0x0
[ 1486.503417] C0 [        mmcqd/0] Buffer I/O error on device mmcblk0p10, logical block 2744453
[ 1487.936614] C0 [        mmcqd/0] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[ 1487.936859] C0 [        mmcqd/0] mmcblk0: error -110 transferring data, sector 26403880, nr 40, cmd response 0x900, card status 0x0
[ 1487.937255] C0 [        mmcqd/0] Buffer I/O error on device mmcblk0p10, logical block 2744453
[ 1487.937438] C0 [        mmcqd/0] Buffer I/O error on device mmcblk0p10, logical block 2744454
[ 1487.937591] C0 [        mmcqd/0] Buffer I/O error on device mmcblk0p10, logical block 2744455
[ 1487.937713] C0 [        mmcqd/0] Buffer I/O error on device mmcblk0p10, logical block 2744456
[ 1487.937866] C0 [        mmcqd/0] Buffer I/O error on device mmcblk0p10, logical block 2744457
[ 1517.150726] C1 [    kworker/u:4] binder: release proc 6413, transaction 1003242, not freed
[ 1601.666259] C0 [    kworker/u:4] failed to stop pwm timer. ret=-22
[ 1602.229492] C0 [    kworker/u:4] Invalid Device Structure
[ 1694.663085] C1 [        mmcqd/0] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400e00
[ 1694.663330] C1 [        mmcqd/0] mmcblk0: error -110 transferring data, sector 5229800, nr 8, cmd response 0x900, card status 0x0
[ 1694.663818] C1 [jbd2/mmcblk0p10] Aborting journal on device mmcblk0p10-8.
[ 1695.623352] C1 [         dexopt] journal commit I/O error
[ 1695.644592] C1 [         dexopt] EXT4-fs error (device mmcblk0p10): ext4_journal_start_sb:296: Detected aborted journal
[ 1695.644744] C1 [         dexopt] EXT4-fs (mmcblk0p10): Remounting filesystem read-only
[ 1695.649810] C1 [         dexopt] Kernel panic - not syncing: EXT4-fs panic from previous error

Die I/O errors gebeuren op device mmcblk0p10. Nu heb ik de tablet vanaf de PC benaderd met ADB om een filecheck te doen op die partitie (is de data partitie overigens) en die check gaf aan dat er niets aan de hand zou zijn:

code:

~ # e2fsck -n /dev/block/mmcblk0p10
e2fsck 1.41.11 (14-Mar-2010)
/dev/block/mmcblk0p10: clean, 40720/791520 files, 2056361/3160055 blocks

Nu weet ik eigenlijk even niet meer wat ik er mee aan moet. Heb ik gewoon geluk gehad dat met de stock firmware alles goed leek te lopen, en is de interne opslag gewoon aan het verslijten?