[yocto] yocto jethro failed on gettext-native

[Zoran Stojsavljevic]

> Take a look at BIOS settings. I had a board that was overclocking based
> on CPU temperature, which failed miserably when you actually used all
> the cores. Disable such settings.

This has nothing to do with this particular problem. You simply, since
you over-clocked CPU, reached very quickly TDP1 (using all cores),
then reached beyond so-called TDP2 (since you did not setup CMOS
correctly), which initiated/triggered HW control called /PROCHOT... In
order to save CPU from physical damage, since you have reached very
close to Junction T.

Even if you did setup thresholds correctly, CPU probably went to
hold/blocked state for some limited time to throttle, in order to cool
down... Then these YOCTO failing effects might be visible, but I have
no idea how (most likely some overheated cores got thread of
execution/HyperThreads pipeline stale/lost)!?

My best guess, IMHO!

Zoran
_______

On Fri, Apr 27, 2018 at 2:04 PM, Philip Balister <philip at balister.org> wrote:
> On 04/27/2018 02:19 AM, Oliver Graute wrote:
>> On 26/04/18, Zoran Stojsavljevic wrote:
>>>> I deleted all the build-imx6ulevk folder and build everything from
>>>> scratch with only one thread, waited a few hours for compilation and now
>>>> its working ;)
>>>
>>> Still, I am struggling to understand why??? What is the requirement
>>> behind this ask?
>>
>> The requirement was just get our older yocto (jethro) build running on a
>> PC of a different developer. Often developers have their own flavor of
>> Ubuntu releases and they update to newer versions while they still
>> develop on yocto releases which is much older. Because that yocto
>> release is currently in the field by our costumer. Our product cycle is
>> not so fast to use the newest yocto releases. We started to develop when
>> jethro was up to date.
>>
>> We compiled single threaded just because his PC is a bit unstable on
>> high load. And it crashed a few times on parallel makes. I know that
>> this is not ideal for yocto development.
>
> Take a look at BIOS settings. I had a board that was overclocking based
> on CPU temperature, which failed miserably when you actually used all
> the cores. Disable such settings.
>
> Philip
>
>
>>
>>>
>>> As we see, it is much longer (one thread only) than on 14.04!?
>>
>> its takes much longer then with settings
>>
>> PARALLEL_MAKE = "-j 4"
>> BB_NUMBER_THREADS = "4"
>>
>>> Could you, please, do it on Ubuntu 17.04, or 17.10 (i bet, you
>>> can't)??? And why, after all???
>>
>> currently not im using only Ubuntu LTS Releases.
>> Perhaps I will try 18.04  LTS which released yesterday ;)
>>
>> Best regards,
>>
>> Oliver
>>
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto