Android 9(Pie) Bringup issue on imx based custom Board : Problem with surfaceflinger

cancel
Showing results for 
Search instead for 
Did you mean: 

Android 9(Pie) Bringup issue on imx based custom Board : Problem with surfaceflinger

134 Views
Contributor I

Hi,
We are trying to bringing up Android 9-pie on imx based custom board. We are facing problem with board bring up. Device is not booting properly and continuously rebooting. We noticed problem with surfaceflinger. Surfaceflinger related errors from logs are highlighted here and also attached full log file for reference purpose. PFA for log file.
Please, Check it and provide the solution for it.

Boot.scr Kernel Command Line Setting:
setenv bootargs "$bootargs console=${console},115200 vmalloc=264M consoleblank=0 rootwait androidboot.console=$console,115200 androidboot.selinux=permisssive androidboot.selinux=disabled early_printk verity=0 androidboot.veritymode=logging androidboot.dm_verity=disabled androidboot.watchdogd=disabled androidboot.primary_display=imx-drm  firmware_class.path=/vendor/firmware androidboot.fbTileSupport=enable init=/init"

Faced Error/Problem:
init: starting service 'surfaceflinger'...
android_work: sent uevent USB_STATE=DISCONNECTED
logd.auditd: 45 output lines suppressed due to ratelimiting
DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
DEBUG: Build fingerprint: 'Android/cid/cid:9/2.2.0-ga-rc3/irrayaneperi07220421:eng/dev-keys'
DEBUG: Revision: '0'
DEBUG: ABI: 'arm'
DEBUG: pid: 664, tid: 664, name: surfaceflinger  >>> /system/bin/surfaceflinger <<<
DEBUG: signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
DEBUG: Abort message: 'EGLContext creation failed'
DEBUG:     r0  00000000  r1  00000298  r2  00000006  r3  abce0700
DEBUG:     r4  00000298  r5  00000298  r6  bee72fb4  r7  0000010c
DEBUG:     r8  00000001  r9  ab62d550  r10 00000001  r11 0000000b
DEBUG:     ip  bee73450  sp  bee72fa0  lr  abc6c0ad  pc  abc63e3a
DEBUG:
DEBUG: backtrace:
DEBUG:     #00 pc 0001ce3a  /system/lib/libc.so (abort+62)
DEBUG:     #01 pc 00006dd5  /system/lib/liblog.so (__android_log_assert+156)
DEBUG:     #02 pc 0006d3bf  /system/lib/libsurfaceflinger.so (android::RE::impl::RenderEngine::create(int, unsigned int)+950)
DEBUG:     #03 pc 00071257  /system/lib/libsurfaceflinger.so (android::SurfaceFlinger::init()+606)
DEBUG:     #04 pc 00002679  /system/bin/surfaceflinger (main+232)
DEBUG:     #05 pc 0008bd29  /system/lib/libc.so (__libc_init+48)
DEBUG:     #06 pc 0000254f  /system/bin/surfaceflinger (_start_main+46)
DEBUG:     #07 pc 00018037  /system/bin/linker (__dl__ZN6soinfoD1Ev+14)
DEBUG:     #08 pc 00020add  [stack:bee53000]
ci_hdrc ci_hdrc.1: remove, state 1

Waiting for your reply.
Regards,
AKS

Labels (4)
0 Kudos
3 Replies

57 Views
NXP TechSupport
NXP TechSupport

what android 9 do you use? P9.0.0_2.2.0?

0 Kudos

57 Views
Contributor I

Thanks for reply. Yes, Android 9 version is p9.0.0_2.2.0.

Please, Provide solution.

Thanks in Advanced.

0 Kudos

57 Views
NXP TechSupport
NXP TechSupport

refer to your log file, it seems that the GPU issue, maybe you can refer to the link as below:

EGLContext issue in P9.0.0_1.0.0-ga for i.MX 8M Quad EGLContext issue in P9.0.0_1.0.0-ga for i.MX 8M Quad 

one also can use  galcore.contiguousSize=xxx in the command line to set gpu memory size

0 Kudos