I've also noticed on this job YAML: http://pastebin.ubuntu.com/19177546/
You need to indent compression underneath nfsrootfs, so it would be
nfsrootfs: url: file:///home/jalbarran/ti-filesystem/tisdk-rootfs-image-am335x-evm.tar.gz compression: gz
because you are declaring the compression of the nfsrootfs.
On 12 July 2016 at 20:08, Neil Williams codehelp@debian.org wrote:
On Tue, 12 Jul 2016 14:32:52 +0000 "Albarran, Josue" j-albarran@ti.com wrote:
Yes, I have tried it outside and it produces the login shell. I was thinking the same for the timeout. How can I change this timeout in order to give the board sufficient time to get to the login prompt? I even made the timeout for the boot action to 6 minutes and still have the same issue.
I don't think it is a timeout - you've got 360s in that timeout. start: 2.4.5 auto-login-action (max 360s)
The standard job for this device only needs: start: 2.4.5 auto-login-action (max 120s) https://staging.validation.linaro.org/scheduler/job/152266#action_2-4-5
The timeout itself is set in the boot action - 2 minutes in the case of the standard job.
We created standard jobs for just this reason - to reduce the number of variables.
https://staging.validation.linaro.org/scheduler/job/152266
This is known to work and gives you a base point to compare with your job. The metadata links to how the files were built.
Staging is using the new code scheduled for the 2016.7 release, so the logs look different.
Your problem looks like a misunderstanding of the prompts list:
prompts: - "am335x-evm login:" method: u-bootThat is not the prompt of the eventual test shell, that is the auto-login prompt:
auto_login: login_prompt: 'login:' username: root prompts: - 'root@jessie:'The am335x-evm is a bad idea in this case. The auto-login prompt needs to be independent of the hostname of the device or it will break as soon as you add a second device or even a second image.
You need to know what prompt this image will give in a normal boot, then set that in the prompts list - it is NOT likely to be login:
If your system needs a password as well as a user, you'll need to specify the password_prompt and password in the auto_login section.
What is happening is not that the test times out, it is that you've asked the test job to do something which is actually different to what you do on the command line, so with a lack of response, it will timeout no matter how long you wait.
-----Original Message----- From: Matt Hart [mailto:matthew.hart@linaro.org] Sent: Tuesday, July 12, 2016 9:29 AM To: Albarran, Josue Cc: linaro-validation@lists.linaro.org Subject: Re: [Linaro-validation] Pipeline Job Submission
Have you tried this boot outside of Lava?
It's either a timeout is too short and doesn't give your board enough time to get to the login prompt, or the rootfs you are loading does not produce a login shell.
On 12 July 2016 at 15:24, Albarran, Josue j-albarran@ti.com wrote:
Hi,
I’m having an issue where the board (beaglebone-black) starts the booting process using the u-boot commands that I specify but gets interrupted before it gets to the “am335x-evm login:” login prompt. I get the following exception http://pastebin.ubuntu.com/19177228/. Any known fix for this issue?
This is the complete boot log section of the pipeline actions http://pastebin.ubuntu.com/19177444/. Also, my YAML job definition can be found here http://pastebin.ubuntu.com/19177546/.
I will appreciate a response.
Thanks,
Josue
linaro-validation mailing list linaro-validation@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-validation
linaro-validation mailing list linaro-validation@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-validation
--
Neil Williams
http://www.linux.codehelp.co.uk/
linaro-validation mailing list linaro-validation@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-validation