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.
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.gzhttp://snapshots.linaro.org/kernel-hwpack/linux-linaro-tracking/linux-linaro-tracking_panda-omap2plus/hwpack_linaro-lt-panda_20120509-0641_b64_armel_supported.tar.gz
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 ?
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-o... . Can someone look at these linux-next build failures ?
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.
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.
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-o.... 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
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.
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... . You need to click on Inline Viewer tab to see the console messages http://validation.linaro.org/lava-server/dashboard/streams/public/personal/c...
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-o... .
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
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.... You need to click on Inline Viewer tab to see the console messages http://validation.linaro.org/lava-server/dashboard/streams/public/personal/c...
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 ?
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-o.... 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/#%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 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.... You need to click on Inline Viewer tab to see the console messages http://validation.linaro.org/lava-server/dashboard/streams/public/personal/c...
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-o.... 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/#%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 11 May 2012 13:47, Venkatraman S venkat@linaro.org wrote:
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.... You need to click on Inline Viewer tab to see the console messages http://validation.linaro.org/lava-server/dashboard/streams/public/personal/c...
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.
Purely a conjecture - looking at the EXYNOS logs which shows that that the rootfs is on a ext4, and omap2plus_defconfig doesn't have ext4 by default, the boot up just borks when trying to mount a ext4fs.
Will wait for your link to the correct logs ..
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-o.... 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/#%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 11 May 2012 11:32, Venkatraman S venkat@linaro.org wrote:
On 11 May 2012 13:47, Venkatraman S venkat@linaro.org wrote:
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.... You need to click on Inline Viewer tab to see the console messages http://validation.linaro.org/lava-server/dashboard/streams/public/personal/c...
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.
Purely a conjecture - looking at the EXYNOS logs which shows that that the rootfs is on a ext4, and omap2plus_defconfig doesn't have ext4 by default, the boot up just borks when trying to mount a ext4fs.
Will wait for your link to the correct logs ..
http://validation.linaro.org/lava-server/scheduler/job/18683/log_file/plain http://validation.linaro.org/lava-server/dashboard/permalink/test-run/e6e429...
The easiest way is to go on http://validation.linaro.org/lava-server/scheduler/alljobs , use the search filter "omap2plus" and click on latest incomplete job.
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-o.... 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/#%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
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel
On Fri, May 11, 2012 at 2:02 PM, Venkatraman S venkat@linaro.org wrote:
On 11 May 2012 13:47, Venkatraman S venkat@linaro.org wrote:
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.
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... .
You need to click on Inline Viewer tab to see the console messages
http://validation.linaro.org/lava-server/dashboard/streams/public/personal/c...
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.
Purely a conjecture - looking at the EXYNOS logs which shows that that the rootfs is on a ext4, and omap2plus_defconfig doesn't have ext4 by default, the boot up just borks when trying to mount a ext4fs.
I have tried enabling the following config option on top of default and tested the build, but it still had the same problem:
"CONFIG_ARCH_OMAP2=n" "CONFIG_THUMB2_KERNEL=y" "CONFIG_CACHE_PL310=y" "CONFIG_THUMB2_AVOID_R_ARM_THM_JUMP11=y" "CONFIG_ARM_ASM_UNIFIED=y" "CONFIG_DEVTMPFS=y" "CONFIG_DEVTMPFS_MOUNT=y" "CONFIG_EXT2_FS=y" "CONFIG_EXT3_FS=y" "CONFIG_EXT4_FS=y"
Are there any other options along with above that needs to be enabled?
Will wait for your link to the correct logs ..
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-o... .
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/#%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 Fri, May 11, 2012 at 1:47 PM, Venkatraman S venkat@linaro.org wrote:
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.
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... .
You need to click on Inline Viewer tab to see the console messages
http://validation.linaro.org/lava-server/dashboard/streams/public/personal/c...
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.
Pure copy paste error, too many tabs open and I copied a wrong link. Here is a correct one:
http://validation.linaro.org/lava-server/dashboard/streams/public/personal/c...
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-o... .
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/#%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
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 ?
2) Can't decipher what the script interpreted as a fail .. Is it a timeout on something ? login prompt ?
Lava failed at action boot_linaro_image with error: Failed to boot test image. Traceback (most recent call last): File "/srv/lava/instances/production/local/lib/python2.7/site-packages/lava_dispatcher/job.py", line 146, in run action.run(**params) File "/srv/lava/instances/production/lib/python2.7/site-packages/lava_dispatcher/actions/boot_control.py", line 57, in run raise CriticalError("Failed to boot test image.") CriticalError: Failed to boot test image.
On 11 May 2012 14:33, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
On Fri, May 11, 2012 at 1:47 PM, Venkatraman S venkat@linaro.org wrote:
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.... You need to click on Inline Viewer tab to see the console messages
http://validation.linaro.org/lava-server/dashboard/streams/public/personal/c...
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.
Pure copy paste error, too many tabs open and I copied a wrong link. Here is a correct one:
http://validation.linaro.org/lava-server/dashboard/streams/public/personal/c...
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-o.... 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/#%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
-- 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
On Fri, May 11, 2012 at 4:19 PM, Venkatraman S 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.
- Can't decipher what the script interpreted as a fail .. Is it a
timeout on something ? login prompt ?
Lava failed at action boot_linaro_image with error: Failed to boot test image. Traceback (most recent call last): File "/srv/lava/instances/production/local/lib/python2.7/site-packages/lava_dispatcher/job.py", line 146, in run action.run(**params) File "/srv/lava/instances/production/lib/python2.7/site-packages/lava_dispatcher/actions/boot_control.py", line 57, in run raise CriticalError("Failed to boot test image.") CriticalError: Failed to boot test image.
On 11 May 2012 14:33, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
On Fri, May 11, 2012 at 1:47 PM, Venkatraman S venkat@linaro.org
wrote:
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... .
You need to click on Inline Viewer tab to see the console messages
http://validation.linaro.org/lava-server/dashboard/streams/public/personal/c...
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.
Pure copy paste error, too many tabs open and I copied a wrong link. Here is a correct one:
http://validation.linaro.org/lava-server/dashboard/streams/public/personal/c...
> 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-o... .
> 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/#%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
-- 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
+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-kernel@lists.linaro.org
-
Andy Doan -
Deepak Saxena -
Deepti Kalakeri -
Fathi Boudra -
S, Venkatraman -
Venkatraman S -
Zygmunt Krynicki