AnsweredAssumed Answered

I.MX6S Losts its data and the Android 4.3 OS could not start normally

Question asked by luke gu on Dec 23, 2015
Latest reply on Dec 24, 2015 by igorpadykov

Hi Dear ,

      My customer has used the MCIMX6S5EVM10AC with the PMIC MMPF0100F0AEP for the application of Building Intercom. They run the android 4.3 OS ,

When they run the OS and application in some Release products ,maybe 50 or above , they give the products power on and off sequentially , the time slot

is about 35 seconds , they miss the following issue :

      1. System has been stuck in the Android word rolling interface, access to the system launcher , and

      2. Encryption error ;


        More , the first phenomenon is also divided into two cases: one is the kernel without any error, but the system is not activated in the process of the system launcher.and the other is, that the kernel occurs ext4 error, and then the kernel runaway. Print log as follows :


(device mmcblk0p4): htree_dirblock_to_tree:587: inode #195: block 8445: comm er.ServerThread: bad entry in directory: rec_len % 4 != 0 - offset=0(12288), inode=1935633765, rec_len=29285, name_len=118

Aborting journal on device mmcblk0p4-8.

Kernel panic - not syncing: EXT4-fs (device mmcblk0p4): panic forced after error


[<c0053fc4>] (unwind_backtrace+0x0/0x138) from [<c06638ac>] (panic+0x74/0x194)

[<c06638ac>] (panic+0x74/0x194) from [<c01c1244>] (ext4_handle_error+0x68/0xa4)

[<c01c1244>] (ext4_handle_error+0x68/0xa4) from [<c01c1540>] (ext4_error_inode+0xa4/0xcc)

[<c01c1540>] (ext4_error_inode+0xa4/0xcc) from [<c01a2100>] (__ext4_check_dir_entry+0x178/0x1a8)

[<c01a2100>] (__ext4_check_dir_entry+0x178/0x1a8) from [<c01b1508>] (htree_dirblock_to_tree+0xb0/0x184)

[<c01b1508>] (htree_dirblock_to_tree+0xb0/0x184) from [<c01b3330>] (ext4_htree_fill_tree+0x130/0x1d0)

[<c01b3330>] (ext4_htree_fill_tree+0x130/0x1d0) from [<c01a26a8>] (ext4_readdir+0x578/0x67c)

[<c01a26a8>] (ext4_readdir+0x578/0x67c) from [<c0140c00>] (vfs_readdir+0x7c/0xa4)

[<c0140c00>] (vfs_readdir+0x7c/0xa4) from [<c0140d34>] (sys_getdents64+0x5c/0xb4)

[<c0140d34>] (sys_getdents64+0x5c/0xb4) from [<c004c900>] (ret_fast_syscall+0x0/0x30)


   Could you kindly help me to check whether the problem locates OR how can the customer to solve this problem? If any other info should be provided , I will contact with my customer ASAP. Appreciated a lot !