From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
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: Mon, 31 Jul 2017 13:04:35 +0100 [thread overview]
Message-ID: <20170731130435.6cb4f00f@alans-desktop> (raw)
In-Reply-To: <CAMym5wuTuVJxoH2+qAy6s2t0g3OpKMUKTH2XfbtXHOTTKSMOYw@mail.gmail.com>
On Wed, 26 Jul 2017 06:54:01 +0900
Satoru Takeuchi <satoru.takeuchi@gmail.com> 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.
Historically we've seen exactly these symptoms on all kinds of systems
where the memory is at fault, even in cases where memtest86 passes.
Whether there's a specific problem on some Ryzen boards is a question for
AMD, but if I saw this without knowing the CPU I'd suspect memory
firstly. GCC it turns out is by accident an amazingly effective memory
testing tool.
If it is memory corruption problems then no - the kernel cannot work
around that level of hardware failure. The BIOS may be able to if it is a
board or compatibility problem as memory tuning is usually done by the
BIOS.
Alan
next prev parent reply other threads:[~2017-07-31 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 21:54 [FYI] GCC segfaults under heavy multithreaded compilation with AMD Ryzen Satoru Takeuchi
2017-07-31 12:04 ` Alan Cox [this message]
2017-07-31 12:22 ` Markus Trippelsdorf
2017-08-11 10:07 ` Borislav Petkov
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=20170731130435.6cb4f00f@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--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