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-linux-next/bundles/2bbe117846bab5d41bc8222e38945aae78802c8d/1180312c-5628-11e1-9729-68b599be548c/attachments/47519/

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.org> wrote:
Hello Sangwook,

On Mon, Feb 13, 2012 at 5:09 PM, Sangwook Lee <sangwook.lee@linaro.org> wrote:
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-next_origen-exynos4/hwpack_linaro-lt-origen_20120209-0723_b255_armel_supported.tar.gz used 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;a=summary)


 
 
 
 
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%20Builds/job/linux-arm-soc-for-next_origen-exynos4/255/consoleFull.

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-linux-arm-soc-for-next/bundles/5216a65f3ace85651125fb35227aa49a4f037f3e/4fae3fe8-52ef-11e1-9729-68b599be548c/attachments/45489/ is 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






--
Thanks and Regards,
Deepti  
Infrastructure Team Member, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs