Ignoring the one failure while I was getting tc2 up and running, we have the following:
------------
panda06
------------
http://validation.linaro.org/lava-server/scheduler/job/38176
The key part is in downloading root.tgz. It gets part way through and then we get "connection reset by peer" on every single retry until we fail.
I've put it back online to retest.
Thanks
Dave
Just got a call from Zen. The leased line is down and we're on the ADSL backup.
I'm preparing to go into the office if needed. Awaiting a callback from Zen.
Thanks
Dave
Begin forwarded message:
> From: Zen Technical Support <support(a)zen.co.uk>
> Subject: Your Zen Fault tracker link - fault ref. 138424
> Date: 13 November 2012 09:30:07 GMT
> To: dave.pigott(a)linaro.org
> Reply-To: support(a)zen.co.uk
>
> Zen Fault Tracker for Fault ref. 138424
> Please do not reply to this email. If you have questions please submit them via the online fault tracker (see link below) to ensure they reach the person dealing with your fault.
>
> The following fault has been opened:
> Fault ref: 138424
> Date fault opened: Tuesday 13th November 2012, 9:21am
> Product/service: Zen Ethernet 100
> Bandwidth: 10 Mbps
> Contract Length: 3 Years
> Bandwidth Type: Premium
> 2C00807211
> Installation
> Address: Suite 220
> The Quorum
> Cambridge
> Order Id: 803244
> Track your Fault Online
> To view the full details of this fault and to ensure you receive updates and history for this fault please click on the following link:
> https://secure.zen.co.uk/zebra/sec/fault.asp?f=138424&a=683586260774
> Updates from Zen are typically provided once per day - Monday to Friday.
>
> Providing Zen with additional information
> Technical Support may request additional information from you in order to progress the fault. Use the form on the page linked above to respond to these requests.
>
> Please note: further notification of updates will not be sent unless you visit the fault tracking page using the link above.
>
> Mobile Updates
> If you wish to receive updates to your mobile via SMS text message please request this using the form on the fault tracker - and provide your mobile number for these updates.
>
> Contacting Technical Support
> We recommend using the form on the page linked above to contact Technical Support, however if you do need to contact Technical Support by telephone we advise calling between 12pm and 4pm on 0845 058 9009 or 01706 902 009. You can also check for Technical Support's current call queue times here, before calling.
>
> Best regards
>
> Technical Support
> --------------------------------------------------
> Zen Internet Ltd
> Sandbrook Park
> Sandbrook Way
> Rochdale
> OL11 1RY
>
> Customer Billing email: customerbilling(a)zen.co.uk
> Credit Control email: creditcontrol(a)zen.co.uk
> Sales email: sales(a)zen.co.uk
> Partner email: partner(a)zen.co.uk
> Support email: support(a)zen.co.uk
> Web: www.zen.co.uk
>
> Switchboard: 0845 058 9000 or 01706 902 000
> Support help line: 0845 058 9009 or 01706 902 009
> Fax: 0845 058 9005 or 01706 902 005
>
> Follow us on Twitter: http://twitter.com/zeninternet
> --------------------------------------------------
>
> The information contained in this email may be confidential and may also be legally privileged. It is intended solely for the addressee(s). If you are not the intended recipient then please delete forthwith.
>
> If a quotation is included, it is provided for budgetary purposes only and is subject to status. Charges exclude VAT and are correct at time of quotation, but may change at any time. All transactions are subject to the appropriate Zen Internet Ltd Terms and Conditions.
>
> Zen Internet Limited is registered in England No. 03101568, VAT Reg No. 686 0495 01.
>
Hi all,
Absent of an emergency in the lab I'm working from home tomorrow. I need to work on my ARM presentation and some minor code updates. Please let me know overnight if I need to be in.
Thanks
Dave
Sent from my Aldis Lamp
Just the one…
------------
panda03
------------
http://validation.linaro.org/lava-server/scheduler/job/38289
Looks like the board locked up just after the startup animation completed. Went onto the board, and it was indeed locked. Hardreset and it came back. Put it down to a one off glitch.
Dave
Hi Michael,
Send me the hard float kernel and some instructions, I'll get onto it.
Re: panda-es, as long as long as nobody complains from the validation list (cc'd) then I don't have a problem off-lining one.
Thanks
Dave
On 9 Nov 2012, at 03:24, Michael Hope <michael.hope(a)linaro.org> wrote:
> Hi Dave. Paul's looking at moving my cbuild stuff into LAVA but I may
> need to take a shortcut. We have six Pandaboards at the moment with
> five functioning. If I got you a hard float image and kernel, could
> you reinstall two of the boards and fix up the broken one? That'd
> give me three soft float and three hard float boards and let me turn
> off the boards in my office.
>
> Could I also steal one or two permanently from the pool? Perhaps a
> Pandaboard ES to use for benchmarks?
>
> -- Michael
I was just doing a manual update of staging and see it got broken
because the dashboard code now requires a newer version of
linaro-dashboard-bundle. I doubt we've packaged that new version and
deployed it, so to address it for now I created a local branch for that
module as well.
This is more of a note that we'll need to remember to make appropriate
updates (lava-manifests ...) when we do our next roll-out of dashboard
changes.
Hi James,
Added the validation list to your e-mail for future reference. :)
Dave
On 8 Nov 2012, at 14:45, James Tunnicliffe <james.tunnicliffe(a)linaro.org> wrote:
> (sorry Dave, validation(a)linaro.org bounced. Not sure what your team's
> address is - please forward)
>
> http://askubuntu.com/questions/211603/problems-with-nat-adapater-since-upgr…
>
> This got me. NAT doesn't work in 12.10, but the proposed fix works:
>
> VBoxManage modifyvm "name" --natdnshostresolver1 on
> VBoxManage modifyvm "name" --natdnsproxy1 on
>
> Not sure if it is worth mentioning in the docs or not.
>
> --
> James Tunnicliffe
Hey Guys,
I'm doing a final test on panda24 before deploying a new dispatcher in
production. This means its no longer in the looping health job mode we
were doing.
-andy
http://staging.validation.linaro.org/scheduler/job/35505/log_file
This is a bit odd. It got confused when we were in the u-boot prompt while trying to boot up the android test image. It may be some code flaw, though I can't see what, other than it took 5 minutes to get from reboot to that point. Perhaps this calls for a similar approach to booting test images, i.e. if it fails, try a couple more times. May be an edge case, but would put our reliability way up. Along with that, we may have to up the timeouts for booting, given we might do it 3 times.
Thoughts?
Dave
