SABRE SDP Android jb4.2.2_1.1.0 boot issue?

[piyushagrawal]

Hi All,       

          I am trying to boot SDP platform using the Android jb4.2.2_1.1.0 bundle per-built image by SD card, I don't know why but some process are continuously crashing. Attached is the log file captured from Minicom.

Original Attachment has been moved to: Logs.txt.zip

[rreay]

Same issue: I've followed the instructions from the Android Users Guide (Document Number:AQSUG Rev jb4.2.2_1.1.0-GA, 07/2013) to configure, load, and boot an SPD board from the prebuilt images on an SD card and get the same error as piyushagrawal

I don't see anything relevant in the FAQ

It looks like two processes that are crashing are:

/system/bin/mediaserver

/system/bin/netd

Thoughts?

[rreay]

The same pre-built images boot fine when installed via MfgTool2.exe.  This isn't ideal as I would prefer not to have to use windows to install my system, but at least it's a workaround.

[benyongshi]

I am having the exact problems. Any solutions? Thanks

[LeonardoSandova]

what is the crash you are referring to? I did not see it on the log.

[BernardDAUTREVA]

Hi leonardo,

I have the exact same problem, in a slightly different configuration.

I rebuild the 4.2.2_1.1.0-ga Android release and try to boot it from the network (downloading the kernel through TFTP and booting with the root filesystem on NFS).

The Linux kernel is booting correctly and I get a shell on the serial line; however the Zygote process seems to crash regularly (about every 30 seconds) so that killed the mediaserver and netd daemons to restart them when the zygorte is restarted by init, and thus I get stuck at the shining ANDROID logo forever... ;-(

Note I comment out everything in /fstab.freescale (as I have everything on my NFS root filesystem) and avoid remounting / read-only.

The start of the console output (just after mounting the root filesystem) is as follows:

VFS: Mounted root (nfs filesystem) on device 0:12.

Freeing init memory: 244K

init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'

android_usb: already disabled

android_usb: already disabled

mtp_bind_config

adb_bind_config

adb_open

input: eCompass as /devices/virtual/input/input9

root@android:/ # eth0: no IPv6 routers present

imx-ipuv3 imx-ipuv3.0: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

warning: `zygote' uses 32-bit capabilities (legacy support in use)

request_suspend_state: wakeup (3->0) at 79420332679 (2013-08-15 19:39:25.669813677 UTC)

init: untracked pid 2310 exited

init: untracked pid 2315 exited

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

request_suspend_state: wakeup (0->0) at 106990319682 (2013-08-15 19:39:53.239801013 UTC)

init: untracked pid 2621 exited

init: untracked pid 2622 exited

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

I've checked the mounted filesystems and everything seems OK:

root@android:/ # mount

rootfs / rootfs rw 0 0

192.168.233.1:/tftpboot/rootfs-sabresd_6dq/ / nfs rw,relatime,vers=2,rsize=4096,wsize=4096,namlen=255,hard,nolock,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.233.1,mountvers=1,mountproto=udp,local_lock=all,addr=192.168.233.1 0 0

tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0

devpts /dev/pts devpts rw,relatime,mode=600 0 0

proc /proc proc rw,relatime 0 0

sysfs /sys sysfs rw,relatime 0 0

none /acct cgroup rw,relatime,cpuacct 0 0

tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0

tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/shm tmpfs rw,relatime,size=1024k,mode=775,uid=1000,gid=1003 0 0

none /dev/cpuctl cgroup rw,relatime,cpu 0 0

none /sys/kernel/debug debugfs rw,relatime 0 0

root@android:/ #

Have you any Idea on what could cause teh Zygote to crash unexpectedy?

Thanks in advance for any hint,

Bernard

[brajeshsharma]

Hi ,

I am having the same problem , after boot up i am stuck with shining Android logo and nothing comes up after that . But i have not used NFS so adding those nfs related lines wont help i guess . But i am getting the same errors and console also . If have you figured it out can you please help me in that .

Any help would be appreciated

Regards

Brajesh

[BernardDAUTREVA]

After looking at the differences between the prebuilt images and the image I generated by recompiling from the source code, I discover that the init.rc and init.freescale.rc were different...

Mainly the prebuilt images:

*    Include a line with

          setprop ro.nfs.mode yes

     in init.freescale.rc in the boot section

*    Start the late_start services in init.rc boot rection, just after starting class main, by:

          class_start late_start

Adding these two lines in my init files seems to solve the problem, although Android boot very slowly...

It is quite disturbing that the provided source file do not allow to directly rebuild the prebuilt-image.

Note that there is a difference that I needed in the configuratyion, that is to build an "eng" image and not an "user" one like the prebuilt image... (in the default.prop file, the android system is put in "secure" non-debuggable mode).

Bernard

[piyushagrawal]

Hi Leonardo,

          I think some process is crashing continuously.

init: untracked pid 2344 exited

init: untracked pid 2349 exited

request_suspend_state: wakeup (0->0) at 33160331006 (1970-01-02 00:09:07.436137003 UTC)

init: untracked pid 2660 exited

init: untracked pid 2659 exited

request_suspend_state: wakeup (0->0) at 45920327341 (1970-01-02 00:09:20.196133339 UTC)

init: untracked pid 2909 exited

init: untracked pid 2908 exited

According to you what could be the possible cause of boot failure?