From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2018-02-25
Date: Tue, 27 Feb 2018 13:08:22 +0100 [thread overview]
Message-ID: <20180227130822.2208e02b@gmx.net> (raw)
In-Reply-To: <87fu5nsyrg.fsf@dell.be.48ers.dk>
Hello Peter,
On Mon, 26 Feb 2018 13:48:03 +0100, Peter Korsgaard <peter@korsgaard.com> wrote:
>
> >> powerpc | binutils-2.29.1 | NOK |
> >> http://autobuild.buildroot.net/results/22839bca79e16fc0d76ebc0f3e5ec4a6d23e99f6
> >> | ORPH
>
> > read.c: In function 's_app_line':
> > read.c:2001:1: internal compiler error: Segmentation fault
> > s_app_line (int appline)
>
> > Compiler error. It's on PowerPC, with a toolchain from 2017.11. Could
> > someone retry with a newer gcc, and see if it is fixed ?
>
> Notice that this happened on gcc67, so on the Ryzen CPU (and nowhere
> else), so I'm afraid the Ryzen crashes are _STILL_ not fixed. I'll stop
> the autobuilder again.
Is it a Ryzen CPU manufactured prior to week 25/2017? It is possible to
get an exchange CPU via RMA by AMD Customer Care, see [1] (worked for me
and the new delivered CPU runs stable (and after disabling PowerSaveStates
leading to machine-check exception)...
Regards,
Peter
[1] https://www.phoronix.com/scan.php?page=article&item=new-ryzen-fixed&num=1
next prev parent reply other threads:[~2018-02-27 12:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-02-25 Thomas Petazzoni
2018-02-26 10:33 ` [Buildroot] Analysis of build " Thomas Petazzoni
2018-02-26 10:51 ` Johan Oudinet
2018-02-26 10:58 ` Thomas Petazzoni
2018-02-26 13:44 ` Frank Hunleth
2018-02-26 12:48 ` Peter Korsgaard
2018-02-26 13:00 ` Thomas Petazzoni
2018-02-26 14:06 ` Peter Korsgaard
2018-02-26 14:47 ` Thomas Petazzoni
2018-02-26 19:01 ` Peter Korsgaard
2018-03-01 19:41 ` Arnout Vandecappelle
2018-03-01 21:17 ` Peter Korsgaard
2018-02-27 12:08 ` Peter Seiderer [this message]
2018-02-27 13:12 ` Peter Korsgaard
2018-02-26 15:30 ` Mahyar Koshkouei
2018-02-26 15:40 ` Thomas Petazzoni
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=20180227130822.2208e02b@gmx.net \
--to=ps.report@gmx.net \
--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