android hang up after memory init

cancel
Showing results for 
Search instead for 
Did you mean: 

android hang up after memory init

777 Views
jjjeeesss
Contributor I

Hello

My custom board have a imx6 solo processor and eMMC.

BSP is android_jb4.3_1.1.0-ga.

When i reset during boot today, my board hang up with kernel panic.

How can i solve this problem?

-------------------------------------------------------------------------------------------------------------------------

...

snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:01 UTC (1)

Freeing init memory: 752K

EXT4-fs error (device mmcblk0p4): ext4_mb_generate_buddy:736: group 8, 32248 blocks in bitmap, 32249 in gd

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

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

[<c06e67d8>] (panic+0x74/0x194) from [<c0241bd4>] (ext4_handle_error.part.111+0x5c/0x98)

[<c0241bd4>] (ext4_handle_error.part.111+0x5c/0x98) from [<c0242684>] (__ext4_grp_locked_error+0xbc/0x1bc)

[<c0242684>] (__ext4_grp_locked_error+0xbc/0x1bc) from [<c024e360>] (ext4_mb_generate_buddy+0x124/0x1d4)

[<c024e360>] (ext4_mb_generate_buddy+0x124/0x1d4) from [<c024e93c>] (ext4_mb_init_cache+0x52c/0x904)

[<c024e93c>] (ext4_mb_init_cache+0x52c/0x904) from [<c024ede0>] (ext4_mb_init_group+0xcc/0xf8)

[<c024ede0>] (ext4_mb_init_group+0xcc/0xf8) from [<c024f258>] (ext4_mb_load_buddy+0x2d8/0x30c)

[<c024f258>] (ext4_mb_load_buddy+0x2d8/0x30c) from [<c0255758>] (ext4_free_blocks+0x300/0xa04)

[<c0255758>] (ext4_free_blocks+0x300/0xa04) from [<c022a2bc>] (ext4_clear_blocks+0x140/0x1a4)

[<c022a2bc>] (ext4_clear_blocks+0x140/0x1a4) from [<c022a4bc>] (ext4_free_data+0x19c/0x1b0)

[<c022a4bc>] (ext4_free_data+0x19c/0x1b0) from [<c022bfd0>] (ext4_truncate+0x500/0x678)

[<c022bfd0>] (ext4_truncate+0x500/0x678) from [<c022efa4>] (ext4_evict_inode+0x2a4/0x3d0)

[<c022efa4>] (ext4_evict_inode+0x2a4/0x3d0) from [<c01c7dd4>] (evict+0x70/0x168)

[<c01c7dd4>] (evict+0x70/0x168) from [<c01c3594>] (d_kill+0x54/0x64)

[<c01c3594>] (d_kill+0x54/0x64) from [<c01c4a18>] (dput+0xd8/0x1b4)

[<c01c4a18>] (dput+0xd8/0x1b4) from [<c01bee44>] (sys_renameat+0x190/0x1d8)

[<c01bee44>] (sys_renameat+0x190/0x1d8) from [<c00ca9c0>] (ret_fast_syscall+0x0/0x30)

0 Kudos
2 Replies

106 Views
liweihua
Contributor I

Hello,

We also encountered this problem,do you have any solution or advise about it?

Thanks a lot!

0 Kudos

106 Views
igorpadykov
NXP TechSupport
NXP TechSupport

HI je

please check that mx6solo_sabresd_android_config used for image building,

as described in attached Android_Frequently_Asked_Questions.pdf

sect.19 "How do I run the image on i.MX 6Solo board?" and

was included patch i.MX 6 Android JB 4.3_1.1.1 Patch Release.

Also had you test DDR memory for custom board :

i.MX6/7 DDR Stress Test Tool V2.10

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

0 Kudos