Surfaceflinger SIGSEGV error.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Surfaceflinger SIGSEGV error.

1,550 Views
kurkinalexandr
Contributor III

Hello.

Trying run Android 6 on Compulab cm-fx6 reference board.

But getting gpu surfaceflinger-gpu issue:

Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 207 (surfaceflinger)

This cause Android main services recursively being restarted and Android never can start.

Could you please give me some tips how to fix this issue, may be some extradebug needed for that.

Please see logcat output below.

--------- beginning of system
01-01 20:44:12.747   198   198 I vold    : Vold 3.0 (the awakening) firing up
01-01 20:44:12.749   198   198 V vold    : Detected support for: ext4 f2fs vfat
01-01 20:44:12.756   198   198 W Vold    : Tearing down stale mount /mnt/shm
01-01 20:44:12.816   205   205 I lowmemorykiller: Using in-kernel low memory killer iinit: Starting service 'netd'...
nterface
01-01 20:44:12.915   19init: Starting service 'surfaceflinger'...
8   210 V vold    : /system/bin/sinit: Starting service 'media'...
gdisk
01-01 20:44:12.915   198  init: Starting service 'zygote'...
 210 V vold    :     --android-dump
01-01 20:44:12.915   198   210 V vold    :     /dev/block/vold/disk:179,0
01-01 20:44:12.960   213   213 I         : debuggerd: starting
01-01 20:44:13.009   218   218 I installd: installd firing up
01-01 20:44:13.021   198   210 V vold    : DISK mbr
01-01 20:44:13.021   198   210 V vold    : PART 1 83
01-01 20:44:13.021   198   210 V vold    : PART 2 83
01-01 20:44:13.021   198   210 V vold    : PART 3 83
01-01 20:44:13.021   198   210 V vold    : PART 5 83
01-01 20:44:13.021   198   210 V vold    : PART 6 83
01-01 20:44:13.021   198   210 V vold    : PART 7 83
01-01 20:44:13.021   198   210 V vold    : PART 8 83
01-01 20:44:13.021   198   210 V vold    : PART 9 83
01-01 20:44:13.021   198   210 W vold    : disk:179,0 is ignoring partition 9 beyond max supported devices
01-01 20:44:13.051   211   211 I Netd    : Netd 1.0 starting
01-01 20:44:13.062   211   211 D TetherController: Setting IP forward enable = 0
01-01 20:44:13.086   224   224 D MagDaemon: init_sensors
01-01 20:44:13.127   222   222 I gatekeeperd: Starting gatekeeperd...
01-01 20:44:13.278   223   223 I perfprofd: starting Android Wide Profiling daemon
01-01 20:44:13.283   223   223 E perfprofd: unable to open configuration file /data/data/com.google.android.gms/files/perfprofd.conf
01-01 20:44:13.283   223   223 I perfprofd: random seed set to 304814250
01-01 20:44:13.347   222   222 W gatekeeperd: falling back to software GateKeeper
01-01 20:44:13.358   219   219 I keystore: Found keymaster0 module Keymaster OpenSSL HAL, version 2
01-01 20:44:13.358   219   219 I SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 122: Creating device
01-01 20:44:13.358   219   219 D SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 123: Device address: 0xb6ba4000
01-01 20:44:13.358   219   219 I keystore: Keymaster0 module is software-only.  Using SoftKeymasterDevice instead.
01-01 20:44:13.358   219   219 I SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 122: Creating device
01-01 20:44:13.358   219   219 D SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 123: Device address: 0xb6ba4180
01-01 20:44:13.588   207   207 I SurfaceFlinger: SurfaceFlinger is starting
01-01 20:44:13.588   207   207 I SurfaceFlinger: SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
01-01 20:44:13.684   207   207 D libEGL  : loaded /system/lib/egl/libEGL_VIVANTE.so
01-01 20:44:13.790   207   207 D libEGL  : loaded /system/lib/egl/libGLESv1_CM_VIVANTE.so
01-01 20:44:13.816   224   224 D MagDaemon: couldn't find 'FreescaleAccelerometer' input device
01-01 20:44:13.816   224   224 D MagDaemon: inital sensor error
01-01 20:44:13.864   207   207 D libEGL  : loaded /system/lib/egl/libGLESv2_VIVANTE.so
--------- beginning of crash
01-01 20:44:13.904   207   207 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 207 (surfaceflinger)
01-01 20:44:14.011   213   213 I SELinux : SELinux: Loaded file_contexts contexts from /file_contexts.
01-01 20:44:14.016   213   213 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-01 20:44:14.016   213   213 F DEBUG   : Build fingerprint: 'Freescale/cm_fx6_evk/cm_fx6_evk:6.0.1/2.1.0-ga-rc2/20160715:eng/release-keys'
01-01 20:44:14.016   213   213 F DEBUG   : Revision: '0'
01-01 20:44:14.016   213   213 F DEBUG   : ABI: 'arm'
01-01 20:44:14.016   213   213 F DEBUG   : pid: 207, tid: 207, name: surfaceflinger  >>> /system/bin/surfaceflinger <<<
01-01 20:44:14.016   213   213 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
01-01 20:44:14.022   213   213 F DEBUG   :     r0 00000000  r1 00000000  r2 00000000  r3 b6b4d415
01-01 20:44:14.022   213   213 F DEBUG   :     r4 00000000  r5 00000000  r6 b6f53d04  r7 ffffffff
01-01 20:44:14.022   213   213 F DEBUG   :     r8 b6f9e6ec  r9 ffffffff  sl b6f53d04  fp b6f977b4
01-01 20:44:14.022   213   213 F DEBUG   :     ip b6e1b884  sp bef9f778  lr b65a337f  pc b6de639e  cpsr 400e0030
01-01 20:44:14.063   213   213 F DEBUG   :
01-01 20:44:14.063   213   213 F DEBUG   : backtrace:
01-01 20:44:14.063   213   213 F DEBUG   :     #00 pc 0004039e  /system/lib/libc.so (pthread_mutex_trylock+1)
01-01 20:44:14.063   213   213 F DEBUG   :     #01 pc 0003d37b  /system/lib/libGAL.so (gcoOS_DeleteMutex+6)
01-01 20:44:14.063   213   213 F DEBUG   :     #02 pc 0003dd8b  /system/lib/libGAL.so
01-01 20:44:14.063   213   213 F DEBUG   :     #03 pc 0000e6c7  /system/lib/libGAL.so
01-01 20:44:14.063   213   213 F DEBUG   :     #04 pc 00002469  /system/bin/linker (__dl__ZN6soinfo13call_functionEPKcPFvvE+48)
01-01 20:44:14.063   213   213 F DEBUG   :     #05 pc 00002535  /system/bin/linker (__dl__ZN6soinfo10call_arrayEPKcPPFvvEjb+136)
01-01 20:44:14.063   213   213 F DEBUG   :     #06 pc 000025f3  /system/bin/linker (__dl__ZN6soinfo16call_destructorsEv+58)
01-01 20:44:14.063   213   213 F DEBUG   :     #07 pc 0000697f  /system/bin/linker (__dl__ZL13soinfo_unloadP6soinfo+266)
01-01 20:44:14.063   213   213 F DEBUG   :     #08 pc 00006a09  /system/bin/linker (__dl__ZL13soinfo_unloadP6soinfo+404)
01-01 20:44:14.063   213   213 F DEBUG   :     #09 pc 00006bef  /system/bin/linker (__dl__Z10do_dlcloseP6soinfo+14)
01-01 20:44:14.063   213   213 F DEBUG   :     #10 pc 00001abd  /system/bin/linker (__dl_dlclose+16)
01-01 20:44:14.063   213   213 F DEBUG   :     #11 pc 00047919  /system/lib/libEGL.so
01-01 20:44:14.063   213   213 F DEBinit: Service 'surfaceflinger' (pid 397) killed by signal 11
UG   :     #12 pc 00047935  /systinit: Service 'surfaceflinger' (pid 397) killing any children in process group
em/lib/libEGL.so
01-01 20:44:14.063   213   213 F DEBUG   :     init: Service 'zygote' is being killed...
#13 pc 00012171  /system/lib/libEinit: Service 'zygote' (pid 399) killed by signal 9
GL.so (android::egl_display_t::geinit: Service 'zygote' (pid 399) killing any children in process group
tDisplay(void*)+88)
01-01 20:44:init: write_file: Unable to open '/sys/android_power/request_state': No such file or directory
14.064   213   213 F DEBUG   :   init: write_file: Unable to write to '/sys/power/state': Invalid argument
  #14 pc 00018e51  /system/lib/liinit: Service 'media' is being killed...
bsurfaceflinger.so (android::Surfinit: Service 'netd' is being killed...
aceFlinger::init()+48)
01-01 20:init: Service 'media' (pid 398) killed by signal 9
44:14.064   213   213 F DEBUG   :init: Service 'media' (pid 398) killing any children in process group
     #15 pc 00000e9d  /system/bininit: Service 'netd' (pid 396) killed by signal 9
/surfaceflinger
01-01 20:44:14.0init: Service 'netd' (pid 396) killing any children in process group
64   213   213 F DEBUG   :     #1init: Untracked pid 428 killed by signal 9
6 pc 00017365  /system/lib/libc.so (__libc_init+44)

Labels (4)
0 Kudos
1 Reply

958 Views
igorpadykov
NXP Employee
NXP Employee

Hi Fan

reason may be that wrong image used, as cm-fx6 may have i.MX6S and i.MX6Q processors

which require different images, one can check

CM-FX6 Freescale i.MX6 SW Resources - CompuLab Wiki 

Alternatively one can try with nxp demo boards and Demo Images from

https://www.nxp.com/support/developer-resources/run-time-software/i.mx-developer-resources/i.mx-6ser...

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

0 Kudos