← Back to team overview

ubuntu-phone team mailing list archive

Android ATOMIC problems

 

Hi to all again,

after some time I am back with my problem connected to HP Toucpad and
Booting in to Black Screen. I have made some investigation and ended with
this:

1) my ubuntuappmanager dies

F/libc    (  142): Fatal signal 11 (SIGSEGV) at 0x2ac83494 (code=2), thread
142 (ubuntuappmanage)

2) caused by libcutils.so

I/DEBUG   (  136): backtrace:
I/DEBUG   (  136):     #00  pc 00005274  /system/lib/libcutils.so
(android_atomic_add+24)
I/DEBUG   (  136):     #01  pc 00005268  /system/lib/libcutils.so
(android_atomic_add+12)

3) when checking source code I can discover

00005270 <android_atomic_acquire_store>:
    5270:       e5810000        str     r0, [r1]
    5274:       eaffffef        b       5238 <android_memory_barrier>

and

0000525c <android_atomic_release_load>:
    525c:       e92d4010        push    {r4, lr}
    5260:       e1a04000        mov     r4, r0
    5264:       ebfffff3        bl      5238 <android_memory_barrier>
    5268:       e5940000        ldr     r0, [r4]
    526c:       e8bd8010        pop     {r4, pc}

So my general question is :

What is wrong with ANDROID_MEMORY_BARRIER ? Am I missing some configuration
related to kernel?

Thanks in advance
-- 

Petr Bláha

Follow ups