On Mon, Jun 4, 2012 at 5:59 PM, S, Venkatraman <[email protected]> wrote:
> Deepti, > On Mon, Jun 4, 2012 at 2:32 PM, Deepti Kalakeri > <[email protected]> wrote: > > Hello Deepak/Andrey, > > > > Building the omap2 defconfig kernel for armhf instead of armel seemed to > fix > > the omap2 defconfig boot issues previously mentioned in bug 972191. > > The omap2_defconfig builds boot fine on panda boards, but the kernel > built > > is now failing to boot on beagle boards because of Kernel panic. > > The Kernel trace can be found in the log > > > http://validation.linaro.org/lava-server/scheduler/job/21290/log_file#entry6 > . > > This gives me a 404 > You should be part of the "linaro" group and need to login to the validation.linaro.org using your lp account to access the boot log. For membership you can speak to lool or doanac. > > > Here is the job which was > > > https://ci.linaro.org/jenkins/job/linux-linaro-tracking_beagle-omap2plus/84/consoleFull > . > > This is a build log, not the the boot log. I followed the downstream > jobs without much success.. > Any help on this ? > > Is this a known issue ? > > > > > > On Tue, May 15, 2012 at 7:57 AM, Deepak Saxena <[email protected]> > wrote: > >> > >> On 11 May 2012 08:03, Andy Doan <[email protected]> wrote: > >> > +1 the LAVA team > >> > > >> > > >> > On 05/11/2012 06:56 AM, Deepti Kalakeri wrote: > >> >> > >> >> On Fri, May 11, 2012 at 4:19 PM, Venkatraman S <[email protected] > >> >> <mailto:[email protected]>> wrote: > >> >> > >> >> Checked that log. The boot log seems to be okay from the kernel. > The > >> >> rootfs was mounted and fsck also succeeded. > >> >> > >> >> 2 interesting sections:- > >> >> > >> >> 1) mount: mounting udev on /dev failed: No such device > >> >> W: devtmpfs not available, falling back to tmpfs for /dev > >> >> > >> >> Do your scripts depend on udev ? > >> >> > >> >> > >> >> Not my scripts, but I guess the linaro-media-create used on LAVA > does. > >> > > >> > > >> > Here's is a link to the scheduler's view of this, which is a little > >> > easier > >> > to read and has details like the job time out. > >> > > >> > http://validation.linaro.org/lava-server/scheduler/job/18287 > >> > >> That still doesn't quite give me enough information. Both this and the > >> other log are confusing b/c as Venkat pointed out, it appears that the > >> kernel booted OK and mounted the rootfs. Is there a log of what > >> commands are actually run on the target with their respective outputs? > >> > >> ~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 > > [email protected] > > http://lists.linaro.org/mailman/listinfo/linaro-kernel > > > -- 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-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
