CI hwpack on lava fail to boot on the boards
Bug #972191 reported by
Deepti B. Kalakeri
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro CI |
Fix Released
|
Medium
|
Deepti B. Kalakeri |
Bug Description
The hwpacks generated by CI does not boot on the lava boards.
Fix the hwpack problems if any from the CI side.
Here is the traceback of the lava for the boot test
Lava failed at action boot_linaro_image with error: Failed to boot test image.\nTraceback (most recent call last):\n File \"/srv/
Related branches
Changed in linaro-ci: | |
assignee: | nobody → Deepti B. Kalakeri (deeptik) |
milestone: | none → 2012.04 |
importance: | Undecided → Medium |
Changed in linaro-ci: | |
milestone: | 2012.04 → 2012.05 |
Changed in linaro-ci: | |
status: | New → In Progress |
Changed in linaro-ci: | |
milestone: | 2012.05 → 2012.06 |
To post a comment you must log in.
With the omap2plus defconfig , my hwpack seems to get stuck at various points with diff config options, with the default upstream omap2 defconfig my hwpack seems to hang @ http:// pastebin. ubuntu. com/942328/. With the following omap2plus config options http:// pastebin. ubuntu. com/942386/, the hwpack fails to boot @ http:// pastebin. ubuntu. com/942414/ .
Between, with the default omap4_defconfig available in the linux linaro tracking tree the hwpack is able to boot on the board when ethernet port is connected and otherwise the boot process keeps waiting at the point where it searches for the ethernet connection to be up when ethernet port is not connected( I tested this on panda only).
Also, I was speaking to Andrey today, he was suggesting that we should use the default omap4 defconfig to build arm-soc , linux(master), linux-next as well. I am in discussion with Ricardo, Andrey to check if we need to continue with the omap2plus defconfig builds or just have omap4 defconfig.
Thanks!!!
Deepti.