Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: [email protected]
W: www.topicproducts.com
Please consider the environment before printing this e-mail
On 27-01-2021 16:43, Leon Woestenberg wrote:
Hello Mike,
At first sight, this does sound like memory corruption in one specific
memory area (DIMM?) to me.
On itself, yes, that was my first thought too - hence running memory and
system tests.
But it only happens with the gatesgarth branch. I've put loads of
pressure on this machine's memory before, never got errors like that. I
sometimes have multiple OE branches building at the same time too.
Check dmesg for tripping temperatures etc.
I would reduce both the amount of bitbake tasks and Makefile
parallelism to 1 on a fresh run to reduce memory pressure.
Reducing somewhat, e.g. 8 each, did not make a difference. Didn't want
to go to "1", it'll take days to rebuild then...
Not seen anything similar yet (MACHINE=zcu102, build host i7-10700K w/
128MB memory.)
Guess that's GB not MB :)
Mine is a Ryzen 7 1700 w/ 32GB.
CPU Temp doesn't rise above 70 degrees while building (during mprime
testing it got up to 90, still within spec)
I would assume aarch64 is widely run by the community.
I would, too
Let me know if I must replicate a specific set of commits.
Don't know what you mean by that, can you explain?
Regards,
Leon.
On Wed, Jan 27, 2021 at 4:10 PM Mike Looijmans
<[email protected] <mailto:[email protected]>> wrote:
When doing large builds, the GCC compiler tends to crash on random
spots
in the code. There are a few common denominators though.
It only happens when compiling for aarch64 (cortex-A53), not for
32-bit
arm (cortex-A9)
It's random and usually happens on "big" sets like kernel, openssl,
boost, u-boot etc.
It always reports "during GIMPLE pass: ealias" in the error, for
example:
| during GIMPLE pass: ealias
| ../openssl-1.1.1i/crypto/x509v3/v3_utl.c: In function
'do_x509_check':
| ../openssl-1.1.1i/crypto/x509v3/v3_utl.c:1239:1: internal compiler
error: Illegal instruction
| 1239 | }
Compiling the same thing again usually goes fine.
I've never experienced this with the zeus and older branches of OE.
I've already tried upgrading to the latest gatesgarth status, and
cleaning out everything and start from scratch. I've also run
"mprime"
test on my machine (over one hour) just to be confident that the
system
itself is really okay.
Ideas to diagnose, fix or reliably reprodruce are more than welcome.
--
Mike Looijmans
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: [email protected]
<mailto:[email protected]>
W: www.topicproducts.com <http://www.topicproducts.com>
Please consider the environment before printing this e-mail
--
Mike Looijmans
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#147353):
https://lists.openembedded.org/g/openembedded-core/message/147353
Mute This Topic: https://lists.openembedded.org/mt/80159078/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
