[Galaxy Note 3 Original Android Development] svbarbosa:
Buffer I/O error on mmcblk0p26 (/data)

My N9005 is rebooting every other day. Looking at the last_kmsg (copy below) I found that my emmc may be failing.

I have enabled the "mmc crc" option using ik. [MENTION=5672995]jcadduono[/MENTION], how does this work? will the kernel just log errors? :confused:

After reboot the "mmc crc" stays enabled as it should, but Kernel Adiutor has a "software CRC control" option under "Misc Controls" that remains disabled. Is this another option or is Kernel Adiutor looking at the wrong place?

I am running Euphoria CM Based ROM with 6.5.3-cm12.1 permissive IdleKernel.

Here are the lines extracted from my last_kmsg:

[134474.959076] Buffer I/O error on device mmcblk0p26, logical block 0
[134474.959168] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1048988: block 4194617: comm gostatiscs_post: unable to read itable block
[134474.959354] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134474.959432] Buffer I/O error on device mmcblk0p26, logical block 0
[134474.959481] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1048988: block 4194617: comm gostatiscs_post: unable to read itable block
[134474.959694] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134474.959739] Buffer I/O error on device mmcblk0p26, logical block 0
[134474.959819] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1048949: block 4194615: comm gostatiscs_post: unable to read itable block
[134474.959992] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134474.960070] Buffer I/O error on device mmcblk0p26, logical block 0
[134474.960116] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1048988: block 4194617: comm gostatiscs_post: unable to read itable block
[134474.998151] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134474.998241] Buffer I/O error on device mmcblk0p26, logical block 0
[134474.998328] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #914296: block 3670071: comm com.whatsapp: unable to read itable block
[134475.015523] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.015579] Buffer I/O error on device mmcblk0p26, logical block 0
[134475.015662] EXT4-fs error (device mmcblk0p26): ext4_find_entry:941: inode #817993: comm Thread-13639: reading directory lblock 0
[134475.027596] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.027694] Buffer I/O error on device mmcblk0p26, logical block 0
[134475.027756] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1566808: block 6291493: comm sdcard: unable to read itable block
[134475.028021] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.028104] Buffer I/O error on device mmcblk0p26, logical block 0
[134475.028155] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1566808: block 6291493: comm sdcard: unable to read itable block
[134475.031850] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.031900] Buffer I/O error on device mmcblk0p26, logical block 0
[134475.031979] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1048988: block 4194617: comm gostatiscs_post: unable to read itable block
[134475.032148] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.032225] Buffer I/O error on device mmcblk0p26, logical block 0
[134475.032270] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1048988: block 4194617: comm gostatiscs_post: unable to read itable block
[134475.032477] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.032523] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1048949: block 4194615: comm gostatiscs_post: unable to read itable block
[134475.032691] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.032769] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1048988: block 4194617: comm gostatiscs_post: unable to read itable block
[134475.075147] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.075237] EXT4-fs error (device mmcblk0p26): ext4_find_entry:941: inode #1175044: comm main: reading directory lblock 0
[134475.100988] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.101045] EXT4-fs error (device mmcblk0p26): ext4_find_entry:941: inode #1045543: comm unkyfresh.samba: reading directory lblock 0
[134475.101470] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.101524] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1045543: block 4194402: comm unkyfresh.samba: unable to read itable block
[134475.103467] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.103561] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #522289: block 2097187: comm wpa_supplicant: unable to read itable block
[134475.109967] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.110063] EXT4-fs error (device mmcblk0p26): ext4_find_entry:941: inode #913924: comm Error dump: dat: reading directory lblock 0
[134475.181764] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.181852] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1048924: block 4194613: comm GOSmsThreadServ: unable to read itable block
[134475.182123] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.182174] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1048931: block 4194614: comm GOSmsThreadServ: unable to read itable block
[134475.182390] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.182437] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1048924: block 4194613: comm GOSmsThreadServ: unable to read itable block
[134475.182634] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.182682] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1048931: block 4194614: comm GOSmsThreadServ: unable to read itable block
[134475.182856] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.182935] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1048931: block 4194614: comm GOSmsThreadServ: unable to read itable block
[134475.183115] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.183195] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1048931: block 4194614: comm GOSmsThreadServ: unable to read itable block
[134475.183409] EXT4-fs (mmcblk0p26): previous I/O error to superblock detected
[134475.183487] EXT4-fs error (device mmcblk0p26): __ext4_get_inode_loc:3593: inode #1048931: block 4194614: comm GOSmsThreadServ: unable to read itable block
[134475.495062] Restarting system with command 'recovery'.
[134475.496312] Calling SCM to disable SPMI PMIC arbiter