Thanks for this Ryan. I'll try to get round to updating a5 in the next day or so.
Thanks Dave On 2 Apr 2013, at 19:00, Ryan Harkin <[email protected]> wrote: > On 2 April 2013 10:11, Dave Pigott <[email protected]> wrote: >> >> On 2 Apr 2013, at 09:25, Ryan Harkin <[email protected]> wrote: >> >> >> >> >> On 2 April 2013 08:24, Dave Pigott <[email protected]> wrote: >>> >>> >>> On 2 Apr 2013, at 00:06, Antonio Terceiro <[email protected]> >>> wrote: >>> >>>> Hey guys, >>>> >>>> Looking at the LAVA queue right now, we have: >>>> >>>> - 20 jobs for rtsm* >>>> - 15 jobs for snowball_sd >>>> - 15 jobs for vexpress-a5 >>>> >>>> Dave: >>>> >>>> regarding rtsm*, what's the status of the cloud problems? Do you need >>>> any help with that? >>> >>> rtsm should be running - unless there's some Andy Doan config that needs >>> to be done. >>> >>>> >>>> regarding snowball_sd, how close we are from a solution? >>> >>> Well, I have a built image, but it still has the problem with eth0 not >>> coming up. I need to poke Andrey to find out what the status is. In the >>> meantime snowball01 and 03 should be ok - they have the temporary emmc >>> master image. I just discovered they were both offline - I'm working on >>> getting them back. >>> >>>> >>>> regarding Vexpress A5, the notes from the last leads weekly meeting say >>>> "microSD needs updating for UEFI, we can’t enable it yet". Is there >>>> anything other than manpower with physical access to the lab blocking us >>>> from going ahead with this? >>> >>> IIRC Ryan said A5 was now good to go. It's just a case of prioritising and >>> scheduling. I've copied Ryan on the mail so he can comment. Ryan? Are we ok >>> for A5? >>> >> >> Yes, A5 was updated and is waiting to be put back online. It should be able >> to use it's old health check and master images, but I'd recommend using a >> more recent one, just so it's up-to-date. >> >> >> OK - I'll put back online for now and see how it goes. Will update master >> image later when I've got some spare cycles. > > I've just realised there was *something* else about this, so I dug out > my last email on the topic, which was: > > ---------------------------------------------------------------------- > Hi Dave, > > I've upgraded the A5 board now. > > I've hacked the master image with the 13.01 kernel/initrd/dtb, so it's > booting fine into master. You might want to deploy 13.01 as a proper > master image at some point. > > I've added the configs for the test images (LAVA Test Image and LAVA > Android Test Image) however, the test image crashes at boot, even > though I've also hacked in the 13.01 kernel/initrd/dtb. > > So, I think the next step for you is to deploy a test image / health > check - a 13.01 image will be best - to make sure the board is > actually deployable. > > Cheers, > Ryan. > > ps. I installed openssh-server into the master image, hope it isn't a > problem. I don't need it any more, so it's ok to uninstall it (or > installing a new master image will get rid of it, of course). > ---------------------------------------------------------------------- > > So the health check image may well need updating... > > I just looked, and the health check job crashed... I see this error in the > log: > > [ 602.838381] [ INFO: possible circular locking dependency detected ] > > Although it only seemed to be a warning here, it is an intermittent > fault and was fixed in 13.02, so I guess we should try to move to the > latest images for master & health check. > > The reason for the complete failure was this line in the log: > > ERROR: Did not find Device Tree blob. > > ... when attempting to run option "[2] LAVA Test Image". I guess the > image being deployed didn't have the DTB file in there? I went over > to look for the boot.tgz file but it seems to be gone now (it was in > tmp). > > Cheers, > Ryan. _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
