On 11/30/14, Barry Kauler <[email protected]> wrote: > On 11/29/14, René Rebe <[email protected]> wrote: >> Hi, >> >> On Nov 29, 2014, at 16:23, Barry Kauler <[email protected]> wrote: >> >>> >>> The first time that I did a build recently, using rev 43395, my laptop >>> crashed when building gcc at stage 5. >>> Just died, instantly, turned completely off. >>> >>> So I powered up again, didn't bother with a f.s. check, ran >>> Build-Target again, this time gcc succeeded and the rest of the build >>> completed. >>> >>> Second build, no problem. >> >> Sounds like the CPU (and i/o) load of compiling gcc caused overheat, or >> otherwise data integrity problem :-/ >> >>> This morning I started the third build. This time, crashed at gcc >>> stage-5. Did a f.s. check and tried again, crashed again. And again, >>> and again. >>> >>> Not good. >>> >>> I currently only have two laptops to build on. Ok, I will copy >>> everything over to my old laptop and see what happens. >> > > Ah, my old laptop has succeeded! > > It is a faithful old workhorse. Acer model 3681WXMi, 60GB HD, 512MB > RAM, Celeron M 410 1.46GHz (single core CPU). > > As I didn't have enough space on the HD, I plugged in a USB HD -- only > USB-2. > > So, very slow. But, it chugged away overnight, through today. Sailed > through compiling 'gcc' at stage-5. > > Which makes me wonder about the cores in my latest laptop. Its an i3 > Intel CPU, with 4 cores, and T2 is using all 4. > I will configure T2 to use just 1 core, and we will see what happens. >
Reporting the outcome. On my main laptop, I reduced number of jobs in parallel from 4 down to 1, in the T2 menuconfig. Slower, but now my laptop does not crash. Very interesting. Regards, Barry
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
