From: Borislav Petkov <bp@alien8.de>
To: Satoru Takeuchi <satoru.takeuchi@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, x86@kernel.org
Subject: Re: [FYI] GCC segfaults under heavy multithreaded compilation with AMD Ryzen
Date: Fri, 11 Aug 2017 12:07:04 +0200 [thread overview]
Message-ID: <20170811100704.GA10069@nazgul.tnic> (raw)
In-Reply-To: <CAMym5wuTuVJxoH2+qAy6s2t0g3OpKMUKTH2XfbtXHOTTKSMOYw@mail.gmail.com>
On Wed, Jul 26, 2017 at 06:54:01AM +0900, Satoru Takeuchi wrote:
> # I'm a LKML subscriber, but not a x86 list subscriber
>
> I found the following new linux kernel bugzilla about Ryzen related problem.
> Since many developers don't check this bugzilla and I've also
> encountered this problem,
> I decided to introduce this problem here.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=196481:
> > I am running Ubuntu and installed the mainline kernel from the mainline PPA.
> > It seems like the Ryzen processor has some bug that leads to gcc crashing
> > when compiling a very large program under heavy load. This is easily reproduced
> > in my system using the script from
> >
> > https://github.com/suaefar/ryzen-test
> >
> > (It assumes that you are running Ubuntu, maybe Debian also works. Just clone it and run the > script kill_ryzen.sh. It downloads the gcc 7.1 code and start multiple compilations of it. If any
> > compilations fails its warns the user giving the time to detect failure).
> >
> > There is already a bug report about this in the FreeBSD bugzilla
> > (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399#c89).
> > There is also a thread on the subject in AMD community forum
> > (https://community.amd.com/thread/215773?start=300&tstart=0)
> > and Phoronix (https://www.phoronix.com/forums/forum/hardware/processors-memory/955368-some-ryzen-linux-users-are-facing-issues-with-heavy-compilation-loads).
Apparently, you can RMA your CPU:
https://www.phoronix.com/scan.php?page=news_item&px=Ryzen-Segv-Response
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2017-08-11 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 21:54 Satoru Takeuchi
2017-07-31 12:04 ` Alan Cox
2017-07-31 12:22 ` Markus Trippelsdorf
2017-08-11 10:07 ` Borislav Petkov [this message]
2017-09-16 12:25 ` Satoru Takeuchi
[not found] <u7g1Z-8nQ-33@gated-at.bofh.it>
2017-07-26 1:42 ` Andreas Hartmann
[not found] ` <u9hGi-686-19@gated-at.bofh.it>
2017-07-31 17:00 ` Andreas Hartmann
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=20170811100704.GA10069@nazgul.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=satoru.takeuchi@gmail.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®