Hi Deepti
If I see the log from your attached file,
Line 399, Line 10278 both shows the success full ping message. Addition to those, there is no problem in Kernel booting message: No kernel panic, USB Ethernet recognised well.
Can I see the exact same booting log that you faced booting problem ?
Thanks Sangwook
On 10 February 2012 06:42, Deepti Kalakeri deepti.kalakeri@linaro.orgwrote:
Hello Sangwook,
On Fri, Feb 10, 2012 at 12:38 AM, Sangwook Lee sangwook.lee@linaro.orgwrote:
Hi Paul
I visited the below and then downloaded the file,but it has the broken to the link for the file serial.log Could you send me kernel log by attached file ?
FYI.. Here is the Kernel build log for the hwpack that was being tested https://ci.linaro.org/jenkins/view/Linux%20ARM%20SoC%20%28for-next%29%20CI%2....
Also, I was able to access the serial log and I have attached the same with the mail.
I saw the serial log, but it looks fine to me.
Thanks
Sangwook
On 9 February 2012 16:57, Paul Larson paul.larson@linaro.org wrote:
http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu... the link to one of the recent results
The kernel ci view page for this is at: http://validation.linaro.org/lava-server/kernel-ci-views/per_board/origen
On Thu, Feb 9, 2012 at 8:56 AM, Paul Larson paul.larson@linaro.orgwrote:
Hi, I'm looking at the kernel ci results and origen seems to be running tests pretty frequently, but always failing to boot. Sangwook, could you take a look at the args that are getting passed and make sure there's not something here that would explain it hanging on boot? Or is this perhaps something in the kernel config that is getting used?
Thanks, Paul Larson
-- 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
Hello Sangwook,
On Mon, Feb 13, 2012 at 5:09 PM, Sangwook Lee sangwook.lee@linaro.orgwrote:
Hi Deepti
If I see the log from your attached file,
Line 399, Line 10278 both shows the success full ping message. Addition to those, there is no problem in Kernel booting message: No kernel panic, USB Ethernet recognised well.
Thanks so much for looking into this.
Can I see the exact same booting log that you faced booting problem ?
I dont have an origen board myself, so I depend on the validation farm for
my testing. The details of the origen hwpack problem as shown by the lava has the following error:
1. Lava failed at action boot_linaro_image with error: Failed to boot test image. 2. Traceback (most recent call last): 3. File "/srv/lava/instances/production/local/lib/python2.7/site-packages/lava_dispatcher/job.py", line 139, in run 4. action.run(**params) 5. File "/srv/lava/instances/production/lib/python2.7/site-packages/lava_dispatcher/actions/boot_control.py", line 50, in run 6. raise CriticalError("Failed to boot test image.") 7. CriticalError: Failed to boot test image.
If you have an origen board, would you be able to test the origen hwpack http://ci.linaro.org/kernel_hwpack/linux-arm-soc-for-next/linux-arm-soc-for-... in the lava execution above and let me know if the hwpack has a problem ?
Thanks Sangwook
On 10 February 2012 06:42, Deepti Kalakeri deepti.kalakeri@linaro.orgwrote:
Hello Sangwook,
On Fri, Feb 10, 2012 at 12:38 AM, Sangwook Lee sangwook.lee@linaro.orgwrote:
Hi Paul
I visited the below and then downloaded the file,but it has the broken to the link for the file serial.log Could you send me kernel log by attached file ?
FYI.. Here is the Kernel build log for the hwpack that was being tested https://ci.linaro.org/jenkins/view/Linux%20ARM%20SoC%20%28for-next%29%20CI%2....
Also, I was able to access the serial log and I have attached the same with the mail.
I saw the serial log, but it looks fine to me.
Thanks
Sangwook
On 9 February 2012 16:57, Paul Larson paul.larson@linaro.org wrote:
http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu... the link to one of the recent results
The kernel ci view page for this is at:
http://validation.linaro.org/lava-server/kernel-ci-views/per_board/origen
On Thu, Feb 9, 2012 at 8:56 AM, Paul Larson paul.larson@linaro.orgwrote:
Hi, I'm looking at the kernel ci results and origen seems to be running tests pretty frequently, but always failing to boot. Sangwook, could you take a look at the args that are getting passed and make sure there's not something here that would explain it hanging on boot? Or is this perhaps something in the kernel config that is getting used?
Thanks, Paul Larson
-- 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
Hi Deepti
On 13 February 2012 12:26, Deepti Kalakeri deepti.kalakeri@linaro.orgwrote:
Hello Sangwook,
On Mon, Feb 13, 2012 at 5:09 PM, Sangwook Lee sangwook.lee@linaro.orgwrote:
Hi Deepti
If I see the log from your attached file,
Line 399, Line 10278 both shows the success full ping message. Addition to those, there is no problem in Kernel booting message: No kernel panic, USB Ethernet recognised well.
Thanks so much for looking into this.
Can I see the exact same booting log that you faced booting problem ?
I dont have an origen board myself, so I depend on the validation farm
for my testing. The details of the origen hwpack problem as shown by the lava has the following error:
- Lava failed at action boot_linaro_image with error: Failed to boot
test image. 2. Traceback (most recent call last): 3. File "/srv/lava/instances/production/local/lib/python2.7/site-packages/lava_dispatcher/job.py", line 139, in run 4. action.run(**params) 5. File "/srv/lava/instances/production/lib/python2.7/site-packages/lava_dispatcher/actions/boot_control.py", line 50, in run 6. raise CriticalError("Failed to boot test image.") 7. CriticalError: Failed to boot test image.
If you have an origen board, would you be able to test the origen hwpack http://ci.linaro.org/kernel_hwpack/linux-arm-soc-for-next/linux-arm-soc-for-... in the lava execution above and let me know if the hwpack has a problem ?
I can't see booting message from this hwpack. Which git are you using now for Origen board ? Are you using Samsung LT git ? ( http://git.linaro.org/gitweb?p=landing-teams/working/samsung/kernel.git%3Ba=... )
Thanks Sangwook
On 10 February 2012 06:42, Deepti Kalakeri deepti.kalakeri@linaro.orgwrote:
Hello Sangwook,
On Fri, Feb 10, 2012 at 12:38 AM, Sangwook Lee sangwook.lee@linaro.orgwrote:
Hi Paul
I visited the below and then downloaded the file,but it has the broken to the link for the file serial.log Could you send me kernel log by attached file ?
FYI.. Here is the Kernel build log for the hwpack that was being tested https://ci.linaro.org/jenkins/view/Linux%20ARM%20SoC%20%28for-next%29%20CI%2....
Also, I was able to access the serial log and I have attached the same with the mail.
I saw the serial log, but it looks fine to me.
Thanks
Sangwook
On 9 February 2012 16:57, Paul Larson paul.larson@linaro.org wrote:
http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu... the link to one of the recent results
The kernel ci view page for this is at:
http://validation.linaro.org/lava-server/kernel-ci-views/per_board/origen
On Thu, Feb 9, 2012 at 8:56 AM, Paul Larson paul.larson@linaro.orgwrote:
Hi, I'm looking at the kernel ci results and origen seems to be running tests pretty frequently, but always failing to boot. Sangwook, could you take a look at the args that are getting passed and make sure there's not something here that would explain it hanging on boot? Or is this perhaps something in the kernel config that is getting used?
Thanks, Paul Larson
-- 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
-- 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
+More information:
This is hwpack for Origen https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
On 13 February 2012 14:38, Sangwook Lee sangwook.lee@linaro.org wrote:
Hi Deepti
On 13 February 2012 12:26, Deepti Kalakeri deepti.kalakeri@linaro.orgwrote:
Hello Sangwook,
On Mon, Feb 13, 2012 at 5:09 PM, Sangwook Lee sangwook.lee@linaro.orgwrote:
Hi Deepti
If I see the log from your attached file,
Line 399, Line 10278 both shows the success full ping message. Addition to those, there is no problem in Kernel booting message: No kernel panic, USB Ethernet recognised well.
Thanks so much for looking into this.
Can I see the exact same booting log that you faced booting problem ?
I dont have an origen board myself, so I depend on the validation farm
for my testing. The details of the origen hwpack problem as shown by the lava has the following error:
- Lava failed at action boot_linaro_image with error: Failed to boot
test image. 2. Traceback (most recent call last): 3. File "/srv/lava/instances/production/local/lib/python2.7/site-packages/lava_dispatcher/job.py", line 139, in run 4. action.run(**params) 5. File "/srv/lava/instances/production/lib/python2.7/site-packages/lava_dispatcher/actions/boot_control.py", line 50, in run 6. raise CriticalError("Failed to boot test image.") 7. CriticalError: Failed to boot test image.
If you have an origen board, would you be able to test the origen hwpack http://ci.linaro.org/kernel_hwpack/linux-arm-soc-for-next/linux-arm-soc-for-... in the lava execution above and let me know if the hwpack has a problem ?
I can't see booting message from this hwpack. Which git are you using now for Origen board ? Are you using Samsung LT git ? ( http://git.linaro.org/gitweb?p=landing-teams/working/samsung/kernel.git%3Ba=... )
Thanks Sangwook
On 10 February 2012 06:42, Deepti Kalakeri deepti.kalakeri@linaro.orgwrote:
Hello Sangwook,
On Fri, Feb 10, 2012 at 12:38 AM, Sangwook Lee <sangwook.lee@linaro.org
wrote:
Hi Paul
I visited the below and then downloaded the file,but it has the broken to the link for the file serial.log Could you send me kernel log by attached file ?
FYI.. Here is the Kernel build log for the hwpack that was being tested https://ci.linaro.org/jenkins/view/Linux%20ARM%20SoC%20%28for-next%29%20CI%2....
Also, I was able to access the serial log and I have attached the same with the mail.
I saw the serial log, but it looks fine to me.
Thanks
Sangwook
On 9 February 2012 16:57, Paul Larson paul.larson@linaro.org wrote:
http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu... the link to one of the recent results
The kernel ci view page for this is at:
http://validation.linaro.org/lava-server/kernel-ci-views/per_board/origen
On Thu, Feb 9, 2012 at 8:56 AM, Paul Larson paul.larson@linaro.orgwrote:
> Hi, I'm looking at the kernel ci results and origen seems to be > running tests pretty frequently, but always failing to boot. Sangwook, > could you take a look at the args that are getting passed and make sure > there's not something here that would explain it hanging on boot? Or is > this perhaps something in the kernel config that is getting used? > > Thanks, > Paul Larson >
-- 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
-- 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
Looking at the latest results on.the kernel CI view I pointed out earlier, here is a serial.log from a recent one http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu...
You can see the test kernel starting to boot at around line 19560 and at 19660 it gets only as far as the starting kernel message, hangs, and eventually times out.
The hwpack we are booting is based on a recent origen hwpack, but replaces the kernel with the output from jenkins building the selected kernel. I'm guessing that perhaps we're missing something critical from the kernel configuration? On Feb 13, 2012 8:45 AM, "Sangwook Lee" sangwook.lee@linaro.org wrote:
+More information:
This is hwpack for Origen
https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
On 13 February 2012 14:38, Sangwook Lee sangwook.lee@linaro.org wrote:
Hi Deepti
On 13 February 2012 12:26, Deepti Kalakeri deepti.kalakeri@linaro.orgwrote:
Hello Sangwook,
On Mon, Feb 13, 2012 at 5:09 PM, Sangwook Lee sangwook.lee@linaro.orgwrote:
Hi Deepti
If I see the log from your attached file,
Line 399, Line 10278 both shows the success full ping message. Addition to those, there is no problem in Kernel booting message: No kernel panic, USB Ethernet recognised well.
Thanks so much for looking into this.
Can I see the exact same booting log that you faced booting problem ?
I dont have an origen board myself, so I depend on the validation farm
for my testing. The details of the origen hwpack problem as shown by the lava has the following error:
- Lava failed at action boot_linaro_image with error: Failed to
boot test image. 2. Traceback (most recent call last): 3. File "/srv/lava/instances/production/local/lib/python2.7/site-packages/lava_dispatcher/job.py", line 139, in run 4. action.run(**params) 5. File "/srv/lava/instances/production/lib/python2.7/site-packages/lava_dispatcher/actions/boot_control.py", line 50, in run 6. raise CriticalError("Failed to boot test image.") 7. CriticalError: Failed to boot test image.
If you have an origen board, would you be able to test the origen hwpack http://ci.linaro.org/kernel_hwpack/linux-arm-soc-for-next/linux-arm-soc-for-... in the lava execution above and let me know if the hwpack has a problem ?
I can't see booting message from this hwpack. Which git are you using now for Origen board ? Are you using Samsung LT git ? ( http://git.linaro.org/gitweb?p=landing-teams/working/samsung/kernel.git%3Ba=... )
Thanks Sangwook
On 10 February 2012 06:42, Deepti Kalakeri deepti.kalakeri@linaro.orgwrote:
Hello Sangwook,
On Fri, Feb 10, 2012 at 12:38 AM, Sangwook Lee < sangwook.lee@linaro.org> wrote:
Hi Paul
I visited the below and then downloaded the file,but it has the broken to the link for the file serial.log Could you send me kernel log by attached file ?
FYI.. Here is the Kernel build log for the hwpack that was being tested https://ci.linaro.org/jenkins/view/Linux%20ARM%20SoC%20%28for-next%29%20CI%2....
Also, I was able to access the serial log and I have attached the same with the mail.
I saw the serial log, but it looks fine to me.
Thanks
Sangwook
On 9 February 2012 16:57, Paul Larson paul.larson@linaro.org wrote:
> > http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu... the link to one of the recent results > > The kernel ci view page for this is at: > > http://validation.linaro.org/lava-server/kernel-ci-views/per_board/origen > > > On Thu, Feb 9, 2012 at 8:56 AM, Paul Larson paul.larson@linaro.orgwrote: > >> Hi, I'm looking at the kernel ci results and origen seems to be >> running tests pretty frequently, but always failing to boot. Sangwook, >> could you take a look at the args that are getting passed and make sure >> there's not something here that would explain it hanging on boot? Or is >> this perhaps something in the kernel config that is getting used? >> >> Thanks, >> Paul Larson >> > >
-- 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
-- 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
Hi Paul
On 14 February 2012 01:03, Paul Larson paul.larson@linaro.org wrote:
Looking at the latest results on.the kernel CI view I pointed out earlier, here is a serial.log from a recent one http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu...
You can see the test kernel starting to boot at around line 19560 and at 19660 it gets only as far as the starting kernel message, hangs, and eventually times out.
I think there is no option to download this log, maybe only for LAVA team.
If I download serial.log file as html, I must follow the link to serial log but again I have a broken link.
The hwpack we are booting is based on a recent origen hwpack,
from https://ci.linaro.org/jenkins/job/linux-arm-soc-for-next_origen-exynos4/260/... , https://ci.linaro.org/jenkins/job/linux-arm-soc-for-next_origen-exynos4/
I found out that LAVA is using from
- Tree: Linux ARM SoC for-next - http://git.linaro.org/git/people/arnd/arm-soc.git - Git: git://git.linaro.org/people/arnd/arm-soc.git @ for-next - defconfig: exynos4 - hwpack: origen
But the output image of kernel is v2.6.35-rcXX, it confused me. Perhaps as doing debian packaing, the name of kernel version might be changed in-properly. This is the latest mainline kernel and enough for LAVA but not from Landing team.
but replaces the kernel with the output from jenkins building the selected
kernel. I'm guessing that perhaps we're missing something critical from the kernel configuration?
Yes, That's right. I am attaching the patch to fix this problem. Unfortunately, currently this is not up-streamable. Hope that we apply this as doing debian packaing. please let me if you have further problem.
On Feb 13, 2012 8:45 AM, "Sangwook Lee" sangwook.lee@linaro.org wrote:
+More information:
This is hwpack for Origen
https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-dailyhttps://code.launchpad.net/%7Ejcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
On 13 February 2012 14:38, Sangwook Lee sangwook.lee@linaro.org wrote:
Hi Deepti
On 13 February 2012 12:26, Deepti Kalakeri deepti.kalakeri@linaro.orgwrote:
Hello Sangwook,
On Mon, Feb 13, 2012 at 5:09 PM, Sangwook Lee sangwook.lee@linaro.orgwrote:
Hi Deepti
If I see the log from your attached file,
Line 399, Line 10278 both shows the success full ping message. Addition to those, there is no problem in Kernel booting message: No kernel panic, USB Ethernet recognised well.
Thanks so much for looking into this.
Can I see the exact same booting log that you faced booting problem ?
I dont have an origen board myself, so I depend on the validation farm
for my testing. The details of the origen hwpack problem as shown by the lava has the following error:
- Lava failed at action boot_linaro_image with error: Failed to
boot test image. 2. Traceback (most recent call last): 3. File "/srv/lava/instances/production/local/lib/python2.7/site-packages/lava_dispatcher/job.py", line 139, in run 4. action.run(**params) 5. File "/srv/lava/instances/production/lib/python2.7/site-packages/lava_dispatcher/actions/boot_control.py", line 50, in run 6. raise CriticalError("Failed to boot test image.") 7. CriticalError: Failed to boot test image.
If you have an origen board, would you be able to test the origen hwpack http://ci.linaro.org/kernel_hwpack/linux-arm-soc-for-next/linux-arm-soc-for-... in the lava execution above and let me know if the hwpack has a problem ?
I can't see booting message from this hwpack. Which git are you using now for Origen board ? Are you using Samsung LT git ? ( http://git.linaro.org/gitweb?p=landing-teams/working/samsung/kernel.git%3Ba=... )
Thanks Sangwook
On 10 February 2012 06:42, Deepti Kalakeri <deepti.kalakeri@linaro.org
wrote:
Hello Sangwook,
On Fri, Feb 10, 2012 at 12:38 AM, Sangwook Lee < sangwook.lee@linaro.org> wrote:
> Hi Paul > > I visited the below and then downloaded the file,but it has the > broken to the link for the file serial.log > Could you send me kernel log by attached file ? > > FYI.. Here is the Kernel build log for the hwpack that was being tested https://ci.linaro.org/jenkins/view/Linux%20ARM%20SoC%20%28for-next%29%20CI%2....
Also, I was able to access the serial log and I have attached the same with the mail.
>
I saw the serial log, but it looks fine to me.
Thanks > Sangwook > > > > On 9 February 2012 16:57, Paul Larson paul.larson@linaro.orgwrote: > >> >> http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu... the link to one of the recent results >> >> The kernel ci view page for this is at: >> >> http://validation.linaro.org/lava-server/kernel-ci-views/per_board/origen >> >> >> On Thu, Feb 9, 2012 at 8:56 AM, Paul Larson <paul.larson@linaro.org >> > wrote: >> >>> Hi, I'm looking at the kernel ci results and origen seems to be >>> running tests pretty frequently, but always failing to boot. Sangwook, >>> could you take a look at the args that are getting passed and make sure >>> there's not something here that would explain it hanging on boot? Or is >>> this perhaps something in the kernel config that is getting used? >>> >>> Thanks, >>> Paul Larson >>> >> >> >
-- 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
-- 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 Tue, Feb 14, 2012 at 2:21 AM, Sangwook Lee sangwook.lee@linaro.orgwrote:
Hi Paul
On 14 February 2012 01:03, Paul Larson paul.larson@linaro.org wrote:
Looking at the latest results on.the kernel CI view I pointed out earlier, here is a serial.log from a recent one http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu...
You can see the test kernel starting to boot at around line 19560 and at 19660 it gets only as far as the starting kernel message, hangs, and eventually times out.
I think there is no option to download this log, maybe only for LAVA
team. If I download serial.log file as html, I must follow the link to serial log but again I have a broken link.
Yes, we need a download link there - known feature request that we'll hopefully get to soon.
but replaces the kernel with the output from jenkins building the selected
kernel. I'm guessing that perhaps we're missing something critical from the kernel configuration?
Yes, That's right. I am attaching the patch to fix this problem. Unfortunately, currently this is not up-streamable. Hope that we apply this as doing debian packaing. please let me if you have further problem.
I'm not sure what you mean here. If this patch fixes the problem, what is preventing it from going upstream? I guess we have this fix somewhere in the kernel produced by the landing team? If so, it seems maybe we should also add the landing team tree here for testing so that we can see it pass.
Thanks, Paul Larson
On 14 February 2012 16:40, Paul Larson paul.larson@linaro.org wrote:
On Tue, Feb 14, 2012 at 2:21 AM, Sangwook Lee sangwook.lee@linaro.orgwrote:
Hi Paul
On 14 February 2012 01:03, Paul Larson paul.larson@linaro.org wrote:
Looking at the latest results on.the kernel CI view I pointed out earlier, here is a serial.log from a recent one http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu...
You can see the test kernel starting to boot at around line 19560 and at 19660 it gets only as far as the starting kernel message, hangs, and eventually times out.
I think there is no option to download this log, maybe only for LAVA
team. If I download serial.log file as html, I must follow the link to serial log but again I have a broken link.
Yes, we need a download link there - known feature request that we'll hopefully get to soon.
but replaces the kernel with the output from jenkins building the
selected kernel. I'm guessing that perhaps we're missing something critical from the kernel configuration?
Yes, That's right. I am attaching the patch to fix this problem. Unfortunately, currently this is not up-streamable. Hope that we apply this as doing debian packaing. please let me if you have further problem.
I'm not sure what you mean here. If this patch fixes the problem, what is preventing it from going upstream?
arnd kernel (mainline kernel) we have to do the following for Origen board 1) Select exynos4_defconfig All boards for exynos CPU are sharing one configuration. So It select all boards configs and then set UART port to 1 2) We have to set UART port to 2 manually only for Origen
The patch I sent to you is to select debug UART port to 2 by default, only for Origen If we release this patch into mainline, all other boards using Exynos will manually select UART port again.
I guess we have this fix somewhere in the kernel produced by the landing team? If so, it seems maybe we should also add the landing team tree here for testing so that we can see it pass.
Here is our branch: *Git: *git://git.linaro.org/landing-teams/working/samsung/kernel.git* branch:* tracking
Initially I thought LAVA team is using hwpack built by John
https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
Does Lave team build their own hwpack from kernel ?
Thanks, Paul Larson
On Wed, Feb 15, 2012 at 4:32 PM, Sangwook Lee sangwook.lee@linaro.orgwrote:
On 14 February 2012 16:40, Paul Larson paul.larson@linaro.org wrote:
On Tue, Feb 14, 2012 at 2:21 AM, Sangwook Lee sangwook.lee@linaro.orgwrote:
Hi Paul
On 14 February 2012 01:03, Paul Larson paul.larson@linaro.org wrote:
Looking at the latest results on.the kernel CI view I pointed out earlier, here is a serial.log from a recent one http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu...
You can see the test kernel starting to boot at around line 19560 and at 19660 it gets only as far as the starting kernel message, hangs, and eventually times out.
I think there is no option to download this log, maybe only for LAVA
team. If I download serial.log file as html, I must follow the link to serial log but again I have a broken link.
Yes, we need a download link there - known feature request that we'll hopefully get to soon.
but replaces the kernel with the output from jenkins building the
selected kernel. I'm guessing that perhaps we're missing something critical from the kernel configuration?
Yes, That's right. I am attaching the patch to fix this problem. Unfortunately, currently this is not up-streamable. Hope that we apply this as doing debian packaing. please let me if you have further problem.
I'm not sure what you mean here. If this patch fixes the problem, what is preventing it from going upstream?
arnd kernel (mainline kernel) we have to do the following for Origen board 1) Select exynos4_defconfig All boards for exynos CPU are sharing one configuration. So It select all boards configs and then set UART port to 1 2) We have to set UART port to 2 manually only for Origen
The patch I sent to you is to select debug UART port to 2 by default, only for Origen If we release this patch into mainline, all other boards using Exynos will manually select UART port again.
I guess we have this fix somewhere in the kernel produced by the landing team? If so, it seems maybe we should also add the landing team tree here for testing so that we can see it pass.
Here is our branch: *Git: *git://git.linaro.org/landing-teams/working/samsung/kernel.git
branch:* tracking
Initially I thought LAVA team is using hwpack built by John
https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-dailyhttps://code.launchpad.net/%7Ejcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
Does Lave team build their own hwpack from kernel ?
Not the LAVA team. We(Infra) team build the latest upstream changes on ci.linaro.org and then send them to LAVA for testing.
Thanks, Paul Larson
On Wed, Feb 15, 2012 at 3:46 AM, Deepti Kalakeri <deepti.kalakeri@linaro.org
wrote:
On Wed, Feb 15, 2012 at 4:32 PM, Sangwook Lee sangwook.lee@linaro.orgwrote:
On 14 February 2012 16:40, Paul Larson paul.larson@linaro.org wrote:
On Tue, Feb 14, 2012 at 2:21 AM, Sangwook Lee sangwook.lee@linaro.orgwrote:
Hi Paul
On 14 February 2012 01:03, Paul Larson paul.larson@linaro.org wrote:
Looking at the latest results on.the kernel CI view I pointed out earlier, here is a serial.log from a recent one http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu...
You can see the test kernel starting to boot at around line 19560 and at 19660 it gets only as far as the starting kernel message, hangs, and eventually times out.
I think there is no option to download this log, maybe only for LAVA
team. If I download serial.log file as html, I must follow the link to serial log but again I have a broken link.
Yes, we need a download link there - known feature request that we'll hopefully get to soon.
but replaces the kernel with the output from jenkins building the
selected kernel. I'm guessing that perhaps we're missing something critical from the kernel configuration?
Yes, That's right. I am attaching the patch to fix this problem. Unfortunately, currently this is not up-streamable. Hope that we apply this as doing debian packaing. please let me if you have further problem.
I'm not sure what you mean here. If this patch fixes the problem, what is preventing it from going upstream?
arnd kernel (mainline kernel) we have to do the following for Origen board 1) Select exynos4_defconfig All boards for exynos CPU are sharing one configuration. So It select all boards configs and then set UART port to 1 2) We have to set UART port to 2 manually only for Origen
The patch I sent to you is to select debug UART port to 2 by default, only for Origen If we release this patch into mainline, all other boards using Exynos will manually select UART port again.
I guess we have this fix somewhere in the kernel produced by the landing team? If so, it seems maybe we should also add the landing team tree here for testing so that we can see it pass.
Here is our branch: *Git: *git:// git.linaro.org/landing-teams/working/samsung/kernel.git* branch:* tracking
Initially I thought LAVA team is using hwpack built by John
https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-dailyhttps://code.launchpad.net/%7Ejcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
Does Lave team build their own hwpack from kernel ?
Not the LAVA team. We(Infra) team build the latest upstream changes on ci.linaro.org and then send them to LAVA for testing.
Right, so I guess the better question would be, is there a bug for this already, and is there a better solution? Can we pass something on the boot cmdline that selects the proper uart? Why don't we have this problem with the linaro kernel in our leb images, do they include this workaround there?
Thanks, Paul Larson
The initial problem, you faced is due to the wrong kernel selected by someone. If you tried kernel from CI (arnd) , it should be based on 3.2 kernel, but it was not true. It was based on 2.6.35-rxxx. Where does this kernel come from ? At first, please select the proper kernel and then try LAVA again.
On 15 February 2012 21:35, Paul Larson paul.larson@linaro.org wrote:
On Wed, Feb 15, 2012 at 3:46 AM, Deepti Kalakeri < deepti.kalakeri@linaro.org> wrote:
On Wed, Feb 15, 2012 at 4:32 PM, Sangwook Lee sangwook.lee@linaro.orgwrote:
On 14 February 2012 16:40, Paul Larson paul.larson@linaro.org wrote:
On Tue, Feb 14, 2012 at 2:21 AM, Sangwook Lee sangwook.lee@linaro.orgwrote:
Hi Paul
On 14 February 2012 01:03, Paul Larson paul.larson@linaro.org wrote:
Looking at the latest results on.the kernel CI view I pointed out earlier, here is a serial.log from a recent one http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu...
You can see the test kernel starting to boot at around line 19560 and at 19660 it gets only as far as the starting kernel message, hangs, and eventually times out.
I think there is no option to download this log, maybe only for LAVA
team. If I download serial.log file as html, I must follow the link to serial log but again I have a broken link.
Yes, we need a download link there - known feature request that we'll hopefully get to soon.
but replaces the kernel with the output from jenkins building the
selected kernel. I'm guessing that perhaps we're missing something critical from the kernel configuration?
Yes, That's right. I am attaching the patch to fix this problem. Unfortunately, currently this is not up-streamable. Hope that we apply this as doing debian packaing. please let me if you have further problem.
I'm not sure what you mean here. If this patch fixes the problem, what is preventing it from going upstream?
arnd kernel (mainline kernel) we have to do the following for Origen board 1) Select exynos4_defconfig All boards for exynos CPU are sharing one configuration. So It select all boards configs and then set UART port to 1 2) We have to set UART port to 2 manually only for Origen
The patch I sent to you is to select debug UART port to 2 by default, only for Origen If we release this patch into mainline, all other boards using Exynos will manually select UART port again.
I guess we have this fix somewhere in the kernel produced by the landing team? If so, it seems maybe we should also add the landing team tree here for testing so that we can see it pass.
Here is our branch: *Git: *git:// git.linaro.org/landing-teams/working/samsung/kernel.git* branch:* tracking
Initially I thought LAVA team is using hwpack built by John
https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-dailyhttps://code.launchpad.net/%7Ejcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
Does Lave team build their own hwpack from kernel ?
Not the LAVA team. We(Infra) team build the latest upstream changes on ci.linaro.org and then send them to LAVA for testing.
Right, so I guess the better question would be, is there a bug for this already, and is there a better solution? Can we pass something on the boot cmdline that selects the proper uart? Why don't we have this problem with the linaro kernel in our leb images, do they include this workaround there?
Thanks, Paul Larson
Hello Sangwook,
On Thu, Feb 16, 2012 at 4:37 PM, Sangwook Lee sangwook.lee@linaro.orgwrote:
The initial problem, you faced is due to the wrong kernel selected by someone. If you tried kernel from CI (arnd) , it should be based on 3.2 kernel, but it was not true. It was based on 2.6.35-rxxx. Where does this kernel come from ? At first, please select the proper kernel and then try LAVA again.
I have rectified this. Actually we were using a repository setup by Arnd on git.linaro.org to build the kernel. We did not notice the move to git.kernel.org and we built the old things. But, otherwise also there are hwpacks built for linus(torvalds), linux-next tree with exynos4 defconfig using the latest upstream changes. I have not seen the hwpacks coming out for these trees either being successful to boot on the LAVA origen boards. Hence this is a problem that the hwpacks built for the origen boards do not work at all and not specific to just arm-soc tree. Can you check as an example if you can verify if the hwpacks built today works fine on your Origen board. http://ci.linaro.org/kernel_hwpack/linux-arm-soc-for-next/linux-arm-soc-for-... .
Do we need to apply the patch you gave yesterday on top of the Arnd latest changes to make it work ?
On 15 February 2012 21:35, Paul Larson paul.larson@linaro.org wrote:
On Wed, Feb 15, 2012 at 3:46 AM, Deepti Kalakeri < deepti.kalakeri@linaro.org> wrote:
On Wed, Feb 15, 2012 at 4:32 PM, Sangwook Lee sangwook.lee@linaro.orgwrote:
On 14 February 2012 16:40, Paul Larson paul.larson@linaro.org wrote:
On Tue, Feb 14, 2012 at 2:21 AM, Sangwook Lee <sangwook.lee@linaro.org
wrote:
Hi Paul
On 14 February 2012 01:03, Paul Larson paul.larson@linaro.orgwrote:
> Looking at the latest results on.the kernel CI view I pointed out > earlier, here is a serial.log from a recent one > http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu... > > You can see the test kernel starting to boot at around line 19560 > and at 19660 it gets only as far as the starting kernel message, hangs, and > eventually times out. > > I think there is no option to download this log, maybe only for LAVA team. If I download serial.log file as html, I must follow the link to serial log but again I have a broken link.
Yes, we need a download link there - known feature request that we'll hopefully get to soon.
but replaces the kernel with the output from jenkins building the > selected kernel. I'm guessing that perhaps we're missing something > critical from the kernel configuration? > Yes, That's right. I am attaching the patch to fix this problem. Unfortunately, currently this is not up-streamable. Hope that we apply this as doing debian packaing. please let me if you have further problem.
I'm not sure what you mean here. If this patch fixes the problem, what is preventing it from going upstream?
arnd kernel (mainline kernel) we have to do the following for Origen board 1) Select exynos4_defconfig All boards for exynos CPU are sharing one configuration. So It select all boards configs and then set UART port to 1 2) We have to set UART port to 2 manually only for Origen
The patch I sent to you is to select debug UART port to 2 by default, only for Origen If we release this patch into mainline, all other boards using Exynos will manually select UART port again.
I guess we have this fix somewhere in the kernel produced by the landing team? If so, it seems maybe we should also add the landing team tree here for testing so that we can see it pass.
Here is our branch: *Git: *git:// git.linaro.org/landing-teams/working/samsung/kernel.git* branch:* tracking
Initially I thought LAVA team is using hwpack built by John
https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-dailyhttps://code.launchpad.net/%7Ejcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
Does Lave team build their own hwpack from kernel ?
Not the LAVA team. We(Infra) team build the latest upstream changes on ci.linaro.org and then send them to LAVA for testing.
Right, so I guess the better question would be, is there a bug for this already, and is there a better solution? Can we pass something on the boot cmdline that selects the proper uart? Why don't we have this problem with the linaro kernel in our leb images, do they include this workaround there?
Thanks, Paul Larson
On 16 February 2012 11:39, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
Hello Sangwook,
On Thu, Feb 16, 2012 at 4:37 PM, Sangwook Lee sangwook.lee@linaro.org wrote:
The initial problem, you faced is due to the wrong kernel selected by someone. If you tried kernel from CI (arnd) , it should be based on 3.2 kernel, but it was not true. It was based on 2.6.35-rxxx. Where does this kernel come from ? At first, please select the proper kernel and then try LAVA again.
I have rectified this. Actually we were using a repository setup by Arnd on git.linaro.org to build the kernel. We did not notice the move to git.kernel.org and we built the old things. But, otherwise also there are hwpacks built for linus(torvalds), linux-next tree with exynos4 defconfig using the latest upstream changes. I have not seen the hwpacks coming out for these trees either being successful to boot on the LAVA origen boards. Hence this is a problem that the hwpacks built for the origen boards do not work at all and not specific to just arm-soc tree. Can you check as an example if you can verify if the hwpacks built today works fine on your Origen board. http://ci.linaro.org/kernel_hwpack/linux-arm-soc-for-next/linux-arm-soc-for-....
With this image, I couldn't see the booting message.
Do we need to apply the patch you gave yesterday on top of the Arnd latest changes to make it work ?
Yes,
I downloaded git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git and then could see the booting message with the patch.
On 15 February 2012 21:35, Paul Larson paul.larson@linaro.org wrote:
On Wed, Feb 15, 2012 at 3:46 AM, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
On Wed, Feb 15, 2012 at 4:32 PM, Sangwook Lee sangwook.lee@linaro.org wrote:
On 14 February 2012 16:40, Paul Larson paul.larson@linaro.org wrote:
On Tue, Feb 14, 2012 at 2:21 AM, Sangwook Lee sangwook.lee@linaro.org wrote: > > Hi Paul > > On 14 February 2012 01:03, Paul Larson paul.larson@linaro.org > wrote: >> >> Looking at the latest results on.the kernel CI view I pointed out >> earlier, here is a serial.log from a recent one >> http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu... >> >> You can see the test kernel starting to boot at around line 19560 >> and at 19660 it gets only as far as the starting kernel message, hangs, and >> eventually times out. > > I think there is no option to download this log, maybe only for LAVA > team. > If I download serial.log file as html, I must follow the link to > serial log but again I have a broken link.
Yes, we need a download link there - known feature request that we'll hopefully get to soon. >> >> but replaces the kernel with the output from jenkins building the >> selected kernel. I'm guessing that perhaps we're missing something critical >> from the kernel configuration? > > Yes, That's right. I am attaching the patch to fix this problem. > Unfortunately, currently this is not up-streamable. Hope that we > apply this as doing debian packaing. > please let me if you have further problem.
I'm not sure what you mean here. If this patch fixes the problem, what is preventing it from going upstream?
arnd kernel (mainline kernel) we have to do the following for Origen board 1) Select exynos4_defconfig All boards for exynos CPU are sharing one configuration. So It select all boards configs and then set UART port to 1 2) We have to set UART port to 2 manually only for Origen
The patch I sent to you is to select debug UART port to 2 by default, only for Origen If we release this patch into mainline, all other boards using Exynos will manually select UART port again.
I guess we have this fix somewhere in the kernel produced by the landing team? If so, it seems maybe we should also add the landing team tree here for testing so that we can see it pass.
Here is our branch: Git: git://git.linaro.org/landing-teams/working/samsung/kernel.git branch: tracking
Initially I thought LAVA team is using hwpack built by John
https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
Does Lave team build their own hwpack from kernel ?
Not the LAVA team. We(Infra) team build the latest upstream changes on ci.linaro.org and then send them to LAVA for testing.
Right, so I guess the better question would be, is there a bug for this already, and is there a better solution? Can we pass something on the boot cmdline that selects the proper uart? Why don't we have this problem with the linaro kernel in our leb images, do they include this workaround there?
Thanks, Paul Larson
-- 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
So if I'm understanding correctly, these are actual failures. It would be nice to have some tree that actually worked, but if it fails because it's missing this patch, then it fails. I think we test the Linaro 3.1 tree there though right? Shouldn't that include this, or is this not what we currently ship in the LEB images?
http://people.linaro.org/~asac/githttp/linux-linaro-3.1.git/ is the one I'm referring to, though I think it should really refer to the real upstream tree, not the one in Alex's people.linaro.org account.
Thanks, Paul Larson
On Tue, Feb 21, 2012 at 6:57 AM, Sangwook Lee sangwook.lee@linaro.orgwrote:
On 16 February 2012 11:39, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
Hello Sangwook,
On Thu, Feb 16, 2012 at 4:37 PM, Sangwook Lee sangwook.lee@linaro.org wrote:
The initial problem, you faced is due to the wrong kernel selected by someone. If you tried kernel from CI (arnd) , it should be based on 3.2 kernel,
but
it was not true. It was based on 2.6.35-rxxx. Where does this kernel come from ? At first, please select the proper kernel and then try LAVA again.
I have rectified this. Actually we were using a repository setup by Arnd
on
git.linaro.org to build the kernel. We did not notice the move to git.kernel.org and we built the old
things.
But, otherwise also there are hwpacks built for linus(torvalds),
linux-next
tree with exynos4 defconfig using the latest upstream changes. I have not seen the hwpacks coming out for these trees either being successful to boot on the LAVA origen boards. Hence this is a problem that the hwpacks built for the origen boards do
not
work at all and not specific to just arm-soc tree. Can you check as an example if you can verify if the hwpacks built today works fine on your Origen board.
http://ci.linaro.org/kernel_hwpack/linux-arm-soc-for-next/linux-arm-soc-for-... .
With this image, I couldn't see the booting message.
Do we need to apply the patch you gave yesterday on top of the Arnd
latest
changes to make it work ?
Yes,
I downloaded git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git and then could see the booting message with the patch.
On 15 February 2012 21:35, Paul Larson paul.larson@linaro.org wrote:
On Wed, Feb 15, 2012 at 3:46 AM, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
On Wed, Feb 15, 2012 at 4:32 PM, Sangwook Lee <
sangwook.lee@linaro.org>
wrote:
On 14 February 2012 16:40, Paul Larson paul.larson@linaro.org
wrote:
> > On Tue, Feb 14, 2012 at 2:21 AM, Sangwook Lee > sangwook.lee@linaro.org wrote: >> >> Hi Paul >> >> On 14 February 2012 01:03, Paul Larson paul.larson@linaro.org >> wrote: >>> >>> Looking at the latest results on.the kernel CI view I pointed out >>> earlier, here is a serial.log from a recent one >>>
http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu...
>>> >>> You can see the test kernel starting to boot at around line 19560 >>> and at 19660 it gets only as far as the starting kernel message,
hangs, and
>>> eventually times out. >> >> I think there is no option to download this log, maybe only for
LAVA
>> team. >> If I download serial.log file as html, I must follow the link to >> serial log but again I have a broken link. > > Yes, we need a download link there - known feature request that
we'll
> hopefully get to soon. >>> >>> but replaces the kernel with the output from jenkins building the >>> selected kernel. I'm guessing that perhaps we're missing
something critical
>>> from the kernel configuration? >> >> Yes, That's right. I am attaching the patch to fix this problem. >> Unfortunately, currently this is not up-streamable. Hope that we >> apply this as doing debian packaing. >> please let me if you have further problem. > > > I'm not sure what you mean here. If this patch fixes the problem, > what is preventing it from going upstream?
arnd kernel (mainline kernel) we have to do the following for Origen board 1) Select exynos4_defconfig All boards for exynos CPU are sharing one configuration. So It select all boards configs and then set UART port to 1 2) We have to set UART port to 2 manually only for Origen
The patch I sent to you is to select debug UART port to 2 by default, only for Origen If we release this patch into mainline, all other boards using Exynos will manually select UART port again.
> > I guess we have this fix somewhere in the kernel produced by the > landing team? If so, it seems maybe we should also add the landing
team
> tree here for testing so that we can see it pass.
Here is our branch: Git: git://git.linaro.org/landing-teams/working/samsung/kernel.git branch: tracking
Initially I thought LAVA team is using hwpack built by John
https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-dailyhttps://code.launchpad.net/%7Ejcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
Does Lave team build their own hwpack from kernel ?
Not the LAVA team. We(Infra) team build the latest upstream changes on ci.linaro.org and then send them to LAVA for testing.
Right, so I guess the better question would be, is there a bug for this already, and is there a better solution? Can we pass something on the
boot
cmdline that selects the proper uart? Why don't we have this problem
with
the linaro kernel in our leb images, do they include this workaround
there?
Thanks, Paul Larson
-- 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 21 February 2012 17:00, Paul Larson paul.larson@linaro.org wrote:
So if I'm understanding correctly, these are actual failures. It would be nice to have some tree that actually worked, but if it fails because it's missing this patch, then it fails. I think we test the Linaro 3.1 tree there though right? Shouldn't that include this, or is this not
what we currently ship in the LEB images?
Git: *git://git.linaro.org/landing-teams/working/samsung/kernel.git* Branch: *tracking*
http://people.linaro.org/~asac/githttp/linux-linaro-3.1.git/ is the one I'm referring to, though I think it should really refer to the real upstream tree, not the one in Alex's people.linaro.org account.
Thanks, Paul Larson
On Tue, Feb 21, 2012 at 6:57 AM, Sangwook Lee sangwook.lee@linaro.orgwrote:
On 16 February 2012 11:39, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
Hello Sangwook,
On Thu, Feb 16, 2012 at 4:37 PM, Sangwook Lee sangwook.lee@linaro.org wrote:
The initial problem, you faced is due to the wrong kernel selected by someone. If you tried kernel from CI (arnd) , it should be based on 3.2 kernel,
but
it was not true. It was based on 2.6.35-rxxx. Where does this kernel come from ? At first, please select the proper kernel and then try LAVA again.
I have rectified this. Actually we were using a repository setup by
Arnd on
git.linaro.org to build the kernel. We did not notice the move to git.kernel.org and we built the old
things.
But, otherwise also there are hwpacks built for linus(torvalds),
linux-next
tree with exynos4 defconfig using the latest upstream changes. I have not seen the hwpacks coming out for these trees either being successful to boot on the LAVA origen boards. Hence this is a problem that the hwpacks built for the origen boards do
not
work at all and not specific to just arm-soc tree. Can you check as an example if you can verify if the hwpacks built today works fine on your Origen board.
http://ci.linaro.org/kernel_hwpack/linux-arm-soc-for-next/linux-arm-soc-for-... .
With this image, I couldn't see the booting message.
Do we need to apply the patch you gave yesterday on top of the Arnd
latest
changes to make it work ?
Yes,
I downloaded git:// git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git and then could see the booting message with the patch.
On 15 February 2012 21:35, Paul Larson paul.larson@linaro.org wrote:
On Wed, Feb 15, 2012 at 3:46 AM, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
On Wed, Feb 15, 2012 at 4:32 PM, Sangwook Lee <
sangwook.lee@linaro.org>
wrote: > > > > On 14 February 2012 16:40, Paul Larson paul.larson@linaro.org
wrote:
>> >> On Tue, Feb 14, 2012 at 2:21 AM, Sangwook Lee >> sangwook.lee@linaro.org wrote: >>> >>> Hi Paul >>> >>> On 14 February 2012 01:03, Paul Larson paul.larson@linaro.org >>> wrote: >>>> >>>> Looking at the latest results on.the kernel CI view I pointed out >>>> earlier, here is a serial.log from a recent one >>>>
http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu...
>>>> >>>> You can see the test kernel starting to boot at around line 19560 >>>> and at 19660 it gets only as far as the starting kernel message,
hangs, and
>>>> eventually times out. >>> >>> I think there is no option to download this log, maybe only for
LAVA
>>> team. >>> If I download serial.log file as html, I must follow the link to >>> serial log but again I have a broken link. >> >> Yes, we need a download link there - known feature request that
we'll
>> hopefully get to soon. >>>> >>>> but replaces the kernel with the output from jenkins building the >>>> selected kernel. I'm guessing that perhaps we're missing
something critical
>>>> from the kernel configuration? >>> >>> Yes, That's right. I am attaching the patch to fix this problem. >>> Unfortunately, currently this is not up-streamable. Hope that we >>> apply this as doing debian packaing. >>> please let me if you have further problem. >> >> >> I'm not sure what you mean here. If this patch fixes the problem, >> what is preventing it from going upstream? > > > arnd kernel (mainline kernel) we have to do the following for Origen > board > 1) Select exynos4_defconfig > All boards for exynos CPU are sharing one > configuration. > So It select all boards configs and then set
UART
> port to 1 > 2) We have to set UART port to 2 manually only for
Origen
> > The patch I sent to you is to select debug UART port to 2 by
default,
> only for Origen > If we release this patch into mainline, all other boards using
Exynos
> will manually select UART port again. > > >> >> I guess we have this fix somewhere in the kernel produced by the >> landing team? If so, it seems maybe we should also add the
landing team
>> tree here for testing so that we can see it pass. > > > Here is our branch: > Git: > git://git.linaro.org/landing-teams/working/samsung/kernel.git > branch: tracking > > Initially I thought LAVA team is using hwpack built by John > >
https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-dailyhttps://code.launchpad.net/%7Ejcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
> > Does Lave team build their own hwpack from kernel ?
Not the LAVA team. We(Infra) team build the latest upstream changes
on
ci.linaro.org and then send them to LAVA for testing.
Right, so I guess the better question would be, is there a bug for
this
already, and is there a better solution? Can we pass something on the
boot
cmdline that selects the proper uart? Why don't we have this problem
with
the linaro kernel in our leb images, do they include this workaround
there?
Thanks, Paul Larson
-- 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 Tue, Feb 21, 2012 at 10:30 PM, Paul Larson paul.larson@linaro.orgwrote:
So if I'm understanding correctly, these are actual failures. It would be nice to have some tree that actually worked, but if it fails because it's missing this patch, then it fails. I think we test the Linaro 3.1 tree there though right? Shouldn't that include this, or is this not what we currently ship in the LEB images?
http://people.linaro.org/~asac/githttp/linux-linaro-3.1.git/ is the one I'm referring to, though I think it should really refer to the real upstream tree, not the one in Alex's people.linaro.org account.
Yes we build the linux-linaro 3.1 from http://people.linaro.org/~asac/githttp/linux-linaro-3.1.git/ which points to the latest upstream changes as well. But the origen hwpack fails for this tree as well.
@ Sangwook,
So should we apply the patch for all the trees (arm-soc, linus(torvalds), linux-linaro, linux-next) and build the kernel for testing on the origen boards?
Thanks,
Paul Larson
On Tue, Feb 21, 2012 at 6:57 AM, Sangwook Lee sangwook.lee@linaro.orgwrote:
On 16 February 2012 11:39, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
Hello Sangwook,
On Thu, Feb 16, 2012 at 4:37 PM, Sangwook Lee sangwook.lee@linaro.org wrote:
The initial problem, you faced is due to the wrong kernel selected by someone. If you tried kernel from CI (arnd) , it should be based on 3.2 kernel,
but
it was not true. It was based on 2.6.35-rxxx. Where does this kernel come from ? At first, please select the proper kernel and then try LAVA again.
I have rectified this. Actually we were using a repository setup by
Arnd on
git.linaro.org to build the kernel. We did not notice the move to git.kernel.org and we built the old
things.
But, otherwise also there are hwpacks built for linus(torvalds),
linux-next
tree with exynos4 defconfig using the latest upstream changes. I have not seen the hwpacks coming out for these trees either being successful to boot on the LAVA origen boards. Hence this is a problem that the hwpacks built for the origen boards do
not
work at all and not specific to just arm-soc tree. Can you check as an example if you can verify if the hwpacks built today works fine on your Origen board.
http://ci.linaro.org/kernel_hwpack/linux-arm-soc-for-next/linux-arm-soc-for-... .
With this image, I couldn't see the booting message.
Do we need to apply the patch you gave yesterday on top of the Arnd
latest
changes to make it work ?
Yes,
I downloaded git:// git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git and then could see the booting message with the patch.
On 15 February 2012 21:35, Paul Larson paul.larson@linaro.org wrote:
On Wed, Feb 15, 2012 at 3:46 AM, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
On Wed, Feb 15, 2012 at 4:32 PM, Sangwook Lee <
sangwook.lee@linaro.org>
wrote: > > > > On 14 February 2012 16:40, Paul Larson paul.larson@linaro.org
wrote:
>> >> On Tue, Feb 14, 2012 at 2:21 AM, Sangwook Lee >> sangwook.lee@linaro.org wrote: >>> >>> Hi Paul >>> >>> On 14 February 2012 01:03, Paul Larson paul.larson@linaro.org >>> wrote: >>>> >>>> Looking at the latest results on.the kernel CI view I pointed out >>>> earlier, here is a serial.log from a recent one >>>>
http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu...
>>>> >>>> You can see the test kernel starting to boot at around line 19560 >>>> and at 19660 it gets only as far as the starting kernel message,
hangs, and
>>>> eventually times out. >>> >>> I think there is no option to download this log, maybe only for
LAVA
>>> team. >>> If I download serial.log file as html, I must follow the link to >>> serial log but again I have a broken link. >> >> Yes, we need a download link there - known feature request that
we'll
>> hopefully get to soon. >>>> >>>> but replaces the kernel with the output from jenkins building the >>>> selected kernel. I'm guessing that perhaps we're missing
something critical
>>>> from the kernel configuration? >>> >>> Yes, That's right. I am attaching the patch to fix this problem. >>> Unfortunately, currently this is not up-streamable. Hope that we >>> apply this as doing debian packaing. >>> please let me if you have further problem. >> >> >> I'm not sure what you mean here. If this patch fixes the problem, >> what is preventing it from going upstream? > > > arnd kernel (mainline kernel) we have to do the following for Origen > board > 1) Select exynos4_defconfig > All boards for exynos CPU are sharing one > configuration. > So It select all boards configs and then set
UART
> port to 1 > 2) We have to set UART port to 2 manually only for
Origen
> > The patch I sent to you is to select debug UART port to 2 by
default,
> only for Origen > If we release this patch into mainline, all other boards using
Exynos
> will manually select UART port again. > > >> >> I guess we have this fix somewhere in the kernel produced by the >> landing team? If so, it seems maybe we should also add the
landing team
>> tree here for testing so that we can see it pass. > > > Here is our branch: > Git: > git://git.linaro.org/landing-teams/working/samsung/kernel.git > branch: tracking > > Initially I thought LAVA team is using hwpack built by John > >
https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-dailyhttps://code.launchpad.net/%7Ejcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
> > Does Lave team build their own hwpack from kernel ?
Not the LAVA team. We(Infra) team build the latest upstream changes
on
ci.linaro.org and then send them to LAVA for testing.
Right, so I guess the better question would be, is there a bug for
this
already, and is there a better solution? Can we pass something on the
boot
cmdline that selects the proper uart? Why don't we have this problem
with
the linaro kernel in our leb images, do they include this workaround
there?
Thanks, Paul Larson
-- 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 Tue, Feb 21, 2012 at 8:27 PM, Sangwook Lee sangwook.lee@linaro.orgwrote:
On 16 February 2012 11:39, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
Hello Sangwook,
On Thu, Feb 16, 2012 at 4:37 PM, Sangwook Lee sangwook.lee@linaro.org wrote:
The initial problem, you faced is due to the wrong kernel selected by someone. If you tried kernel from CI (arnd) , it should be based on 3.2 kernel,
but
it was not true. It was based on 2.6.35-rxxx. Where does this kernel come from ? At first, please select the proper kernel and then try LAVA again.
I have rectified this. Actually we were using a repository setup by Arnd
on
git.linaro.org to build the kernel. We did not notice the move to git.kernel.org and we built the old
things.
But, otherwise also there are hwpacks built for linus(torvalds),
linux-next
tree with exynos4 defconfig using the latest upstream changes. I have not seen the hwpacks coming out for these trees either being successful to boot on the LAVA origen boards. Hence this is a problem that the hwpacks built for the origen boards do
not
work at all and not specific to just arm-soc tree. Can you check as an example if you can verify if the hwpacks built today works fine on your Origen board.
http://ci.linaro.org/kernel_hwpack/linux-arm-soc-for-next/linux-arm-soc-for-... .
With this image, I couldn't see the booting message.
Thanks for trying this. What is the last message we see when the hwpack boots ?
Do we need to apply the patch you gave yesterday on top of the Arnd
latest
changes to make it work ?
Yes,
I downloaded git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git and then could see the booting message with the patch.
On 15 February 2012 21:35, Paul Larson paul.larson@linaro.org wrote:
On Wed, Feb 15, 2012 at 3:46 AM, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
On Wed, Feb 15, 2012 at 4:32 PM, Sangwook Lee <
sangwook.lee@linaro.org>
wrote:
On 14 February 2012 16:40, Paul Larson paul.larson@linaro.org
wrote:
> > On Tue, Feb 14, 2012 at 2:21 AM, Sangwook Lee > sangwook.lee@linaro.org wrote: >> >> Hi Paul >> >> On 14 February 2012 01:03, Paul Larson paul.larson@linaro.org >> wrote: >>> >>> Looking at the latest results on.the kernel CI view I pointed out >>> earlier, here is a serial.log from a recent one >>>
http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu...
>>> >>> You can see the test kernel starting to boot at around line 19560 >>> and at 19660 it gets only as far as the starting kernel message,
hangs, and
>>> eventually times out. >> >> I think there is no option to download this log, maybe only for
LAVA
>> team. >> If I download serial.log file as html, I must follow the link to >> serial log but again I have a broken link. > > Yes, we need a download link there - known feature request that
we'll
> hopefully get to soon. >>> >>> but replaces the kernel with the output from jenkins building the >>> selected kernel. I'm guessing that perhaps we're missing
something critical
>>> from the kernel configuration? >> >> Yes, That's right. I am attaching the patch to fix this problem. >> Unfortunately, currently this is not up-streamable. Hope that we >> apply this as doing debian packaing. >> please let me if you have further problem. > > > I'm not sure what you mean here. If this patch fixes the problem, > what is preventing it from going upstream?
arnd kernel (mainline kernel) we have to do the following for Origen board 1) Select exynos4_defconfig All boards for exynos CPU are sharing one configuration. So It select all boards configs and then set UART port to 1 2) We have to set UART port to 2 manually only for Origen
The patch I sent to you is to select debug UART port to 2 by default, only for Origen If we release this patch into mainline, all other boards using Exynos will manually select UART port again.
> > I guess we have this fix somewhere in the kernel produced by the > landing team? If so, it seems maybe we should also add the landing
team
> tree here for testing so that we can see it pass.
Here is our branch: Git: git://git.linaro.org/landing-teams/working/samsung/kernel.git branch: tracking
Initially I thought LAVA team is using hwpack built by John
https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-dailyhttps://code.launchpad.net/%7Ejcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
Does Lave team build their own hwpack from kernel ?
Not the LAVA team. We(Infra) team build the latest upstream changes on ci.linaro.org and then send them to LAVA for testing.
Right, so I guess the better question would be, is there a bug for this already, and is there a better solution? Can we pass something on the
boot
cmdline that selects the proper uart? Why don't we have this problem
with
the linaro kernel in our leb images, do they include this workaround
there?
Thanks, Paul Larson
-- 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 22 February 2012 09:53, Deepti Kalakeri deepti.kalakeri@linaro.orgwrote:
On Tue, Feb 21, 2012 at 10:30 PM, Paul Larson paul.larson@linaro.orgwrote:
So if I'm understanding correctly, these are actual failures. It would be nice to have some tree that actually worked, but if it fails because it's missing this patch, then it fails. I think we test the Linaro 3.1 tree there though right? Shouldn't that include this, or is this not what we currently ship in the LEB images?
http://people.linaro.org/~asac/githttp/linux-linaro-3.1.git/ is the one I'm referring to, though I think it should really refer to the real upstream tree, not the one in Alex's people.linaro.org account.
Yes we build the linux-linaro 3.1 from http://people.linaro.org/~asac/githttp/linux-linaro-3.1.git/ which points to the latest upstream changes as well. But the origen hwpack fails for this tree as well.
@ Sangwook,
So should we apply the patch for all the trees (arm-soc, linus(torvalds), linux-linaro, linux-next) and build the kernel for testing on the origen boards?
Yes, only If you want to build kernel automatically without touching exynos4_defconfig or .confg.
Thanks,
Paul Larson
On Tue, Feb 21, 2012 at 6:57 AM, Sangwook Lee sangwook.lee@linaro.orgwrote:
On 16 February 2012 11:39, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
Hello Sangwook,
On Thu, Feb 16, 2012 at 4:37 PM, Sangwook Lee <sangwook.lee@linaro.org
wrote:
The initial problem, you faced is due to the wrong kernel selected by someone. If you tried kernel from CI (arnd) , it should be based on 3.2
kernel, but
it was not true. It was based on 2.6.35-rxxx. Where does this kernel come from ? At first, please select the proper kernel and then try LAVA again.
I have rectified this. Actually we were using a repository setup by
Arnd on
git.linaro.org to build the kernel. We did not notice the move to git.kernel.org and we built the old
things.
But, otherwise also there are hwpacks built for linus(torvalds),
linux-next
tree with exynos4 defconfig using the latest upstream changes. I have not seen the hwpacks coming out for these trees either being successful to boot on the LAVA origen boards. Hence this is a problem that the hwpacks built for the origen boards
do not
work at all and not specific to just arm-soc tree. Can you check as an example if you can verify if the hwpacks built
today
works fine on your Origen board.
http://ci.linaro.org/kernel_hwpack/linux-arm-soc-for-next/linux-arm-soc-for-... .
With this image, I couldn't see the booting message.
Do we need to apply the patch you gave yesterday on top of the Arnd
latest
changes to make it work ?
Yes,
I downloaded git:// git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git and then could see the booting message with the patch.
On 15 February 2012 21:35, Paul Larson paul.larson@linaro.org
wrote:
On Wed, Feb 15, 2012 at 3:46 AM, Deepti Kalakeri deepti.kalakeri@linaro.org wrote: > > > > On Wed, Feb 15, 2012 at 4:32 PM, Sangwook Lee <
sangwook.lee@linaro.org>
> wrote: >> >> >> >> On 14 February 2012 16:40, Paul Larson paul.larson@linaro.org
wrote:
>>> >>> On Tue, Feb 14, 2012 at 2:21 AM, Sangwook Lee >>> sangwook.lee@linaro.org wrote: >>>> >>>> Hi Paul >>>> >>>> On 14 February 2012 01:03, Paul Larson paul.larson@linaro.org >>>> wrote: >>>>> >>>>> Looking at the latest results on.the kernel CI view I pointed
out
>>>>> earlier, here is a serial.log from a recent one >>>>>
http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu...
>>>>> >>>>> You can see the test kernel starting to boot at around line
19560
>>>>> and at 19660 it gets only as far as the starting kernel
message, hangs, and
>>>>> eventually times out. >>>> >>>> I think there is no option to download this log, maybe only for
LAVA
>>>> team. >>>> If I download serial.log file as html, I must follow the link to >>>> serial log but again I have a broken link. >>> >>> Yes, we need a download link there - known feature request that
we'll
>>> hopefully get to soon. >>>>> >>>>> but replaces the kernel with the output from jenkins building
the
>>>>> selected kernel. I'm guessing that perhaps we're missing
something critical
>>>>> from the kernel configuration? >>>> >>>> Yes, That's right. I am attaching the patch to fix this problem. >>>> Unfortunately, currently this is not up-streamable. Hope that we >>>> apply this as doing debian packaing. >>>> please let me if you have further problem. >>> >>> >>> I'm not sure what you mean here. If this patch fixes the problem, >>> what is preventing it from going upstream? >> >> >> arnd kernel (mainline kernel) we have to do the following for
Origen
>> board >> 1) Select exynos4_defconfig >> All boards for exynos CPU are sharing one >> configuration. >> So It select all boards configs and then set
UART
>> port to 1 >> 2) We have to set UART port to 2 manually only for
Origen
>> >> The patch I sent to you is to select debug UART port to 2 by
default,
>> only for Origen >> If we release this patch into mainline, all other boards using
Exynos
>> will manually select UART port again. >> >> >>> >>> I guess we have this fix somewhere in the kernel produced by the >>> landing team? If so, it seems maybe we should also add the
landing team
>>> tree here for testing so that we can see it pass. >> >> >> Here is our branch: >> Git: >> git://git.linaro.org/landing-teams/working/samsung/kernel.git >> branch: tracking >> >> Initially I thought LAVA team is using hwpack built by John >> >>
https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-dailyhttps://code.launchpad.net/%7Ejcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
>> >> Does Lave team build their own hwpack from kernel ? > > > Not the LAVA team. We(Infra) team build the latest upstream changes
on
> ci.linaro.org and then send them to LAVA for testing.
Right, so I guess the better question would be, is there a bug for
this
already, and is there a better solution? Can we pass something on
the boot
cmdline that selects the proper uart? Why don't we have this problem
with
the linaro kernel in our leb images, do they include this workaround
there?
Thanks, Paul Larson
-- 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
-- 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 22 February 2012 09:54, Deepti Kalakeri deepti.kalakeri@linaro.orgwrote:
On Tue, Feb 21, 2012 at 8:27 PM, Sangwook Lee sangwook.lee@linaro.orgwrote:
On 16 February 2012 11:39, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
Hello Sangwook,
On Thu, Feb 16, 2012 at 4:37 PM, Sangwook Lee sangwook.lee@linaro.org wrote:
The initial problem, you faced is due to the wrong kernel selected by someone. If you tried kernel from CI (arnd) , it should be based on 3.2 kernel,
but
it was not true. It was based on 2.6.35-rxxx. Where does this kernel come from ? At first, please select the proper kernel and then try LAVA again.
I have rectified this. Actually we were using a repository setup by
Arnd on
git.linaro.org to build the kernel. We did not notice the move to git.kernel.org and we built the old
things.
But, otherwise also there are hwpacks built for linus(torvalds),
linux-next
tree with exynos4 defconfig using the latest upstream changes. I have not seen the hwpacks coming out for these trees either being successful to boot on the LAVA origen boards. Hence this is a problem that the hwpacks built for the origen boards do
not
work at all and not specific to just arm-soc tree. Can you check as an example if you can verify if the hwpacks built today works fine on your Origen board.
http://ci.linaro.org/kernel_hwpack/linux-arm-soc-for-next/linux-arm-soc-for-... .
With this image, I couldn't see the booting message.
Thanks for trying this. What is the last message we see when the hwpack boots ?
exactly same as like the previous one.
Deepti, do you want to get one Origen board from Samsung Bangalore ?
Do we need to apply the patch you gave yesterday on top of the Arnd
latest
changes to make it work ?
Yes,
I downloaded git:// git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git and then could see the booting message with the patch.
On 15 February 2012 21:35, Paul Larson paul.larson@linaro.org wrote:
On Wed, Feb 15, 2012 at 3:46 AM, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
On Wed, Feb 15, 2012 at 4:32 PM, Sangwook Lee <
sangwook.lee@linaro.org>
wrote: > > > > On 14 February 2012 16:40, Paul Larson paul.larson@linaro.org
wrote:
>> >> On Tue, Feb 14, 2012 at 2:21 AM, Sangwook Lee >> sangwook.lee@linaro.org wrote: >>> >>> Hi Paul >>> >>> On 14 February 2012 01:03, Paul Larson paul.larson@linaro.org >>> wrote: >>>> >>>> Looking at the latest results on.the kernel CI view I pointed out >>>> earlier, here is a serial.log from a recent one >>>>
http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu...
>>>> >>>> You can see the test kernel starting to boot at around line 19560 >>>> and at 19660 it gets only as far as the starting kernel message,
hangs, and
>>>> eventually times out. >>> >>> I think there is no option to download this log, maybe only for
LAVA
>>> team. >>> If I download serial.log file as html, I must follow the link to >>> serial log but again I have a broken link. >> >> Yes, we need a download link there - known feature request that
we'll
>> hopefully get to soon. >>>> >>>> but replaces the kernel with the output from jenkins building the >>>> selected kernel. I'm guessing that perhaps we're missing
something critical
>>>> from the kernel configuration? >>> >>> Yes, That's right. I am attaching the patch to fix this problem. >>> Unfortunately, currently this is not up-streamable. Hope that we >>> apply this as doing debian packaing. >>> please let me if you have further problem. >> >> >> I'm not sure what you mean here. If this patch fixes the problem, >> what is preventing it from going upstream? > > > arnd kernel (mainline kernel) we have to do the following for Origen > board > 1) Select exynos4_defconfig > All boards for exynos CPU are sharing one > configuration. > So It select all boards configs and then set
UART
> port to 1 > 2) We have to set UART port to 2 manually only for
Origen
> > The patch I sent to you is to select debug UART port to 2 by
default,
> only for Origen > If we release this patch into mainline, all other boards using
Exynos
> will manually select UART port again. > > >> >> I guess we have this fix somewhere in the kernel produced by the >> landing team? If so, it seems maybe we should also add the
landing team
>> tree here for testing so that we can see it pass. > > > Here is our branch: > Git: > git://git.linaro.org/landing-teams/working/samsung/kernel.git > branch: tracking > > Initially I thought LAVA team is using hwpack built by John > >
https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-dailyhttps://code.launchpad.net/%7Ejcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
> > Does Lave team build their own hwpack from kernel ?
Not the LAVA team. We(Infra) team build the latest upstream changes
on
ci.linaro.org and then send them to LAVA for testing.
Right, so I guess the better question would be, is there a bug for
this
already, and is there a better solution? Can we pass something on the
boot
cmdline that selects the proper uart? Why don't we have this problem
with
the linaro kernel in our leb images, do they include this workaround
there?
Thanks, Paul Larson
-- 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
-- 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 Wed, Feb 22, 2012 at 3:42 PM, Sangwook Lee sangwook.lee@linaro.orgwrote:
On 22 February 2012 09:54, Deepti Kalakeri deepti.kalakeri@linaro.orgwrote:
On Tue, Feb 21, 2012 at 8:27 PM, Sangwook Lee sangwook.lee@linaro.orgwrote:
On 16 February 2012 11:39, Deepti Kalakeri deepti.kalakeri@linaro.org wrote:
Hello Sangwook,
On Thu, Feb 16, 2012 at 4:37 PM, Sangwook Lee <sangwook.lee@linaro.org
wrote:
The initial problem, you faced is due to the wrong kernel selected by someone. If you tried kernel from CI (arnd) , it should be based on 3.2
kernel, but
it was not true. It was based on 2.6.35-rxxx. Where does this kernel come from ? At first, please select the proper kernel and then try LAVA again.
I have rectified this. Actually we were using a repository setup by
Arnd on
git.linaro.org to build the kernel. We did not notice the move to git.kernel.org and we built the old
things.
But, otherwise also there are hwpacks built for linus(torvalds),
linux-next
tree with exynos4 defconfig using the latest upstream changes. I have not seen the hwpacks coming out for these trees either being successful to boot on the LAVA origen boards. Hence this is a problem that the hwpacks built for the origen boards
do not
work at all and not specific to just arm-soc tree. Can you check as an example if you can verify if the hwpacks built
today
works fine on your Origen board.
http://ci.linaro.org/kernel_hwpack/linux-arm-soc-for-next/linux-arm-soc-for-... .
With this image, I couldn't see the booting message.
Thanks for trying this. What is the last message we see when the hwpack boots ?
exactly same as like the previous one.
Deepti, do you want to get one Origen board from Samsung Bangalore ?
Ah! that would be cool. Thanks. But am not allowed to get any hardware like that from outside into IBM. It would have to go through the process at IBM. I will speak to my manager to understand how I can loan an origen board if offered.
Do we need to apply the patch you gave yesterday on top of the Arnd
latest
changes to make it work ?
Yes,
I downloaded git:// git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git and then could see the booting message with the patch.
On 15 February 2012 21:35, Paul Larson paul.larson@linaro.org
wrote:
On Wed, Feb 15, 2012 at 3:46 AM, Deepti Kalakeri deepti.kalakeri@linaro.org wrote: > > > > On Wed, Feb 15, 2012 at 4:32 PM, Sangwook Lee <
sangwook.lee@linaro.org>
> wrote: >> >> >> >> On 14 February 2012 16:40, Paul Larson paul.larson@linaro.org
wrote:
>>> >>> On Tue, Feb 14, 2012 at 2:21 AM, Sangwook Lee >>> sangwook.lee@linaro.org wrote: >>>> >>>> Hi Paul >>>> >>>> On 14 February 2012 01:03, Paul Larson paul.larson@linaro.org >>>> wrote: >>>>> >>>>> Looking at the latest results on.the kernel CI view I pointed
out
>>>>> earlier, here is a serial.log from a recent one >>>>>
http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linu...
>>>>> >>>>> You can see the test kernel starting to boot at around line
19560
>>>>> and at 19660 it gets only as far as the starting kernel
message, hangs, and
>>>>> eventually times out. >>>> >>>> I think there is no option to download this log, maybe only for
LAVA
>>>> team. >>>> If I download serial.log file as html, I must follow the link to >>>> serial log but again I have a broken link. >>> >>> Yes, we need a download link there - known feature request that
we'll
>>> hopefully get to soon. >>>>> >>>>> but replaces the kernel with the output from jenkins building
the
>>>>> selected kernel. I'm guessing that perhaps we're missing
something critical
>>>>> from the kernel configuration? >>>> >>>> Yes, That's right. I am attaching the patch to fix this problem. >>>> Unfortunately, currently this is not up-streamable. Hope that we >>>> apply this as doing debian packaing. >>>> please let me if you have further problem. >>> >>> >>> I'm not sure what you mean here. If this patch fixes the problem, >>> what is preventing it from going upstream? >> >> >> arnd kernel (mainline kernel) we have to do the following for
Origen
>> board >> 1) Select exynos4_defconfig >> All boards for exynos CPU are sharing one >> configuration. >> So It select all boards configs and then set
UART
>> port to 1 >> 2) We have to set UART port to 2 manually only for
Origen
>> >> The patch I sent to you is to select debug UART port to 2 by
default,
>> only for Origen >> If we release this patch into mainline, all other boards using
Exynos
>> will manually select UART port again. >> >> >>> >>> I guess we have this fix somewhere in the kernel produced by the >>> landing team? If so, it seems maybe we should also add the
landing team
>>> tree here for testing so that we can see it pass. >> >> >> Here is our branch: >> Git: >> git://git.linaro.org/landing-teams/working/samsung/kernel.git >> branch: tracking >> >> Initially I thought LAVA team is using hwpack built by John >> >>
https://code.launchpad.net/~jcrigby/+recipe/linux-linaro-3.2-lt-origen-dailyhttps://code.launchpad.net/%7Ejcrigby/+recipe/linux-linaro-3.2-lt-origen-daily
>> >> Does Lave team build their own hwpack from kernel ? > > > Not the LAVA team. We(Infra) team build the latest upstream changes
on
> ci.linaro.org and then send them to LAVA for testing.
Right, so I guess the better question would be, is there a bug for
this
already, and is there a better solution? Can we pass something on
the boot
cmdline that selects the proper uart? Why don't we have this problem
with
the linaro kernel in our leb images, do they include this workaround
there?
Thanks, Paul Larson
-- 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
-- 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-validation@lists.linaro.org
-
Deepti Kalakeri -
Paul Larson -
Sangwook Lee