[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Proposal to replace/extend current armhf builders



On Thu, Jan 23, 2014 at 8:11 PM, peter green <plugwash@p10link.net> wrote:
> peter green wrote:
>>
>> Steve McIntyre wrote:
>>>
>>> if we're happy that they're stable and supportable.
>>>
>>
>> Having had a 2GB nitrogen6x running as a raspbian buildd for a while I
>> would consider it "stable and supportable". We did have some crashes on both
>> the nitrogen6x and the wandboard quad  caused by the eglibc testsuite in the
>> past but since upgrading to  3.11.0-armv7-x13 that seems to have stopped
>> happening.
>
> For the record some news on the raspbian imx6 based autobuilders
>
> Bad: two buildds (both wandboard quads) running robert nelson's
> 3.11.0-armv7-x13 crashed while trying to build the latest iceweasel
> Good: these crashes prompted me to upgrade to the 3.13 kernel from
> experimental (compiled locally because the debian autobuilders haven't built
> it yet) on the raspbian build cluster which I can now confirm boots
> successfully and brings up all the hardware needed for autobuilding on both
> the 2GB nitrogen6x and the wandboard quads. After the kernel upgrade one of
> the wandboards built the new iceweasel without crashing.
> Ugly: reconfiguring u-boot to load the initrd was a pain.
>
> Other than the two crashes with the new iceweasel I don't recall having any
> crashes in quite some time.

Yeah, sorry v3.11.x was painful on those wandboard quad's for awhile.
(specially sata rootfs)  Since you originally had 3.11.0-armv7-x13,
you should also double check the version of u-boot has this patch to
enable the cpu errata fixes..

http://git.denx.de/?p=u-boot.git;a=commit;h=02824dc78642b3057cc8c1ab7dc32203f55a17fa

My build identifier for that is:
U-Boot 2013.10-00016-g6cccbd3 (Dec 05 2013 - 16:14:38)

As i was seeing other oddities on my wand's while doing gcc trunk
bootstraps and building chromium.

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/


Reply to: