On 11 May 2012 13:44, Venkatraman S <venkat@linaro.org> wrote:
> On 11 May 2012 11:59, Deepti Kalakeri <deepti.kalakeri@linaro.org> wrote:
>>
>>
>> On Fri, May 11, 2012 at 10:25 AM, Deepak Saxena <dsaxena@linaro.org> wrote:
>>>
>>> On 9 May 2012 12:40, Deepti Kalakeri <deepti.kalakeri@linaro.org> wrote:
>>> > Hello,
>>> >
>>> > Its been close to a month now that the kernel CI hwpacks built on
>>> > ci.linaro.org with default omap2plus defconfigs
>>> > (available in the linux-arm-soc, linux-next, linux-linaro, linux) are
>>> > failing to boot on the boards.
>>>
>>> Thanks for the update Deepti.
>>>
>>> >
>>> > Here is an example hwpack built using the linux-linaro tree with
>>> > omap2plus
>>> > defconfig on ci.linaro.org which is failing to boot, in case you want to
>>> > try
>>> > to test it.
>>> >
>>> > http://snapshots.linaro.org/kernel-h
>>> >
>>> > wpack/linux-linaro-tracking/linux-linaro-tracking_panda-omap2plus/hwpack_linaro-lt-panda_20120509-0641_b64_armel_supported.tar.gz
>>>
>>> Is it possible to just get a boot log? I've tried looking through
>>> ci.linaro.org and not quite sure where I can just pull that out.
>>
>>
>> Here is the boot log for the boot test run by LAVA, this is not for the
>> above hwpack, but is a similar error which is produced by
>> http://snapshots.linaro.org/kernel-hwpack/linux-linaro-tracking/linux-linaro-tracking_panda-omap2plus/hwpack_linaro-lt-panda_20120508-0637_b63_armel_supported.tar.gz.
>> You need to click on Inline Viewer tab to see the console messages
>> http://validation.linaro.org/lava-server/dashboard/streams/public/personal/ciadmin/ci-linux-linaro-tracking/bundles/a2eb08c544838bc5c44d35c831aa46ba3a70a9a2/7f1538aa-9844-11e1-9729-68b599be548c/attachments/71973/
>>>
>
> The inline viewer just hangs for me and I can't seem to download the
> file. Just trying to click the serial.log file just opens the
> Attachment information, with no option to download ?

Well, eventually it did open, but it looks like the console log of
EXYNOS4, not OMAP.

>
>
>>>
>>> > I was able to fix the  above boot problem of the CI kernel hwpacks built
>>> > with omap2plus defconfig
>>> > by adding the options similar to the ones available in (linux-linaro
>>> > tree)
>>> > default omap4 defconfig on top of the default
>>> > omap2plus defconfig options.
>>> >
>>> > Here is the list of the config options which I added
>>> > http://paste.ubuntu.com/977642/ along with the omap2plus
>>> > defconfig to make it work.
>>> >
>>> > Can someone help me with the basic omap2plus defconfig options that will
>>> > be
>>> > required to boot the  hwpack on the board.
>>> > Does anyone care of kernel builds for linux-arm-soc, linux-next,
>>> > linux-linaro, linux tree using omap2plus defconfigs ?
>>>
>>> The answer is that someone should care, ideally Tony L. the OMAP
>>> maintainer and I will ping him to start looking at results.
>>>
>>
>> That would be great, I have created a bug 972191 for tracking this problem,
>> in case you want to update the bug.
>>>
>>> >
>>> > Apart from this, there are build failures with the linux-next trees
>>> > failing
>>> > since last 20 days.
>>> > https://ci.linaro.org/jenkins/view/Linux%20%28next%29/ lists such
>>> > failing
>>> > build jobs.
>>> > For example the following job fails
>>> >
>>> > https://ci.linaro.org/jenkins/view/Linux%20%28next%29/job/linux-next_panda-omap2plus/.
>>> > Can someone look at these linux-next build failures ?
>>>
>>> I grabbed today's -next and reproduced the issue, which turns out to
>>> be related to 'make deb-pkg'. I'll dig into it.
>>>
>>>
>>> ~Deepak
>>
>>
>>
>>
>> --
>> Thanks and Regards,
>> Deepti
>> Infrastructure Team Member, Linaro Platform Teams
>> Linaro.org | Open source software for ARM SoCs
>> Follow Linaro: http://www.facebook.com/pages/Linaro
>> http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
>>
>>
>>
>> _______________________________________________
>> linaro-kernel mailing list
>> linaro-kernel@lists.linaro.org
>> http://lists.linaro.org/mailman/listinfo/linaro-kernel
>>