AnTuTu test issues on i.mx8 Android 9.0

CordialMai — Fri, 04 Jun 2021 03:14:52 GMT

While running the Antutu benchmark test on i.mx8 Android 9.0, Antutu stucked at 图像处理FishEye window.

Could you let me know how to sloved it?

The following is the log,it stuck at 9:40.Please see the attachment for the detailed log

(Filename: ./Runtime/Graphics/RenderTexture.cpp Line: 477)
2021-06-04 09:40:11.258 4691-4708/com.antutu.benchmark.full.lite W/Unity: RenderTexture.Create: Depth|ShadowMap RenderTexture requested without a depth buffer. Changing to a 16 bit depth buffer.

(Filename: ./Runtime/Graphics/RenderTexture.cpp Line: 477)
2021-06-04 09:40:12.302 3213-3223/system_process I/system_server: Background concurrent copying GC freed 175280(5MB) AllocSpace objects, 0(0B) LOS objects, 42% free, 6MB/11MB, paused 133us total 123.878ms
2021-06-04 09:40:15.313 3213-3223/system_process I/system_server: Background concurrent copying GC freed 185512(5MB) AllocSpace objects, 0(0B) LOS objects, 42% free, 6MB/11MB, paused 167us total 126.378ms
2021-06-04 09:40:15.734 3076-3185/? E/Fence: Throttling EGL Production: fence 58 didn't signal in 3000 ms
2021-06-04 09:40:17.953 3213-3223/system_process I/system_server: Background concurrent copying GC freed 173010(4MB) AllocSpace objects, 0(0B) LOS objects, 42% free, 6MB/11MB, paused 166us total 124.254ms
2021-06-04 09:40:20.781 3213-3223/system_process I/system_server: Background concurrent copying GC freed 173050(5MB) AllocSpace objects, 0(0B) LOS objects, 42% free, 6MB/12MB, paused 147us total 125.255ms
2021-06-04 09:40:21.147 3076-3135/? E/Fence: Throttling EGL Production: fence 98 didn't signal in 3000 ms
2021-06-04 09:40:21.503 3076-3185/? E/Fence: Throttling EGL Production: fence 71 didn't signal in 3000 ms
2021-06-04 09:40:21.525 3377-3684/com.android.systemui I/OpenGLRenderer: Davey! duration=3385ms; Flags=0, IntendedVsync=515704150633, Vsync=515704150633, OldestInputEvent=9223372036854775807, NewestInputEvent=0, HandleInputStart=515704786445, AnimationStart=515704817765, PerformTraversalsStart=515704818725, DrawStart=515707487166, SyncQueued=515707575486, SyncStart=515707645086, IssueDrawCommandsStart=515707803966, SwapBuffers=515710004766, FrameCompleted=519090308182, DequeueBufferDuration=13292000, QueueBufferDuration=3366697000,
2021-06-04 09:40:23.610 3075-3075/? I/lowmemorykiller: Kill 'com.android.contacts' (4292), uid 10019, oom_adj 906 to free 43964kB
2021-06-04 09:40:23.610 3075-3075/? I/lowmemorykiller: Killing to reclaim 318408kB, reclaimed 43964kB, cache(320904kB) and free(22276kB)-reserved(18124kB) below min(322560kB) for oom_adj 906
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000000000000460
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: Build fingerprint: 'Android/evk_8mq/evk_8mq:9/PQ2A.190405.003/dxy06040851:eng/dev-keys'
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: Revision: '0'
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: pid: 4691, tid: 4708, name: UnityMain >>> com.antutu.benchmark.full.lite:unity <<<
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: x0 0000f41abb9fdce0 x1 0000000000000001 x2 0000f41abb9fdc00 x3 0000000000000000
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: x4 0000000000000000 x5 0000f41ab70dc5a0 x6 0000f41ab70dc588 x7 0000000000000000
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: x8 0000f41abb9fdce0 x9 0000000000000000 x10 0000000000000001 x11 0000000000000021
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: x12 00000000deadbeaf x13 0000f41ab70dc578 x14 0000f41adac28148 x15 0000000000000208
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: x16 0000f41adac63868 x17 0000f41adb324508 x18 0000000000000001 x19 0000f41a9a178f50
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: x20 0000000000000000 x21 0000000000008814 x22 0000000000000000 x23 0000000000000000
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: x24 0000f41ab3e4ef10 x25 0000000000000000 x26 0000f41ab70dc578 x27 0000f41ab0249b90
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: x28 0000000000000000 x29 0000f41abb9fdd90 x30 0000f41adabc8444
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: sp 0000f41abb9fdc50 pc 0000f41adb324510 pstate 0000000060000000
2021-06-04 09:40:23.681 4691-4708/com.antutu.benchmark.full.lite E/CRASH: backtrace:
2021-06-04 09:40:23.693 3021-3021/? I/Zygote: Process 4292 exited due to signal (9)
2021-06-04 09:40:23.814 3213-3292/system_process W/InputDispatcher: channel 'a885e65 com.antutu.benchmark.full.lite/com.example.benchmark.full.UnityPlayerActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9
2021-06-04 09:40:23.814 3213-3292/system_process E/InputDispatcher: channel 'a885e65 com.antutu.benchmark.full.lite/com.example.benchmark.full.UnityPlayerActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
2021-06-04 09:40:23.816 3213-3231/system_process W/libprocessgroup: kill(-4292, 9) failed: No such process
2021-06-04 09:40:23.816 3213-3231/system_process I/libprocessgroup: Successfully killed process cgroup uid 10019 pid 4292 in 67ms
2021-06-04 09:40:23.822 3021-3021/? I/Zygote: Process 4691 exited due to signal (11)
2021-06-04 09:40:24.036 3213-3571/system_process I/ActivityManager: Process com.android.contacts (pid 4292) has died: cch+6CEM
2021-06-04 09:40:24.069 3073-3273/? E/Sensors: Could not open (write-only) SysFs attribute "/sys/class/input/input2/fifo" (No such file or directory).
2021-06-04 09:40:24.109 3213-3356/system_process I/WindowManager: WIN DEATH: Window{a885e65 u0 com.antutu.benchmark.full.lite/com.example.benchmark.full.UnityPlayerActivity}
2021-06-04 09:40:24.222 3213-3356/system_process W/InputDispatcher: Attempted to unregister already unregistered input channel 'a885e65 com.antutu.benchmark.full.lite/com.example.benchmark.full.UnityPlayerActivity (server)'
2021-06-04 09:40:24.435 3213-3223/system_process I/system_server: Background concurrent copying GC freed 182258(5MB) AllocSpace objects, 0(0B) LOS objects, 42% free, 8MB/14MB, paused 247us total 874.850ms
2021-06-04 09:40:24.437 3038-4473/? W/audio_hw_primary: ret -32, pcm write 768 error wait error: hw 0x816600 app 0x816c00 avail 0x0
: Broken pipe
2021-06-04 09:40:24.489 3213-3571/system_process W/system_server: Long monitor contention with owner Binder:3213_4 (3356) at void com.android.server.wm.WindowState$DeathRecipient.binderDied()(WindowState.java:2447) waiters=0 in void com.android.server.wm.WindowManagerService.deferSurfaceLayout() for 281ms
2021-06-04 09:40:24.489 3213-3410/system_process W/system_server: Long monitor contention with owner Binder:3213_4 (3356) at void com.android.server.wm.WindowState$DeathRecipient.binderDied()(WindowState.java:2447) waiters=1 in void com.android.server.wm.Session.binderDied() for 264ms
2021-06-04 09:40:24.494 3213-3267/system_process W/system_server: Long monitor contention with owner Binder:3213_4 (3356) at void com.android.server.wm.WindowState$DeathRecipient.binderDied()(WindowState.java:2447) waiters=3 in void com.android.server.wm.WindowAnimator.lambda$new$1(com.android.server.wm.WindowAnimator, long) for 265ms
2021-06-04 09:40:24.494 3213-3224/system_process W/system_server: Long monitor contention with owner Binder:3213_6 (3571) at void com.android.server.am.ActivityManagerService$AppDeathRecipient.binderDied()(ActivityManagerService.java:1890) waiters=0 in void com.android.server.am.ActivityManagerService$AppDeathRecipient.binderDied() for 674ms
2021-06-04 09:40:24.495 3213-3224/system_process I/ActivityManager: Process com.antutu.benchmark.full.lite:unity (pid 4691) has died: fore TOP
2021-06-04 09:40:24.496 3213-3231/system_process W/libprocessgroup: kill(-4691, 9) failed: No such process
2021-06-04 09:40:24.496 3213-3231/system_process I/libprocessgroup: Successfully killed process cgroup uid 10066 pid 4691 in 0ms
2021-06-04 09:40:24.497 3213-3224/system_process W/ActivityManager: Force removing ActivityRecord{11bb985 u0 com.antutu.benchmark.full.lite/com.example.benchmark.full.UnityPlayerActivity t12}: app died, no saved state
2021-06-04 09:40:24.502 3076-3628/? W/SurfaceFlinger: Attempting to destroy on removed layer: AppWindowToken{5ff300b token=Token{d32b3da ActivityRecord{11bb985 u0 com.antutu.benchmark.full.lite/com.example.benchmark.full.UnityPlayerActivity t12}}}#0
2021-06-04 09:40:24.562 3213-3229/system_process W/Looper: Slow dispatch took 396ms android.ui h=com.android.server.am.ActivityManagerService$UiHandler c=null m=53
2021-06-04 09:40:24.563 3213-3229/system_process W/Looper: Slow delivery took 261ms android.ui h=com.android.server.policy.PhoneWindowManager$PolicyHandler c=com.android.server.policy.PhoneWindowManager$27@757825 m=0
2021-06-04 09:40:24.564 3213-3236/system_process W/ActivityManager: setHasOverlayUi called on unknown pid: 4691

Regards

CordialMai

Re: AnTuTu test issues on i.mx8 Android 9.0

CordialMai — Fri, 04 Jun 2021 03:38:35 GMT

add AnTuTu stuck ScreenShot

Re: AnTuTu test issues on i.mx8 Android 9.0

nxf63675 — Tue, 08 Jun 2021 05:36:26 GMT

Hi CordialMai,

Please try the new version of Android, this an issue that is not fixed on android 9 but it has no problems running on android 11.

Hope this helps you.

Regards,

Israel.

Re: AnTuTu test issues on i.mx8 Android 9.0

CordialMai — Wed, 09 Jun 2021 02:31:13 GMT

Hi nxf63675.， Thank you very much for your reply. But we have spent a lot of time on android9.0 to develop custom function. Try the new version of Android11 will cost a lot of time. Do you have any other idea to slove it ? I catch a serial log，it contains the following message： ...... .ect ...... [ 3086.660484] ************************** [ 3086.664439] *** GPU STATE DUMP *** [ 3086.668258] ************************** [ 3086.672076] axi = 0x00000070 [ 3086.675842] idle = 0x7FFFBF06 [ 3086.679480] FE not idle [ 3086.682274] SH not idle [ 3086.685270] PA not idle [ 3086.688079] SE not idle [ 3086.690872] RA not idle [ 3086.693735] TX not idle [ 3086.696625] MC not idle [ 3086.699488] DMA appears to be stuck at this address: [ 3086.704640] 0x1EC9FFC8 ...... .ect ..... I searched the community and found a similar issue： https://community.nxp.com/t5/i-MX-Processors/GPU-STATE-DUMP-DMA-appears-to-be-stuck-at-this-address/m-p/580490?commentID=812844 The detail log please see attachment ,it stucked on 图像处理FishEye window about 19:24. It seem as if it can ben sloved by upgrade GPU patch on IMX6dual JB4.3 release. So I hope I can sloved it by using the same method on i.mx8 Android 9.0. Best regard. CordialMai

Re: AnTuTu test issues on i.mx8 Android 9.0

CordialMai — Wed, 09 Jun 2021 02:44:59 GMT

Hi nxf63675,

I am sorry for the above reply is confusing, please ignore it.

Thank you very much for your reply.

But we have spent a lot of time on android9.0 to develop custom function. Try the new version of Android11 will cost a lot of time.

Do you have any other idea to slove it ?

I catch a serial log，it contains the following message：

...

[ 3086.660484] **************************

[ 3086.664439] *** GPU STATE DUMP ***

[ 3086.668258] **************************

[ 3086.672076] axi = 0x00000070

[ 3086.675842] idle = 0x7FFFBF06

[ 3086.679480] FE not idle

[ 3086.682274] SH not idle

[ 3086.685270] PA not idle

[ 3086.688079] SE not idle

[ 3086.690872] RA not idle

[ 3086.693735] TX not idle

[ 3086.696625] MC not idle

[ 3086.699488] DMA appears to be stuck at this address:

[ 3086.704640] 0x1EC9FFC8

...

I searched the community and found a similar issue：

https://community.nxp.com/t5/i-MX-Processors/GPU-STATE-DUMP-DMA-appears-to-be-stuck-at-this-address/m-p/580490?commentID=812844

The detail log please see attachment 'antutu_serial_log.log' ,it stucked on 图像处理FishEye window about 19:24.

It seem as if it can ben sloved by upgrade GPU patch on IMX6dual JB4.3 release.

So I hope I can sloved it by using the same method on i.mx8 Android 9.0.

Best regard.

CordialMai

topic Re: AnTuTu test issues on i.mx8 Android 9.0 in i.MX Processors

AnTuTu test issues on i.mx8 Android 9.0

Re: AnTuTu test issues on i.mx8 Android 9.0

Re: AnTuTu test issues on i.mx8 Android 9.0

Re: AnTuTu test issues on i.mx8 Android 9.0

Re: AnTuTu test issues on i.mx8 Android 9.0