partition mount is broken for JellyBean4.2

Reported by Yongqin Liu on 2012-11-29
32
This bug affects 2 people
Affects Status Importance Assigned to Milestone
LAVA Dispatcher
High
Yongqin Liu
Linaro Android
High
Yongqin Liu

Bug Description

The system partition is not mount correctly for JellyBean4.2.
like:
https://validation.linaro.org/lava-server/scheduler/job/40324/log_file

This is because the partition mount information is moved to fstab.properties file
And here is some information from bhoj:

<liuyq> bhoj, do all the boards use the fstab.partitions file to mount, or they use separate file?
<bhoj> liuyq, can you parse fstab.* file
<bhoj> liuyq, we will be adding a cleanup to look at fstab.<ro.hardware> which would map to fstab.omap4pandaboard fstab.origen etc .
<liuyq> bhoj, ok, I see. but for now, it is just the fstab.partitions file right?
<bhoj> liuyq, yes
<liuyq> bhoj, do you have plan when will change to use fstab.<ro.hardware>?
<bhoj> liuyq, sometime in 12.12 .
<liuyq> bhoj, ok, will check if we can change to support that easily

Related branches

Yongqin Liu (liuyq0307) wrote :

Hope the modification of this can be deployed as soon as possible.
otherwise we can not do the test jobs with lava.

Changed in linaro-android:
status: New → In Progress
Changed in lava-dispatcher:
status: New → In Progress
Changed in linaro-android:
assignee: nobody → Yongqin Liu (liuyq0307)
Changed in lava-dispatcher:
assignee: nobody → Yongqin Liu (liuyq0307)
milestone: none → 2012.12
Changed in linaro-android:
milestone: none → 12.12
Changed in lava-dispatcher:
importance: Undecided → High
Changed in linaro-android:
importance: Undecided → High
Yongqin Liu (liuyq0307) on 2012-11-30
Changed in lava-dispatcher:
status: In Progress → Fix Committed
Changed in linaro-android:
status: In Progress → Fix Committed
Andy Doan (doanac) on 2012-12-03
Changed in lava-dispatcher:
status: Fix Committed → Fix Released
Fathi Boudra (fboudra) on 2012-12-20
Changed in linaro-android:
status: Fix Committed → Fix Released
Soumya Basak (soumya-basak) wrote :

observed with panda linaro android stable image:
image url: https://android-build.linaro.org/jenkins/job/linaro-android_panda-jb-gcc47-tilt-stable-blob/148/
job id: http://validation.linaro.org/lava-server/scheduler/job/42476
complete log: http://validation.linaro.org/lava-server/scheduler/job/42476/log_file
log:
due to kernel panic the booting is abort from the log:

[ 5.922668] EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=panic
[ 5.975677] android_usb: already disabled
[ 5.980499] adb_bind_config
[ 6.079376] Disabling lock debugging due to kernel taint

failed to boot-test image getting from the log:

version: 2.4 ($Revision: 516 $)
command: /usr/bin/telnet
args: [u'/usr/bin/telnet', u'serial2', u'7018']
searcher: searcher_re:
    0: re.compile("root@linaro# ")
buffer (last 100 chars): size 12-0
[ 116.351287] binder: send failed reply for transaction 7816, target dead

Lava failed at action boot_linaro_android_image with error:Failed to boot test image.
Traceback (most recent call last):
  File "/srv/lava/.cache/eggs/lava_dispatcher-0.27-py2.7.egg/lava_dispatcher/job.py", line 177, in run
    action.run(**params)
  File "/srv/lava/.cache/eggs/lava_dispatcher-0.27-py2.7.egg/lava_dispatcher/actions/boot_control.py", line 51, in run
    raise CriticalError("Failed to boot test image.")
CriticalError: Failed to boot test image.

Yongqin Liu (liuyq0307) wrote :

The above error is not related to this bug.

[ 5.922668] EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=panic
is information from the first boot, and there are some test executed after that,
so we can consider this information as not a problem

And the job is failed due to the failure of the boot_linaro_android_image action.
after run "netcfg eth0 dhcp", there was no response returned.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers