boot test fail with Linaro-android jellybean snowball builds

Bug #1192548 reported by Soumya Basak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Android
Fix Released
Critical
Axel Fagerstedt

Bug Description

on my side with snowball board with latest available Linaro Android image:
https://android-build.linaro.org/builds/~linaro-android-member-ste/snowball-linaro-jb/#build=332

the boot test is fail. No display on HDMI

some error is observed from the boot log:

[ 3.439025] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
[ 3.610809] init: cannot open '/initlogo.rle'
[ 3.708465] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
[ 3.861297] EXT4-fs (mmcblk1p3): mounted filesystem with ordered data mode. Opts: (null)
[ 4.016479] EXT4-fs (mmcblk1p5): mounted filesystem with ordered data mode. Opts: (null)
[ 4.046997] android_usb: already disabled
[ 4.158752] init: cannot find '/system/bin/rild', disabling 'ril-daemon'
[ 4.200897] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
[ 4.214752] init: cannot find '/system/bin/gatord', disabling 'gatord'
[ 4.222320] init: cannot find '/system/bin/hciattach', disabling 'hciattach'
[ 4.230194] init: cannot find '/system/bin/lbsd', disabling 'lbsd'

[ 6.289276] generic-usb 0003:15D9:0A4C.0001: input,hidraw0: USB HID v1.11 Mouse [ USB OPTICAL MOUSE] on usb-musb-hdrc-1/input0
[ 7.276672] init: untracked pid 1859 exited
[ 8.116546] av8100_hdmi av8100_hdmi.3: HDMI display probed
[ 8.867187] av8100_hdmi av8100_hdmi.3: Framebuffer created (av8100_hdmi)
[ 8.873901] init_dispdev: name=disp0 w=1280, h=720, fmt=0, stride=2560
[ 8.880950] av8100_hdmi av8100_hdmi.3: Disp dev created for (av8100_hdmi)
[ 9.554290] init: untracked pid 1907 exited
[ 14.843505] init: untracked pid 2072 exited
[ 19.236450] init: untracked pid 2086 exited
[ 23.447479] warning: `zygote' uses 32-bit capabilities (legacy support in use)
[ 24.543457] init: untracked pid 2101 exited
[ 24.586425] init: untracked pid 2097 exited
[ 29.894195] init: untracked pid 2122 exited
[ 29.956298] init: untracked pid 2134 exited
[ 34.270111] init: untracked pid 2155 exited
[ 34.306396] init: untracked pid 2159 exited
[ 39.608856] init: untracked pid 2184 exited

can't figure out what exactly the problem is.
complete log attached for your reference.

Revision history for this message
Soumya Basak (soumya-basak) wrote :
vishal (vishalbhoj)
Changed in linaro-android:
importance: Undecided → Critical
assignee: nobody → Axel Fagerstedt (fagerstedt-axel)
milestone: none → 13.06
Revision history for this message
Botao (botao-sun) wrote :

Double checked this boot failure on STE Snowball with Linaro Android image:

https://android-build.linaro.org/builds/~linaro-android-member-ste/snowball-linaro-jb/#build=332

Different boot log observed. There seems be something wrong about Device Tree:

reading board.dtb
** Unable to read file board.dtb **
## Booting kernel from Legacy Image at 00100000 ...
   Image Name: Linux-3.4.0+
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 4644688 Bytes = 4.4 MiB
   Load Address: 00008000
   Entry Point: 00008000
## Loading init Ramdisk from Legacy Image at 05000000 ...
   Image Name: Android Ramdisk Image
   Image Type: ARM Linux RAMDisk Image (gzip compressed)
   Data Size: 242796 Bytes = 237.1 KiB
   Load Address: 00000000
   Entry Point: 00000000
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree

Please refer to attachment to get full boot log.

Revision history for this message
Axel Fagerstedt (fagerstedt-axel) wrote :

looks like this is caused by a failure to load mali, which looks like ti might be due to incompatability between the vendor overlay and the new 4.8 toolchain.

A build with the 4.7 toolchain has been triggered.

Revision history for this message
Axel Fagerstedt (fagerstedt-axel) wrote :

Board boots ok with the new gcc 4.7 build.

Changed in linaro-android:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.