devmem2 crashed in JB

James Li

Hi All,

We have checked out source code of TI-Android-JB-4.1.2-DevKit-4.0.0 and built Android images for Mistral EVM board. Everything seems working fine except that I notice devmem2 crashes. I have tested the same command with ICS and devmem2 works fine with ICS.

The following is the logcat after I run "devmem2 0x48050000 w" command:

F/libc    ( 2892): Fatal signal 11 (SIGSEGV) at 0x00000034 (code=1), thread 2892 (devmem2)

I/DEBUG   ( 1150): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

I/DEBUG   ( 1150): Build fingerprint: 'Android/omap3evn/omap3evm:4.1.2/JZO54K/eng.james.20130813.092747:eng/test-keys'

I/DEBUG   ( 1150): pid: 2892, tid: 2892, name: devmem2 >>> devmem2 <<<

I/DEBUG   ( 1150): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000034

I/DEBUG   ( 1150):     r0 00000034 r1 00000000 r2 00000034 r3 00000000

I/DEBUG   ( 1150):     r4 400eca08 r5 00000006 r6 bee77cd0 r7 00000000

I/DEBUG   ( 1150):     r8 400ec000 r9 400ec9e0 sl 00000000 fp bee77d28

I/DEBUG   ( 1150):     ip 400ec8bc sp bee77a78 lr 400ec9e0 pc 400dd35c cpsr 00000030

I/DEBUG   ( 1150):     d0 0000000000000000 d1 0000000000000000

I/DEBUG   ( 1150):     d2 0000000000000000 d3 0000000000000000

I/DEBUG   ( 1150):     d4 0000000000000000 d5 0000000000000000

I/DEBUG   ( 1150):     d6 0000000000000000 d7 0000000000000000

I/DEBUG   ( 1150):     d8 0000000000000000 d9 0000000000000000

I/DEBUG   ( 1150):     d10 0000000000000000 d11 0000000000000000

I/DEBUG   ( 1150):     d12 0000000000000000 d13 0000000000000000

I/DEBUG   ( 1150):     d14 0000000000000000 d15 0000000000000000

I/DEBUG   ( 1150):     d16 0000000000000000 d17 0000000000000000

I/DEBUG   ( 1150):     d18 0000000000000000 d19 0000000000000000

I/DEBUG   ( 1150):     d20 0000000000000000 d21 0000000000000000

I/DEBUG   ( 1150):     d22 0000000000000000 d23 0000000000000000

I/DEBUG   ( 1150):     d24 0000000000000000 d25 0000000000000000

I/DEBUG   ( 1150):     d26 0000000000000000 d27 0000000000000000

I/DEBUG   ( 1150):     d28 0000000000000000 d29 0000000000000000

I/DEBUG   ( 1150):     d30 0000000000000000 d31 0000000000000000

I/DEBUG   ( 1150):     scr 00000000

I/DEBUG   ( 1150):

I/DEBUG   ( 1150): backtrace:

I/DEBUG   ( 1150):     #00 pc 0000535c /system/bin/linker

I/DEBUG   ( 1150):     #01 pc 00003708 /system/bin/linker

I/DEBUG   ( 1150):

I/DEBUG   ( 1150): stack:

I/DEBUG   ( 1150):          bee77a38 00000000

I/DEBUG   ( 1150):          bee77a3c 400f7630

I/DEBUG   ( 1150):          bee77a40 400eca08 /system/bin/linker

I/DEBUG   ( 1150):          bee77a44 400eca08 /system/bin/linker

I/DEBUG   ( 1150):          bee77a48 bee77ced [stack]

I/DEBUG   ( 1150):          bee77a4c 400eca08 /system/bin/linker

I/DEBUG   ( 1150):          bee77a50 bee77ced [stack]

I/DEBUG   ( 1150):          bee77a54 400dbb63 /system/bin/linker

I/DEBUG   ( 1150):          bee77a58 bee77ced [stack]

I/DEBUG   ( 1150):          bee77a5c 400e8e2c /system/bin/linker

I/DEBUG   ( 1150):          bee77a60 00000050

I/DEBUG   ( 1150):          bee77a64 00000000

I/DEBUG   ( 1150):          bee77a68 00000000

I/DEBUG   ( 1150):          bee77a6c 400eca08 /system/bin/linker

I/DEBUG   ( 1150):          bee77a70 df0027ad

I/DEBUG   ( 1150):          bee77a74 00000000

I/DEBUG   ( 1150):     #00 bee77a78 00000000

I/DEBUG   ( 1150):          bee77a7c 00000000

I/DEBUG   ( 1150):          bee77a80 00000000

I/DEBUG   ( 1150):          bee77a84 00000000

I/DEBUG   ( 1150):          bee77a88 00000000

I/DEBUG   ( 1150):          bee77a8c 00000000

I/DEBUG   ( 1150):          bee77a90 00000000

I/DEBUG   ( 1150):          bee77a94 00000000

I/DEBUG   ( 1150):          bee77a98 00000000

I/DEBUG   ( 1150):          bee77a9c 00000000

