bigLITTLE system halted after boot

[Naresh Kamboju]

I have booted RTSM fastmodel with the latest vexpress-rtsm-isw android image and found below issue.

root@android:/ # bl-agitator -n 0 1 2 3 -s 10 &
[ 36.185726] init: critical process 'servicemanager' exited 4 times in 4 minutes; rebooting into recovery mode
[ 36.249583] SysRq : Emergency Remount R/O
[ 36.259417] EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)
[ 36.280243] EXT4-fs (mmcblk0p5): re-mounted. Opts: (null)
[ 36.308813] Emergency Remount complete
[ 36.379368] Disabling non-boot CPUs ...
[ 36.398105] CPU1: shutdown
[ 36.405387] Restarting system with command 'recovery'.
[ 36.415542] v2m_cfg_write: writing 00000000 to 00900000
[ 36.425948] Unable to reboot
[ 37.432356] Reboot failed -- System halted

Linux version
-------------------
Linux version 3.6.3+ (jenkins-build@ip-10-40-119-136) (gcc version 4.7.2 20120731 (prerelease) (Linaro GCC 4.7-2012.08) ) #1 SMP Thu Oct 25 01:33:32 UTC 2012

Android image:
---------------------
https://android-build.linaro.org/builds/~linaro-android-restricted/vexpress-rtsm-isw-jb-gcc47-armlt-stable-open/#build=82

complete log:
------------------
boot log:
https://pastebin.linaro.org/1036/
Error log:
https://pastebin.linaro.org/1035/

[Naresh Kamboju (naresh-kamboju)]

kernel config

[Naresh Kamboju (naresh-kamboju)]

kernel_config_diff

[Naresh Kamboju (naresh-kamboju)]

ftrace-enable-bug

[Naresh Kamboju (naresh-kamboju)]

without bl-agitator also system halted.

[Naresh Kamboju (naresh-kamboju)]

same issue has been reported with latest Android Build please find lava log here
http://validation.linaro.org/lava-server/scheduler/job/38516/log_file

Issue has not reported with Ubuntu build.
-Naresh Kamboju

[Naresh Kamboju (naresh-kamboju)]

bug title has been modified.

[Naresh Kamboju (naresh-kamboju)]

 Build #106 which has included with latest dmart fixes.
https://android-build.linaro.org/builds/~linaro-android-restricted/vexpress-rtsm-isw-jb-gcc47-armlt-stable-open/#build=106

But the test did not executed on lava
here the observation is that file System mount is not happened.
"mmcblk0: p1 p2 p3 p4 < p5 p6 >" This step is missing. IIUC.

Log:
http://validation.linaro.org/lava-server/scheduler/job/38516/log_file

[Naresh Kamboju (naresh-kamboju)]

 Build #106 which has included with latest dmart fixes.
https://android-build.linaro.org/builds/~linaro-android-restricted/vexpress-rtsm-isw-jb-gcc47-armlt-stable-open/#build=106

But the test did not executed on lava
here the observation is that file System mount is not happened.
"mmcblk0: p1 p2 p3 p4 < p5 p6 >" This step is missing. IIUC.

Log:
latest Failure log:
http://validation.linaro.org/lava-server/scheduler/job/39460/log_file

Old failure log:
http://validation.linaro.org/lava-server/scheduler/job/38516/log_file

[Dave Martin (dave-martin-arm)]

Can you give me a pointer to the images for reproducing this failure?

It looks like the MMC image is not detected in the second case, but
we do reach userspace.

The kernel might have crashed, but we might also just be waiting forever
for MMC partitions which never appear. It looks from the log that the
MMC image was generated correctly though.

Cheers
---Dave

[Naresh Kamboju (naresh-kamboju)]

The issue has been appeared yesterday with Buil#106.
https://android-build.linaro.org/builds/~linaro-android-restricted/vexpress-rtsm-isw-jb-gcc47-armlt-stable-open/#build=106
Log:
http://validation.linaro.org/lava-server/scheduler/job/39460/log_file

Bug has been disappeared with build#107, which vishal has tested.
Log:
 https://validation.linaro.org/lava-server/scheduler/job/39557/log_file

I am not sure the diff of 106 and 107 build, however the bug has been disappeared now :)

-Naresh Kamboju