From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-06-29
Date: Sat, 30 Jun 2018 21:21:04 +0200 [thread overview]
Message-ID: <20180630212104.4254a15e@windsurf.home> (raw)
In-Reply-To: <CAMWSM7icLBAbxF9OmTCSPr5qXjeNZJBa7ddZP9SbdHpVmY03jg@mail.gmail.com>
Hello,
On Sat, 30 Jun 2018 12:17:35 -0700, Joseph Kogut wrote:
> > It seems that gcc 8.1.1 from the host (ArchLinux) is buggy, there is no such
> > error with a Fedora 28 with gcc 8 installed.
>
> I'm wondering if it really is an Arch bug, or something else, because
> the problem is not consistently reproducible. It seems to only happen
> a fraction of the time, and I can run make again on the exact same
> config after GCC segfaults, and the build will finish.
>
> Could be a hardware problem. I remember reading about a segfault issue
> with Ryzen chips during parallel compilation, though Threadripper
> chips, which this was built on, weren't supposed to be affected.
I also believe it's a HW issue. Could you stop your autobuilder, until
you figure out what's going on ?
Having bogus build results really isn't helpful, as it gives a lot of
noise to analyze and triage to find out what are the interesting things
to look at.
However, I very much welcome an installation like yours as part of the
autobuilders, because you found out a number of issues that we had
never found so far, and those are very useful to fix.
> I have a few Arch systems with Intel chips I can use to see if I can
> reproduce the issue. That would at least tell us if it *is* an Arch
> bug, or a hardware problem.
Would be good.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-06-30 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-06-29 Thomas Petazzoni
2018-06-30 18:30 ` Romain Naour
2018-06-30 19:12 ` Thomas Petazzoni
2018-06-30 19:17 ` Joseph Kogut
2018-06-30 19:21 ` Thomas Petazzoni [this message]
2018-06-30 19:28 ` Joseph Kogut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180630212104.4254a15e@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox