+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 <venkat@linaro.org mailto:venkat@linaro.org> 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
On 11 May 2012 08:03, Andy Doan andy.doan@linaro.org 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 <venkat@linaro.org mailto:venkat@linaro.org> 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
W dniu 15.05.2012 04:27, Deepak Saxena pisze:
On 11 May 2012 08:03, Andy Doan andy.doan@linaro.org 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 <venkat@linaro.org mailto:venkat@linaro.org> 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?
In lava-core, yes, in lava-dispatcher, no.
I cannot help you more than others did: the log is confusing (I re-wrote the dispatcher, in part, to address that), here it seems that after the reboot to the test image, lava decided that everything failed, since there are no timestamps on the messages it's hard to track
the reboot was requested at 07:52:36 and the system failed at 07:57:57 so 5 minutes later
It seems that fsck was checking the card at that time, seeing timestamps from the future (yay for test images that don't know what time it is).
That's about it Thanks ZK
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 . Here is the job which was https://ci.linaro.org/jenkins/job/linux-linaro-tracking_beagle-omap2plus/84/... . Is this a known issue ?
On Tue, May 15, 2012 at 7:57 AM, Deepak Saxena dsaxena@linaro.org wrote:
On 11 May 2012 08:03, Andy Doan andy.doan@linaro.org 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 <venkat@linaro.org mailto:venkat@linaro.org> 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:-
- 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
Deepti, On Mon, Jun 4, 2012 at 2:32 PM, Deepti Kalakeri deepti.kalakeri@linaro.org 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
Here is the job which was https://ci.linaro.org/jenkins/job/linux-linaro-tracking_beagle-omap2plus/84/....
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 dsaxena@linaro.org wrote:
On 11 May 2012 08:03, Andy Doan andy.doan@linaro.org 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 <venkat@linaro.org mailto:venkat@linaro.org> 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/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
On Mon, Jun 4, 2012 at 5:59 PM, S, Venkatraman svenkatr@ti.com wrote:
Deepti, On Mon, Jun 4, 2012 at 2:32 PM, Deepti Kalakeri deepti.kalakeri@linaro.org 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/... .
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 dsaxena@linaro.org
wrote:
On 11 May 2012 08:03, Andy Doan andy.doan@linaro.org 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 <venkat@linaro.org mailto:venkat@linaro.org> 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:-
- 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/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
On 06/04/2012 08:07 AM, Deepti Kalakeri wrote:
> 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 404You should be part of the "linaro" group and need to login to the validation.linaro.org http://validation.linaro.org using your lp account to access the boot log. For membership you can speak to lool or doanac.
He's already a member of Linaro in Launchpad, so logging into validationn.linaro.org should make that link visible.
linaro-validation@lists.linaro.org
-
Andy Doan -
Deepak Saxena -
Deepti Kalakeri -
S, Venkatraman -
Zygmunt Krynicki