I/DEBUG   ( 1150):          bee77aa0 00000000

I/DEBUG   ( 1150):          bee77aa4 00000000

I/DEBUG   ( 1150):          bee77aa8 00000000

I/DEBUG   ( 1150):          bee77aac 00000000

I/DEBUG   ( 1150):          bee77ab0 00000000

I/DEBUG   ( 1150):          bee77ab4 00000000

I/DEBUG   ( 1150):          ........ ........

I/DEBUG   ( 1150):     #01 bee77be0 00000003

I/DEBUG   ( 1150):          bee77be4 bee77ced [stack]

I/DEBUG   ( 1150):          bee77be8 bee77cf5 [stack]

I/DEBUG   ( 1150):          bee77bec bee77d00 [stack]

I/DEBUG   ( 1150):          bee77bf0 00000000

I/DEBUG   ( 1150):          bee77bf4 bee77d02 [stack]

I/DEBUG   ( 1150):          bee77bf8 bee77d18 [stack]

I/DEBUG   ( 1150):          bee77bfc bee77d40 [stack]

I/DEBUG   ( 1150):          bee77c00 bee77d51 [stack]

I/DEBUG   ( 1150):          bee77c04 bee77e5d [stack]

I/DEBUG   ( 1150):          bee77c08 bee77e9a [stack]

I/DEBUG   ( 1150):          bee77c0c bee77eb3 [stack]

I/DEBUG   ( 1150):          bee77c10 bee77ec6 [stack]

I/DEBUG   ( 1150):          bee77c14 bee77edb [stack]

I/DEBUG   ( 1150):          bee77c18 bee77ef0 [stack]

I/DEBUG   ( 1150):          bee77c1c bee77f04 [stack]

I/DEBUG   ( 1150):

I/DEBUG   ( 1150): memory near r4:

I/DEBUG   ( 1150):     400ec9e8 00000000 00000000 00000000 00000000 ................

I/DEBUG   ( 1150):     400ec9f8 00000000 00000000 00000000 00000000 ................

I/DEBUG   ( 1150):     400eca08 6d766564 00326d65 00000000 00000000 devmem2.........

I/DEBUG   ( 1150):     400eca18 00000000 00000000 00000000 00000000 ................

I/DEBUG   ( 1150):     400eca28 00000000 00000000 00000000 00000000 ................

I/DEBUG   ( 1150):

I/DEBUG   ( 1150): memory near r6:

I/DEBUG   ( 1150):     bee77cb0 00000017 00000000 00000019 bee77cd9 .............|..

I/DEBUG   ( 1150):     bee77cc0 0000001f bee77fe8 0000000f bee77ce9 .............|..

I/DEBUG   ( 1150):     bee77cd0 00000000 00000000 30ddbd00 95dac35a ...........0Z...

I/DEBUG   ( 1150):     bee77ce0 64b500ff 40ae8a87 6c37766d 76656400 ...d...@mv7l.dev

I/DEBUG   ( 1150):     bee77cf0 326d656d 34783000 30353038 00303030 mem2.0x48050000.

I/DEBUG   ( 1150):

I/DEBUG   ( 1150): memory near r8:

I/DEBUG   ( 1150):     400ebfe0 00000000 00000000 00000000 00000000 ................

I/DEBUG   ( 1150):     400ebff0 00000000 00000000 00000000 00000000 ................

I/DEBUG   ( 1150):     400ec000 00000001 400ecb0c 400ddac5 00000000 .......@...@....

I/DEBUG   ( 1150):     400ec010 00000000 400eca08 400e8e67 400e8e73 .......@g..@s..@

I/DEBUG   ( 1150):     400ec020 00000000 00004000 00000000 00000002 .....@..........

I/DEBUG   ( 1150):

I/DEBUG   ( 1150): memory near r9:

I/DEBUG   ( 1150):     400ec9c0 00000000 400ec8bc 00000000 00000000 .......@........

I/DEBUG   ( 1150):     400ec9d0 400ecb0c 00000000 00000000 00000000 ...@............

I/DEBUG   ( 1150):     400ec9e0 400ec9c0 00000000 00000000 00000000 ...@............

I/DEBUG   ( 1150):     400ec9f0 00000000 00000000 00000000 00000000 ................

I/DEBUG   ( 1150):     400eca00 00000000 00000000 6d766564 00326d65 ........devmem2.

I/DEBUG   ( 1150):

I/DEBUG   ( 1150): memory near fp:

I/DEBUG   ( 1150):     bee77d08 2f6d6574 2f6e6962 6d766564 00326d65 tem/bin/devmem2.

I/DEBUG   ( 1150):     bee77d18 4c5f444c 41524249 505f5952 3d485441 LD_LIBRARY_PATH=

I/DEBUG   ( 1150):     bee77d28 6e65762f 2f726f64 3a62696c 7379732f /vendor/lib:/sys

I/DEBUG   ( 1150):     bee77d38 2f6d6574 0062696c 54534f48 454d414e tem/lib.HOSTNAME

