On Thu, Mar 11, 2021 at 11:22 PM Mike Looijmans <[email protected]> wrote: > > > 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 05-03-2021 00:32, Randy MacLeod wrote: > > On 2021-02-05 2:49 a.m., Mike Looijmans wrote: > >> I've been doing quite some tests and things last week, my conclusion > >> so far is that the latest gcc seems to trigger a bug particular to > >> this CPU. Maybe even this particular batch. > >> > >> Hours of testing found no issues with RAM. > >> > >> I've also done huge amounts of builds with zeus, no problems. > >> > >> Then googling for "illegal instruction gcc ryzen 1700" reveals quite > >> a few threads on something that sounds suspiciously similar. Though > >> it makes me wonder why I never encountered it before, since these are > >> all many years old. I did try a bunch of the suggestions done there, > >> but so far no luck. > >> > >> > > > > Any update on this bug Mike? > > Have you opened a YP bug? If not please do. > > I'd like to see if the problem still happens on master. > > Interesting. > > I just built the 64-kernel using OE master and no crashes, everything > went fine. With the gatesgarth branch, it'd crash at least two times > during kernel compilation. > > So something has been fixed since then?
can you try by disabling uninative ? > > > -- > Mike Looijmans > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#149327): https://lists.openembedded.org/g/openembedded-core/message/149327 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]] -=-=-=-=-=-=-=-=-=-=-=-
