Android L5.1.1_2.1.0 cat log will show error message

[felixhsu]

Hi All

My customer use android L5..1.1_2.1.0 cat log will show error message, detail procedure as below

Hardware : MCIMX6Q-SDP

Software : android_L5.1.1_2.1.0_full_image_6dqsabresd (pre-build)

Step1 :

Uboot boot parameter

setenv bootargs console=ttymxc0,115200 init=/init video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off vmalloc=256M androidboot.console=ttymxc0 consoleblank=0 androidboot.hardware=freescale cma=384M androidboot.selinux=disabled androidboot.dm_verity=disabled

Step2 :

Waiting boot complete, android show home page on the screen,  then key in command in the console

logcat | grep -e cutils-trace -e memtrack

Final:

Will show error message

root@sabresd_6dq:/ # logcat | grep -e cutils-trace -e memtrack

E/cutils-trace(  203): Error opening trace file: Permission denied (13)

E/cutils-trace(  385): Error opening trace file: Permission denied (13)

E/cutils-trace(  213): Error opening trace file: No such file or directory (2)

E/memtrack(  213): Couldn't load memtrack module (No such file or directory)

E/android.os.Debug(  213): failed to load memtrack module: -2

E/cutils-trace(  208): Error opening trace file: Permission denied (13)

PS:don't execution any application.

This error message will have any problems?

Thanks.

[gary_bisson · Accepted solution]

Hi Felix,

Those error messages can be ignored. Here are the details:

- cutils-trace(  208): Error opening trace file: Permission denied

This issue comes from the atrace util because it can't open /sys/kernel/debug/tracing/trace_marker

Cross Reference: /system/core/libcutils/trace.c

It is only necessary if you need/want to use atrace/systrace. To do so you need to enable the tracing options in your kernel configuration, then the message will disappear and the OS will be able to trace every system call.

- memtrack(  213): Couldn't load memtrack module (No such file or directory)

Indeed the release doesn't include a memtrack HAL layer:

Cross Reference: /system/core/libmemtrack/memtrack.c

This is not mandatory at all, here is what memtrack HAL is about:

"The Memory Tracker HAL is designed to return information about device-specific memory usage.  The primary goal is to be able to track memory that is not trackable in any other way, for example texture memory that is allocated by a process, but not mapped in to that process' address space. A secondary goal is to be able to categorize memory used by a process into GL, graphics, etc.  All memory sizes should be in real memory usage, accounting for stride, bit depth, rounding up to page size, etc."

Cross Reference: /hardware/libhardware/include/hardware/memtrack.h

Hope this answers your question.

Regards,

Gary