I/DEBUG   ( 1150):     bee77d48 646e613d 64696f72 4f4f4200 414c4354 =android.BOOTCLA

I/DEBUG   ( 1150):

I/DEBUG   ( 1150): memory near ip:

I/DEBUG   ( 1150):     400ec89c 00000000 00000000 00000000 00000000 ................

I/DEBUG   ( 1150):     400ec8ac 00000000 00000000 00000000 00000000 ................

I/DEBUG   ( 1150):     400ec8bc 7379732f 2f6d6574 2f6e6962 6b6e696c /system/bin/link

I/DEBUG   ( 1150):     400ec8cc 00007265 00000000 00000000 00000000 er..............

I/DEBUG   ( 1150):     400ec8dc 00000000 00000000 00000000 00000000 ................

I/DEBUG   ( 1150):

I/DEBUG   ( 1150): memory near sp:

I/DEBUG   ( 1150):     bee77a58 bee77ced 400e8e2c 00000050 00000000 .|..,..@P.......

I/DEBUG   ( 1150):     bee77a68 00000000 400eca08 df0027ad 00000000 .......@.'......

I/DEBUG   ( 1150):     bee77a78 00000000 00000000 00000000 00000000 ................

I/DEBUG   ( 1150):     bee77a88 00000000 00000000 00000000 00000000 ................

I/DEBUG   ( 1150):     bee77a98 00000000 00000000 00000000 00000000 ................

I/DEBUG   ( 1150):

I/DEBUG   ( 1150): code around pc:

I/DEBUG   ( 1150):     400dd33c f8c46873 36083080 2b006833 f8c4d1ea sh...0.63h.+....

I/DEBUG   ( 1150):     400dd34c f8d4308c e00c5084 2080f8d4 18500159 .0...P..... Y.P.

I/DEBUG   ( 1150):     400dd35c 29065851 6885d104 f8c41b50 e002008c QX.)...hP.......

I/DEBUG   ( 1150):     400dd36c 42ab3301 2500dbf0 32fff04f f8c42301 .3.B...%O..2.#..

I/DEBUG   ( 1150):     400dd37c f8c42098 f8c4209c f8c450a0 f8c43100 . ... ...P...1..

I/DEBUG   ( 1150):

I/DEBUG   ( 1150): code around lr:

I/DEBUG   ( 1150):     400ec9c0 00000000 400ec8bc 00000000 00000000 .......@........

I/DEBUG   ( 1150):     400ec9d0 400ecb0c 00000000 00000000 00000000 ...@............

I/DEBUG   ( 1150):     400ec9e0 400ec9c0 00000000 00000000 00000000 ...@............

I/DEBUG   ( 1150):     400ec9f0 00000000 00000000 00000000 00000000 ................

I/DEBUG   ( 1150):     400eca00 00000000 00000000 6d766564 00326d65 ........devmem2.

Does anybody encounter the same problem? Is there any fix for that?

Thanks,

James

over 12 years ago

0 James Li over 12 years ago

Intellectual 750 points

I also noticed that liblights folder under device/ti/omap3evm was also removed. Right now JB on evm cannot control backlight from UI.

Is there any specific reason to remove liblights folder?

Thanks,

James

0 Arun Joseph over 12 years ago in reply to James Li

TI__Expert 7220 points

HI James,

The devmem2 crash is due to application sandboxing feature of JellyBean (Security related). The devmem2 binary from the ICS DevKit does not crash in JB filesystem.

There is no specific reason for removing liblights folder. You can copy the folder from the ICS sources and add the lights.<>.so to the PRODUCT_PACKAGES definition. This will work

Regards,

Arun

0 James Li over 12 years ago in reply to Arun Joseph

Intellectual 750 points

Hi Arun,

Thanks for your prompt reply.

I run devmem2 binary from ICS and it runs in JB. However I built lights.omap3.so in JB and it crashed again. The ICS version lights.omap3.so works fine in JB filesystem.

Could you help me verify this?

I'm just afraid that there are maybe some other binaries or libraries will fail due to JB security features. How can we make sure that all binaries will pass application sandboxing feature?

Thanks a lot,

James

0 Arun Joseph over 12 years ago in reply to James Li

TI__Expert 7220 points

Hi James,

Normally Android HALs like lights do not have any issue with sand boxing if compiled properly.

As I understand, Application sand boxing is enforced from the android toolchain and the bionic libraries.

Can you refer to http://gitorious.org/rowboat/vendor-ti-am335xevm/trees/rowboat-jb-4.1 and create a similar lights HAL?

0 James Li over 12 years ago in reply to Arun Joseph

Intellectual 750 points

Hi Arun,

I compared two lights.c files between am37xx and am335xevm. The difference is "const struct hw_module_t HAL_MODULE_INFO_SYM = {". am37xx defines struct hw_module_t HAL_MODULE_INFO_SYM with const. After I delete const and rebuild, my backlight works in JB. I don't understand why const keyword will cause backlight lib to crash. Can you explain a little bit so that we can avoid the similar issue in the future if we need to write our own HAL?

Thanks,

James